Fix brokered dispatch fallback when the host broker is unavailable #1272
No reviewers
Labels
No labels
burndown-2026-06
pressure-test
sunday-sprint
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/ward!1272
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-1240"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This narrows broker forwarding so read-only surfaces make one real broker request and treat an unavailable broker as a fallback signal instead of surfacing the raw TCP refusal. PR/workflow reads now fall back to the direct path when the host broker is absent, and list/logs do the same.
ward exec test,ward exec vet,ward exec lint.closes #1240
ward.workflow: pull-request-and-merge