Reproduce the director broker exit after a Docker name-conflict 125 #1385
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!1385
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-1244"
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 adds a synthetic regression for the brokered Docker name-conflict 125 path and keeps the host dispatch broker alive after the failure. The test now matches the incident shape more closely by exercising
exit status 125explicitly, so we can prove the broker/request lifetime behavior without a live host repro.go test ./....closes #1244
ward.workflow: pull-request-and-merge