Stop director dispatch from exceeding the global engineer limit #1369
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!1369
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-1016"
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 tightens engineer admission so a launch waits for Docker to reflect the new container before the capacity lock is released, and it makes the director list surface derive its count from the same live running set the dispatcher uses.
WARD_CONFIG_REF=file://$PWD/.ward/ward-kdl go test ./cmd/ward -run 'TestEngineerContainerLimit|TestLaunchAgentContainerRejectsAtLimitWithoutReservation|TestEngineerCapacityLockSerializesConcurrentAdmissions|TestEngineerCapacityLockWaitsForVisibleContainerBeforeRelease|TestAgentRunningEngineerFromInspectIncludesReservation|TestFormatAgentListCapacityNotesUnavailableSource'WARDED_WORKFLOW: blocked 🛑
details
manual close/update snapshot at 2026-07-15T09:41:17Z is newer than the latest ward acknowledgement at 2026-07-15T09:14:23Z
This action is blocked until the feedback is visibly acknowledged.
— Codex, via
ward agent