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:
Lap Tran
2026-06-26 10:05:18 -04:00
parent fe43b9e1fc
commit bc7daf8590
666 changed files with 15994 additions and 69 deletions
+1
View File
@@ -0,0 +1 @@
complete
+18
View File
@@ -0,0 +1,18 @@
# Bug Report: Project Migration Script
## Methodology
Reviewed migrate-project.sh and onboarding.md migration section.
## Acceptance Criteria
| # | Criterion | Result |
|---|-----------|--------|
| 1 | migrate-project.sh exists and is executable | ✅ |
| 2 | Correctly identifies identical vs customized files | ✅ |
| 3 | Customized files moved to extensions/ | ✅ |
| 4 | .agent.md and .rules.md preserved | ✅ |
| 5 | Onboarding detects stale projects | ✅ |
## Findings
1. **Minor**: Script skips symlinks with `-type f` — unlikely in practice.
## Verdict: PASS
+13
View File
@@ -0,0 +1,13 @@
# Doc Review: Project Migration Script
## Documents Checked
| Doc | Status |
|-----|--------|
| scripts/migrate-project.sh | ✅ Self-documenting output |
| prompts/onboarding.md | ✅ Migration Check section |
| README.md | ✅ Migration path documented |
## Findings
None.
## Verdict: PASS
+27
View File
@@ -0,0 +1,27 @@
# Implementation: Project Migration Script
## Summary
Created `scripts/migrate-project.sh` to clean up projects that were set up under the old copy-based model. Also updated `prompts/onboarding.md` to detect stale projects and offer migration.
## Changes Made
### `scripts/migrate-project.sh`
Shell script that:
1. Scans `{project}/.automaton/` for files that now live in `~/.automaton/`
2. Files **identical to global** → deleted (framework provides them)
3. Files **different from global** → moved to `.automaton/extensions/`
4. Preserves `.agent.md` and `.rules.md` as-is
5. Reports what was deleted, moved, and kept
### `prompts/onboarding.md`
Added "Migration Check" section at the end:
- During onboarding, checks if project has stale framework file copies
- Identifies files beyond `.agent.md` and `.rules.md`
- Offers to run `migrate-project.sh` or provides manual instructions
## Files Created
- `scripts/migrate-project.sh` — migration shell script (125 lines)
## Files Modified
- `prompts/onboarding.md` — added migration detection section
+3
View File
@@ -0,0 +1,3 @@
# Review
- **Status**: approved
- **Timestamp**: 2026-06-13T18:04:51.992742
+34
View File
@@ -0,0 +1,34 @@
# SPEC: Project Migration Script for Additive Extension Model
## Overview
After switching to the additive extension model, existing projects have stale copies of framework files in their `{project}/.automaton/` directories. These need to be cleaned up.
## Context
Under the old model, framework files (prompts, contracts, scripts) were copied into the project's `.automaton/`. Under the new model, the project should only contain `.agent.md`, `.rules.md`, and optionally an `extensions/` directory. Everything else comes from `~/.automaton/`.
## Changes
### 1. `scripts/migrate-project.sh`
Script that takes a project path and:
1. Scans `{project}/.automaton/` for files that now live in `~/.automaton/`
2. For each matching file:
- **Identical to global** → delete (framework provides them)
- **Different from global** → move to `.automaton/extensions/`
3. Preserves `.agent.md` and `.rules.md` as-is
4. Reports what was deleted, moved, and kept
### 2. `prompts/onboarding.md`
Add a section at the top that checks if migration is needed:
- If project has prompt/contract/script copies in `.automaton/`, offer to run migration
## Acceptance Criteria
- [ ] `scripts/migrate-project.sh` exists and is executable
- [ ] Script correctly identifies identical vs customized files
- [ ] Customized files are moved to `extensions/`, not deleted
- [ ] `.agent.md` and `.rules.md` are never touched
- [ ] Onboarding detects stale projects and offers migration
+17
View File
@@ -0,0 +1,17 @@
# VERDICT: Project Migration Script
## Status: PASS
## Summary
Created migrate-project.sh to clean up stale framework file copies from old-model projects. Onboarding detects stale projects and offers migration.
## Phase Results
| Phase | Result |
|-------|--------|
| Implementation | ✅ PASS |
| Bug Find | ✅ PASS (1 minor finding) |
| Adversarial Bug Find | ⏭️ Skipped (shell script, no security surface) |
| Doc Review | ✅ PASS |
## Final Verdict
**PASS** — All acceptance criteria met. Migration path is clear and safe.