Lap Tran
bc7daf8590
- **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).
24 lines
1.1 KiB
Markdown
24 lines
1.1 KiB
Markdown
# BUG_REPORT: move-completed-tasks-to-complete-folder
|
|
|
|
## Findings
|
|
|
|
### Bug 1 (LOW): `cmd_create_task` error message references old path
|
|
|
|
When creating a task with the same name as a completed task, the error message uses `task_path` which is now the completed task path (via `_task_dir` fallback). The message says "already exists at {task_path}" which shows the `tasks/complete/<name>/` path instead of `tasks/<name>/`. This is correct behavior but could be confusing to the user.
|
|
|
|
**Severity:** LOW (accurate but surprising path)
|
|
**Fix:** None needed for v1. The error message is factually correct.
|
|
|
|
### Bug 2 (INFO): Subtask paths not covered by fallback
|
|
|
|
The `_task_dir` fallback only applies to non-subtask paths (no "/" in the name). If a subtask is completed, `_task_dir` won't find it in `tasks/complete/<parent>/subtasks/<name>/`. However, subtasks are never independently transitioned to `complete` -- they are part of their parent task's lifecycle.
|
|
|
|
**Severity:** INFO (by design)
|
|
**Fix:** None needed.
|
|
|
|
## Summary
|
|
|
|
No correctness bugs found. One LOW (cosmetic error message) and one INFO (by design).
|
|
|
|
**Verdict: CLEAN**
|