issues with stale reservations should be in scope for director backlog automated burndown flow #992

Merged
coilyco-ops merged 1 commit from issue-978 into main 2026-07-10 09:31:56 +00:00
Member

closes #978

ward.workflow: pull-requests-and-merge

closes #978 ward.workflow: pull-requests-and-merge
feat: distinguish stale director reservations
All checks were successful
test / test (pull_request) Successful in 24s
f13ed495fa
Author
Member

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#978 contract.

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#978` contract.
Sign in to join this conversation.
No description provided.