Problem Statement

• WorkerProcess._process_next_request always sends completed after backend.resolve(...) returns, without validating final response content.
• This can mark requests successful even when final response is missing (None) or empty (no choices/content/usage).
• Downstream this increments successful_requests and enters completed metrics.

Proposed Solution

• If final resolve result has no usable output payload, request should be marked errored (or at minimum cancelled/incomplete, but not successful).
• Successful completion should require a valid terminal response contract.

Alternatives Considered

No response

Usage Examples

Additional Context

No response