Director surface dispatch broker address refuses connections, blocking sibling warded dispatch #1257
No reviewers
Labels
No labels
burndown-2026-06
pressure-test
sunday-sprint
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/ward!1257
Loading…
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?
Fix stale broker fallbacks on read-only director surfaces.
The director surface now probes broker reachability before choosing the brokered dispatch path. If the advertised TCP broker is unreachable,
warded engineerand PR workflow verbs fall back to the direct path instead of failing on TCP refusal, and the preflight error now names an unreachable broker when no fallback exists.warded engineerno longer hard-fails on a dead broker address.ward agent pr statusand PR merge/rerun verbs degrade to direct Forgejo access when broker forwarding is not available.Closes #1240
ward.workflow: pull-request-and-merge