issues with stale reservations should be in scope for director backlog automated burndown flow #992
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!992
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-978"
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?
closes #978
ward.workflow: pull-requests-and-merge
verdict: pass
confidence: medium
summary: The patch moves stale reservation handling into the director backlog refresh, keeps fresh holds parked, and treats stale holds as queued work. The included tests cover fresh, stale, and released reservation states plus lane counting.
findings:
conclusion: Review passes PR #992. The change makes stale reservations visible to automated burndown without dispatching over fresh holds, which satisfies the core
ward#978contract.