Finish dispatch-path partial-launch guarantees after #1359 #1362

Merged
coilyco-ops merged 1 commit from issue-1360 into main 2026-07-15 09:11:07 +00:00
Member

This tightens the dispatch path so a run that actually launched cannot be flattened into a generic capacity failure when reservation posting fails. The reservation acquisition path now carries a structured partial-launch signal, and the broker/output layers preserve it as the final dispatch result.

  • Partial-launch errors now carry repo, issue, container, and remediation text.
  • Dispatch artifacts classify the new state explicitly instead of treating it as launch failure or capacity backpressure.
  • Tests cover the reservation-post failure path and the dispatch classification.

closes #1360
ward.workflow: pull-request-and-merge

This tightens the dispatch path so a run that actually launched cannot be flattened into a generic capacity failure when reservation posting fails. The reservation acquisition path now carries a structured partial-launch signal, and the broker/output layers preserve it as the final dispatch result. - Partial-launch errors now carry repo, issue, container, and remediation text. - Dispatch artifacts classify the new state explicitly instead of treating it as launch failure or capacity backpressure. - Tests cover the reservation-post failure path and the dispatch classification. closes #1360 ward.workflow: pull-request-and-merge
Surface partial-launch after reservation post failure
All checks were successful
test / test (pull_request) Successful in 50s
c1425fa1a8
Sign in to join this conversation.
No description provided.