Dispatch health and agent list disagree on active engineers, leaving stale starting records at capacity #1274
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!1274
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-1174"
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?
Unifies the active-engineer model behind
ward agent list, capacity checks, andward agent dispatch-health. Cleanup-needed prelaunch records and failed-before-start records stay visible for diagnosis, but they no longer count against active capacity.ward agent listnow keeps stale starting records visible withstatus: cleanup-neededand surfaces failed-before-start rows separately.dispatch-healthreports cleanup-needed and failed-before-start counts separately and reuses the same active count for capacity.ward agent reapand the launch capacity gate now consume the same active inventory model.ward exec test,ward exec lint,pre-commit run --all-files.