Restore archived tasks, fix dashboard scroll-reset, bind ornith, add Playwright smoke test
- **Restore 82 completed tasks** from tasks/complete/ back to tasks/ top level (all <7 days old per the cleanup policy; premature bulk archive was fixed). - **Dashboard: fix scroll-reset on auto-refresh** — renderBoard rebuilds the board via innerHTML every 2s, destroying each column-body's scrollTop. Now snapshots column-body scrollTop + board.scrollLeft + view.scrollTop before rebuild and restores after (matched by PHASE_GROUPS index). - **Dashboard UI additions** (pre-existing unstaged work): approval section cards, transition buttons, inline artifact editor (textarea for writing missing SPEC/VERDICT/etc from the detail modal). - **Bind ornith as Implement model** — config.md: Model explicit to omlx/Ornith-1.0-35B-4bit-mlx, context window 32768. Interactive autopilot already used ornith via opencode default; now explicit. - **Fix cleanup stub** — automaton-cleanup.sh had a stale --project arg pointing at a pytest temp dir (test isolation leak). Rewired to point at ~/.automaton. - **Fix plist-isolation test** — test asserted host plist doesn't exist, but a real install creates it. Now snapshots mtime before run, asserts unchanged after (only a write during the test counts as bleed). - **New Playwright smoke test** (tests/test_dashboard_ui.py) — 2 tests: board renders tasks, column scroll survives auto-refresh tick. Verified the test fails without the scroll fix (scrollTop resets to 0). Skipped via importorskip when playwright is absent (main CI stays green). - **Clarify SI loop scope in README** — new-project onboarding section documents the framework-scoped self-improvement loop and options (leave/pause/create project loop). - **CHANGELOG** documents all changes including the known model-divergence gap (mde tasks marked complete but per-role model binding was never implemented).
This commit is contained in:
@@ -0,0 +1,13 @@
|
||||
# Adversarial Bug Report: fix-stale-task-mtime-proxy
|
||||
|
||||
## Attack Vectors Tested
|
||||
1. **Manual .state.lastedit manipulation**: A user could `touch .state.lastedit` to reset the timer — this is equivalent to `--touch` and is acceptable behavior
|
||||
2. **Deleted .state.lastedit**: `_get_edit_timestamp()` falls back to `.state` mtime — correct
|
||||
3. **Multiple tasks in implement phase**: `_touch_lastedit` called only for `primary` task (the first in-scope task) — acceptable, as the primary task is the one being edited
|
||||
4. **Clock skew**: Uses `time.time()` consistently — not a concern on local system
|
||||
5. **Stale task in single-task path**: Now correctly checked (was missing before this fix)
|
||||
|
||||
## Findings
|
||||
No bugs found.
|
||||
|
||||
## Verdict: PASS
|
||||
Reference in New Issue
Block a user