- **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
Bug Report: Multi-Agent Support
Methodology
Reviewed claim/release/next-available/available commands, .state.lock files, Agent Configuration in .agent.md, and single-agent zero-overhead guarantee.
Acceptance Criteria
| # | Criterion | Result |
|---|---|---|
| 1 | Single-agent mode has zero behavioral change | ✅ |
| 2 | --claim creates .state.lock atomically |
✅ |
| 3 | --claim refuses if already claimed (non-expired) |
✅ |
| 4 | --claim overclaims if expired |
✅ |
| 5 | --release removes .state.lock |
✅ |
| 6 | --release refuses if wrong agent |
✅ |
| 7 | --next-available finds highest-priority unclaimed task |
✅ |
| 8 | --available lists all unclaimed tasks for agent role |
✅ |
| 9 | Agent Configuration in .agent.md activates multi-agent |
✅ |
| 10 | .state.lock excluded from --validate-folder |
✅ |
| 11 | Completed tasks auto-release locks | ✅ |
Findings
-
Minor: Lock timeout defaults to 30 minutes. The configurable timeout parsing (
5m,10m, etc.) from.agent.mdworks but is case-sensitive —30Mwould not be parsed correctly. Minor UX issue. -
Minor: The
--as-coordinatorflag and--forceflag for coordinator override are parsed but the coordinator role validation is limited — any agent can potentially pass--agent orchestratorwithout verification. This is acceptable since agent identity is self-reported in the current design.