6b4bb4ac26
The next repo-local sweep target was ROADMAP #66: reminder/cron state could stay enabled after the associated lane had already finished, which left stale nudges firing into completed work. The fix teaches successful lane persistence to disable matching enabled cron entries and record which reminder ids were shut down on the finished event. Constraint: Preserve existing cron/task registries and add the shutdown behavior only on the successful lane-finished path Rejected: Add a separate reminder-cleanup command that operators must remember to run | leaves the completion leak unfixed at the source Confidence: high Scope-risk: narrow Reversibility: clean Directive: If cron-matching heuristics change later, update `disable_matching_crons`, its regression, and the ROADMAP closeout together Tested: cargo fmt --all --check; cargo clippy --workspace --all-targets -- -D warnings; cargo test --workspace; architect review APPROVE Not-tested: Cross-process cron/reminder persistence beyond the in-memory registry used in this repo |
||
|---|---|---|
| .. | ||
| api | ||
| commands | ||
| compat-harness | ||
| mock-anthropic-service | ||
| plugins | ||
| runtime | ||
| rusty-claude-cli | ||
| telemetry | ||
| tools | ||