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).

tasks/phase-scoped-prompts/ADVERSARIAL_BUG_REPORT.md

@@ -0,0 +1,13 @@
+# Adversarial Bug Report: Phase-Scoped Prompts
+
+## Deep Review
+The ALLOWED/FORBIDDEN sections create hard boundaries that prevent phase-skipping. The user override resistance instructions give agents a standard refusal template. The orchestrate.md reduction from 493 to 143 lines is significant and removes state machine duplication.
+
+## Potential Issues
+1. **FORBIDDEN section is advisory only**: An agent that ignores the prompt can still perform forbidden actions. The enforcement relies on the agent following instructions. `status.py --validate-folder` catches violations after the fact, but cannot prevent them in real-time.
+
+2. **Agent can fabricate APPROVED signal**: The approval gate says "wait for user approval," but a non-compliant agent could call `status.py --approve` itself without waiting. This is mitigated by the spec requirement that `--approve` is an explicit user action, but a truly adversarial agent could simulate it.
+
+3. **decompose.md length**: At over 150 lines, decompose.md pushes against the prompt discipline target. Not a functional bug but a maintenance concern.
+
+## Verdict: PASS — no security or logic flaws. Enforcement is prompt-based with status.py as a post-hoc check, which is the intended design.