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.2 KiB
Markdown
24 lines
1.2 KiB
Markdown
# BUG_REPORT: add-self-improvement-loop
|
|
|
|
## Findings
|
|
|
|
### Bug 1 (LOW): install.sh loop bootstrap is inside the `else` block
|
|
|
|
The loop creation commands are inside the `else` block of `if [ -d "$FRAMEWORK_DIR" ]`, which means they only run on fresh installs. If a user previously installed the framework before this change and runs `install.sh` again, they get "already installed" and the loop is NOT created. This is correct behavior -- `update.sh` handles the existing-user case.
|
|
|
|
**Severity:** LOW (by design)
|
|
**Fix:** None needed.
|
|
|
|
### Bug 2 (INFO): No `--project` flag consistency check
|
|
|
|
`install.sh` uses `--project "$FRAMEWORK_DIR"` while `update.sh` also uses `--project "$FRAMEWORK_DIR"`. Both are consistent. The `work_source.project` in the template is `"~/.automaton/"` (a string), but `--create-loop` doesn't use `work_source.project` -- it uses the `--project` flag. The runner reads `work_source.project` at tick time. No mismatch because `--project "$FRAMEWORK_DIR"` (which is `$HOME/.automaton`) and `work_source.project: "~/.automaton/"` resolve to the same path.
|
|
|
|
**Severity:** INFO (no bug)
|
|
**Fix:** None needed.
|
|
|
|
## Summary
|
|
|
|
No correctness bugs found. One LOW (by design) and one INFO.
|
|
|
|
**Verdict: CLEAN**
|