CI / build (push) Has been cancelled
Batch 1 (High severity): - Bug 1: --audit cat3 now checks .automaton/tasks/ paths - Bug 4: Verdict PASS/FAIL uses structured ## Status: line parsing - Bug 5: register-guards.sh checks .json/.jsonc, writes plugin key, strips comments - Bug 7: --can-edit/--scope-check path prefix uses os.sep boundary Batch 2 (Medium/Low severity): - Bug 2: migrate-project.sh find command parentheses for -prune binding - Bug 3: vram_detect model prefix matching with known-suffix whitelist - Bug 6: dashboard reads .state file before artifact heuristic fallback - Bug 8: removed wildcard CORS, added security headers (nosniff, DENY) - Bug 9: stale-task detection uses .state.lastedit instead of .state mtime - Bug 10: TEST_PLAN.md maps to test_design (was implement) 249 tests pass (up from 235). All 10 tasks driven through full workflow to completion.
1.4 KiB
1.4 KiB
Code Review: fix-stale-task-mtime-proxy
Reviewed Files
scripts/status.py(_get_edit_timestamp(),_touch_lastedit(),cmd_can_edit(),cmd_same_session(),cmd_touch(),NON_ARTIFACT_FILES)
Changes
- Added
.state.lasteditfile as the stale-task timer source _touch_lastedit()called on ALLOWED--can-editresponses_get_edit_timestamp()reads.state.lasteditwith fallback to.statemtime- Added staleness check to single-task
--can-edit --taskpath --touchnow touches.state.lasteditinstead of.state
Analysis
- Correctness: Using
.state.lastedit(touched on actual edit activity) is a better proxy for staleness than.statemtime (which only reflects phase transitions) - Backward compatibility: Falls back to
.statemtime when.state.lasteditdoesn't exist - Non-artifact:
.state.lasteditcorrectly added toNON_ARTIFACT_FILESto avoid being treated as a phase artifact - Single-task path: Adding staleness check to
--can-edit --taskmakes enforcement consistent across both code paths --touchcommand: Updated to touch.state.lastedit— consistent with the new activity tracking model
Verdict: PASS
The fix is well-structured, maintains backward compatibility, and correctly addresses the mtime proxy issue. Tests cover creation, staleness detection, and fallback behavior.