Runner · Request context & routing

Deadline handling

Carry one named deadline across admission and bounded work, then report expiry as a distinct outcome.

Workflow

1. Declare time limitThe caller supplies a supported positive limit with the request.
2. Validate deadlineThe Runner validates units and boundary before submission.
3. Check remaining timeThe operation checks the deadline around blocking or streamed work.
4. Return deadline outcomeExpiry is distinct from cancellation, unavailable and failed work; partial artifacts remain named.
5. Return completed resultOnly work that reaches its normal completion boundary before expiry is complete.

Failure boundaries

• Negative timeoutValidation refusal: Correct request
• Work continues after expiryEnforcement gap: Stop claiming bound
• Expiry shown as cancelOutcome mapping error: Preserve distinction

runner.route.deadline