Restore archived tasks, fix dashboard scroll-reset, bind ornith, add Playwright smoke test
- **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).
This commit is contained in:
@@ -0,0 +1,72 @@
|
||||
# SPEC: add-self-improvement-loop
|
||||
|
||||
## Context
|
||||
|
||||
Task 6 created the self-improvement loop template at `templates/loops/self-improvement/loop.json`. This task wires it into `install.sh` and `update.sh` so the loop is default-on at install time (D21). Existing users who run `update.sh` get the loop bootstrapped idempotently.
|
||||
|
||||
## Non-Goals (deferred)
|
||||
|
||||
- Loop dashboard panel -> v1.1
|
||||
- Auto-approve for self-improvement loop -> never (D4)
|
||||
- Tier 2 context-sizing work -> picked up by the loop itself after first tick
|
||||
- `design/context-sizing/` skeleton -> v1.1 (the loop will create it when it picks up Tier 2 work)
|
||||
|
||||
## Requirements
|
||||
|
||||
### R1 -- `install.sh` creates and schedules the self-improvement loop
|
||||
|
||||
After the clone and guard registration, add:
|
||||
```bash
|
||||
# Bootstrap self-improvement loop (default-on, D21)
|
||||
python3 "$FRAMEWORK_DIR/scripts/status.py" --create-loop self-improvement \
|
||||
--from-template self-improvement --project "$FRAMEWORK_DIR" || true
|
||||
python3 "$FRAMEWORK_DIR/scripts/status.py" --install-schedule self-improvement \
|
||||
--interval 3600 --project "$FRAMEWORK_DIR" || true
|
||||
```
|
||||
|
||||
The `|| true` ensures install continues even if loop creation fails (e.g. Python not yet in PATH, or schedule installation fails on an unusual platform). The loop is optional; the framework works without it.
|
||||
|
||||
Print a message telling the user the loop is running and how to disable it:
|
||||
```bash
|
||||
echo ""
|
||||
echo "=== Self-Improvement Loop ==="
|
||||
echo "A self-improvement loop has been created and scheduled (runs every 3600s)."
|
||||
echo "It will tick against status.py --audit on this framework's own repo."
|
||||
echo "To disable: python3 ~/.automaton/scripts/status.py --pause-loop self-improvement --project ~/.automaton/"
|
||||
```
|
||||
|
||||
### R2 -- `update.sh` bootstraps the self-improvement loop idempotently
|
||||
|
||||
After the git pull and guard registration, add:
|
||||
```bash
|
||||
# Bootstrap self-improvement loop if not present (default-on, D21)
|
||||
if [ ! -d "$FRAMEWORK_DIR/loops/self-improvement" ]; then
|
||||
python3 "$FRAMEWORK_DIR/scripts/status.py" --create-loop self-improvement \
|
||||
--from-template self-improvement --project "$FRAMEWORK_DIR" || true
|
||||
python3 "$FRAMEWORK_DIR/scripts/status.py" --install-schedule self-improvement \
|
||||
--interval 3600 --project "$FRAMEWORK_DIR" || true
|
||||
echo "Created self-improvement loop (default-on). --pause-loop self-improvement to disable."
|
||||
fi
|
||||
```
|
||||
|
||||
### R3 -- Tests
|
||||
|
||||
Write `tests/test_self_improvement_loop.py` with:
|
||||
|
||||
1. `test_install_sh_creates_self_improvement_loop` -- verify `install.sh` contains `--create-loop self-improvement` and `--install-schedule self-improvement`
|
||||
2. `test_update_sh_bootstraps_self_improvement_loop` -- verify `update.sh` contains the idempotent bootstrap check
|
||||
3. `test_install_sh_has_opt_out_message` -- verify `install.sh` contains `--pause-loop self-improvement`
|
||||
4. `test_self_improvement_template_has_correct_fields` -- verify the template has `work_source.kind: audit`, `brakes.max_iterations: 10`, `blast_radius.use_worktree: true` (this may overlap with task 6 tests; if so, keep it as a regression guard)
|
||||
5. `test_create_loop_self_improvement_from_template` -- simulate `--create-loop self-improvement --from-template self-improvement --project <tmp>` and verify the loop dir, `loop.json`, `.state.loop`, and `.state.log` are created correctly
|
||||
|
||||
### R4 -- Documentation updates
|
||||
|
||||
- `CHANGELOG.md` under `[unreleased]`
|
||||
- `README.md` -- add a note in the Loop Engineering section that the self-improvement loop is default-on at install
|
||||
- `design/loops/technical.md` -- section 9 already documents the self-improvement template; add a note that install.sh creates it default-on
|
||||
|
||||
## Verification
|
||||
|
||||
- `bash -n scripts/install.sh scripts/update.sh` -- syntax check
|
||||
- `python3 -m pytest tests/test_self_improvement_loop.py -v`
|
||||
- `python3 -m pytest tests/ -q` -- full suite must remain green
|
||||
Reference in New Issue
Block a user