feat(FN-1646): add stale-spec guard to prevent execution of outdated tasks
- Add spec-staleness evaluator to check task specification age before execution - Guard executor startup and resume to prevent running tasks with stale specs - Guard scheduler dispatch to skip stale tasks and move them back to triage - Add comprehensive tests for spec staleness detection (7d/14d thresholds) - Add getFusionDir mock for executor staleness check tests
This commit is contained in:
5
.changeset/retriage-stale-spec-before-execution.md
Normal file
5
.changeset/retriage-stale-spec-before-execution.md
Normal file
@@ -0,0 +1,5 @@
|
||||
---
|
||||
"@gsxdsm/fusion": patch
|
||||
---
|
||||
|
||||
Prevent execution from starting with stale specifications. When spec staleness enforcement is enabled via `specStalenessEnabled: true` and `specStalenessMaxAgeMs` settings, tasks whose PROMPT.md age exceeds the configured threshold are automatically moved back to triage with `status: "needs-respecify"` before execution begins. This guard applies both at scheduler dispatch and executor startup/resume, preventing manual moves, orphan resume, and unpause paths from bypassing the policy. Behavior is unchanged when enforcement is disabled.
|
||||
Reference in New Issue
Block a user