Detect stale plan execution after the worktree changes
A developer reviews a plan, edits another package, then executes commands from the earlier plan.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Integrity checks · CLI design
Estimated field mix
- Developer tooling100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional internal tools team maintains eighteen packages. Engineers currently run everything because the affected-package script occasionally misses downstream consumers.
Setup prerequisites
- Create a local six-package fixture with a dependency cycle, shared compiler configuration, and two example changes.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- BMONO-101 · Document task inputs beyond package dependencies
- BMONO-102 · Parse workspace manifests without executing package scripts
- BMONO-103 · Handle cycles in the downstream impact graph
- BMONO-104 · Resolve renamed and deleted files against both revisions
- BMONO-105 · Explain why each selected command is necessary
- BMONO-106 · Make cache keys include generator versions and relevant environment
Acceptance criteria
- Bind plans to revision and relevant working-tree digests.
- Check the binding immediately before execution.
- Return a distinct stale-plan error with regeneration guidance.
Implementation constraints
- Do not discard or reset local edits.
Verification to include
- Execute an unchanged reviewed plan successfully.
- Modify a tracked input and reject the stale plan before spawning commands.
Deliverables
- Plan freshness guard.
Rollout and recovery
Require freshness for execution; allow explicit regeneration without modifying the checkout.
Value of the work
For the engineer: Practice graph analysis, reproducible commands, and safe developer-tool failure modes.
For the team: Produce an inspectable CI selection plan that avoids unnecessary work without silently skipping consumers.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.