coilyco-flight-deck/ward
2
0
Fork 0
Code Issues 107 Pull requests 2 Projects Releases 737 Packages Wiki Activity Actions

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
Conversation 0 Commits 1 Files changed 8 +214 -38
coilyco-ops commented 2026-07-15 09:09:48 +00:00
Member
Copy link

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
Details
c1425fa1a8
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
pressure-test
Cold-read release pressure-test findings and coordination

  
sunday-sprint
Burn-down by Sunday 2026-06-07

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
pressure-test
sunday-sprint
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/ward!1362
No description provided.