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 @@
|
||||
complete
|
||||
@@ -0,0 +1 @@
|
||||
research:approved|2026-06-15T18:32:07.362325+00:00|user
|
||||
@@ -0,0 +1,10 @@
|
||||
# Adversarial Bug Report: README and Upgrade Docs
|
||||
|
||||
## Deep Bugs Found: 0
|
||||
|
||||
Documentation-only changes. No code paths altered.
|
||||
|
||||
## Pre-existing Issues (not in scope but noted)
|
||||
1. `upgrade.sh` silently swallows `status.py --upgrade` failures
|
||||
2. Pre-commit hook doesn't handle bare repos or worktrees
|
||||
3. `_infer_state_from_artifacts` heuristic bug (SPEC.md-only → bug_find instead of research)
|
||||
@@ -0,0 +1,10 @@
|
||||
# Bug Report: README and Upgrade Docs
|
||||
|
||||
## Bugs Found: 0
|
||||
|
||||
No bugs found. Changes are documentation-only and all tests pass.
|
||||
|
||||
## Issues Noted (pre-existing, not introduced by this task)
|
||||
1. `upgrade.sh` uses `|| true` so `status.py --upgrade` failure is silently swallowed
|
||||
2. `upgrade.sh` doesn't verify python3 is available
|
||||
3. Pre-commit hook assumes `.git/hooks/` path (doesn't handle bare repos/worktrees)
|
||||
@@ -0,0 +1,16 @@
|
||||
# Doc Review: README and Upgrade Docs
|
||||
|
||||
## Review Summary
|
||||
|
||||
All documentation changes are accurate and consistent with the v2.0 enforcement implementation.
|
||||
|
||||
## Checklist
|
||||
- [x] `--project` flag present on all status.py command examples
|
||||
- [x] `--can-edit` 4 modes documented with examples
|
||||
- [x] `--upgrade` documented for untracked tasks
|
||||
- [x] Three enforcement layers documented
|
||||
- [x] Upgrade process is step-by-step with commands
|
||||
- [x] Pre-commit hook installation in both Project Setup and Upgrading sections
|
||||
- [x] Key Components updated with all new files
|
||||
- [x] Untracked tasks section explains the refusal behavior
|
||||
- [x] No broken markdown or formatting issues
|
||||
@@ -0,0 +1,31 @@
|
||||
# Implementation: README and Upgrade Docs
|
||||
|
||||
## Changes Made
|
||||
|
||||
### 1. Quick Reference (README.md)
|
||||
- Added `--project /path/to/project` to every `status.py` command example
|
||||
- Added `--upgrade` and `--can-edit` commands with all 4 modes
|
||||
- Added note about `--project` being required with multiple projects
|
||||
|
||||
### 2. Untracked Tasks Section
|
||||
- Documents that tasks without `.state` files are refused by all commands
|
||||
- Shows how to upgrade single tasks or all tasks at once
|
||||
|
||||
### 3. Enforcement Section
|
||||
- Documents 3 enforcement layers: harness pre-edit hook, git pre-commit hook, prompt rules
|
||||
- References `contracts/harness-integration.md` for details
|
||||
|
||||
### 4. Upgrading Section (rewritten)
|
||||
- "Updating the framework" (git pull) separated from "Upgrading to v2.0" (upgrade.sh)
|
||||
- Step-by-step upgrade.sh usage with what it does
|
||||
- Manual pre-commit hook installation
|
||||
- `--can-edit` verification step
|
||||
|
||||
### 5. Project Setup Section
|
||||
- Option B (Manual Way) now includes pre-commit hook installation
|
||||
|
||||
### 6. Key Components
|
||||
- Added `scripts/git-hooks/pre-commit`
|
||||
- Added `contracts/harness-integration.md`
|
||||
- Added `plugins/automaton-guard/`
|
||||
- Updated `scripts/status.py` description to mention `--can-edit`
|
||||
@@ -0,0 +1,23 @@
|
||||
# README and Upgrade Documentation Update
|
||||
|
||||
## Goal
|
||||
Update README.md with complete, clear documentation for v2.0 features: `--project` flag, `--upgrade`, `--can-edit` project-level mode, pre-commit hook installation, and the full upgrade process for existing projects.
|
||||
|
||||
## Requirements
|
||||
- Quick Reference includes `--project` on every command
|
||||
- `--can-edit` project-level modes documented with examples
|
||||
- `--upgrade` documented for untracked tasks
|
||||
- Enforcement layers section (pre-edit hook, pre-commit hook, prompt rules)
|
||||
- Upgrade process for existing projects (step-by-step for newcomers)
|
||||
- Pre-commit hook installation instructions in Project Setup and Upgrading sections
|
||||
- Key Components updated with new files
|
||||
|
||||
## Acceptance Criteria
|
||||
- [x] All `status.py` examples include `--project`
|
||||
- [x] `--can-edit` modes documented
|
||||
- [x] `--upgrade` for untracked tasks documented
|
||||
- [x] Three enforcement layers documented
|
||||
- [x] Upgrade process for existing projects is step-by-step
|
||||
- [x] Pre-commit hook installation in both Project Setup and Upgrading
|
||||
- [x] Key Components updated
|
||||
- [x] 200 tests pass
|
||||
@@ -0,0 +1,16 @@
|
||||
# Verdict: readme-upgrade-docs
|
||||
|
||||
## Status: PASS
|
||||
**Completion Date**: 2026-06-15
|
||||
|
||||
## Summary
|
||||
Updated README.md with comprehensive v2.0 documentation: `--project` flag on all commands, `--can-edit` modes, `--upgrade` for untracked tasks, three enforcement layers, full upgrade process for existing projects, pre-commit hook installation, and updated Key Components.
|
||||
|
||||
## Findings
|
||||
- All 6 acceptance criteria met
|
||||
- 200 tests pass
|
||||
- Documentation-only change, no code bugs possible
|
||||
- Pre-existing issues in upgrade.sh noted but not in scope
|
||||
|
||||
## Score
|
||||
+10
|
||||
Reference in New Issue
Block a user