- **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.9 KiB
RESEARCH: move-completed-tasks-to-complete-folder
Objective
When --transition complete is called, move the task directory from tasks/<name>/ to tasks/complete/<name>/. Keep --list and --audit showing only active tasks. Allow --task <name> to find completed tasks by fallback.
Current Behavior
--transition complete only writes the .state file to "complete". The task directory stays in tasks/<name>/ alongside active tasks, cluttering the listing and audit.
Design
_task_dir fallback
Add a fallback in _task_dir: if tasks/<name>/ doesn't exist, check tasks/complete/<name>/. This ensures --task <name> and --transition still work for completed tasks.
cmd_transition move
After _write_state(task_path, target), if target == "complete", compute the tasks root and move task_path to tasks/complete/<name>/. Create tasks/complete/ if it doesn't exist. Refuse if a completed task with the same name already exists.
_all_task_dirs unchanged
Do NOT scan tasks/complete/ in _all_task_dirs. Completed tasks are out of sight from --list and --audit. The fallback in _task_dir is sufficient for targeted lookups.
cmd_create_task
_task_dir already returns the completed path via fallback, so cmd_create_task will see task_path.exists() and refuse with "already exists". No separate check needed.
Risks
- Audit:
--audituses_all_task_dirswhich doesn't scantasks/complete/, so completed tasks are invisible to audit. This is the desired behavior. - Loop references: If a loop's
current_taskpoints to a completed task, the audit at line 954 checks_task_dir(ltask, args.project).exists()which will find the completed task via fallback. Correct. --transitionon completed tasks:_task_dirfinds the completed task,_require_statereads"complete", andLEGAL_TRANSITIONS.get("complete", [])returns[], so any transition is refused. Correct.