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

Make broker-unavailable failures actionable #1354

Merged
coilyco-ops merged 1 commit from issue-1342 into main 2026-07-15 08:33:26 +00:00
Conversation 0 Commits 1 Files changed 7 +248 -69
coilyco-ops commented 2026-07-15 08:30:40 +00:00
Member
Copy link

This change makes broker contact failures actionable across director surfaces. Read-only brokered commands now report a typed broker diagnostic instead of falling back to local launch/list behavior, and the diagnostics name the broker address source, connection failure, and a single remediation step.

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

  • Added broker-unreachable and broker-timeout diagnostics, then wired them through ref dispatch, list/ps, stop, PR workflow, and freeform engineer forwarding.
  • Added refused-connection and timeout fixtures, plus a capacity-defer wording check so capacity backpressure stays distinct from broker failures.
  • Live host broker health was not verified from the sealed engineer container; verification was limited to unit fixtures and broker-response tests.
This change makes broker contact failures actionable across director surfaces. Read-only brokered commands now report a typed broker diagnostic instead of falling back to local launch/list behavior, and the diagnostics name the broker address source, connection failure, and a single remediation step. closes #1342 ward.workflow: pull-request-and-merge - Added `broker-unreachable` and `broker-timeout` diagnostics, then wired them through ref dispatch, list/ps, stop, PR workflow, and freeform engineer forwarding. - Added refused-connection and timeout fixtures, plus a capacity-defer wording check so capacity backpressure stays distinct from broker failures. - Live host broker health was not verified from the sealed engineer container; verification was limited to unit fixtures and broker-response tests.
Make broker-unavailable failures actionable
All checks were successful
test / test (pull_request) Successful in 2m12s
Details
c4e2dd43bb
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!1354
No description provided.