- **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).
1.4 KiB
1.4 KiB
Documentation Review: task-status-reason
Summary
No DESIGN.md. Conducting ad-hoc review of code documentation for the status_reason feature.
Documentation Completeness
- Code documentation: Adequate —
status_reasonproperty has a docstring.parse_verdict_statuswas already documented. No DESIGN.md or deployment docs produced (proportional to the small change set). - User documentation: Not updated — the dashboard README (
automaton/dashboard/README.md) doesn't mention the status reason display. The new status_reason field in the API response is also undocumented. - API documentation: No formal API docs exist for the dashboard endpoints.
Issues Found
Issue 1: Dashboard README not updated for status reason display
- Severity: Low
- Description: The dashboard README at
automaton/dashboard/README.mddoesn't document that the detail panel now shows a status reason. This is a user-facing UI change without documentation. - Suggested Fix: Add a note to the README under "Detail Panel" section describing the status reason.
Issue 2: CHANGELOG entry missing bug fixes
- Severity: Low
- Description: The CHANGELOG correctly lists the status_reason feature and revoke buttons, but doesn't mention the REFEREE state fix (a consequence of Bug 2 fix from BUG_REPORT.md).
- Suggested Fix: Add a Fixed entry for the REFEREE state being unreachable.
Score
+3