Rework dispatch capacity architecture beyond TTL mitigation #1192
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!1192
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-1191"
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 reworks dispatch capacity around visible workers instead of prelaunch intents. The launch broker still tracks intent and release state, but repo/global capacity now counts only running engineers, and failed visibility clears the launch intent immediately instead of waiting for TTL-based recovery.
Why: the old reservation shape treated a launch intent as active capacity, which could block repo slots before a visible engineer existed. The new split keeps intent, visibility, and terminal release separate so list, dispatch-health, and reap report the real state model.
listnow reports running engineers and launch intents separately.dispatch-healthreports launch intents independently of running workers.Tests:
ward exec test,ward exec lint, andpre-commit run --all-filesall passed locally.closes #1191
ward.workflow: pull-request-and-merge