Archive completed tasks, add cleanup commands, self-documenting dashboard UI

- Archive 79 completed framework-dev tasks from tasks/ -> tasks/complete/
- status.py: add --cleanup-done and --install-cleanup-schedule commands
- Add scripts/automaton-cleanup.sh for periodic task archiving
- Dashboard: rename 'Background' tab -> 'Agent', 'Cleanup' agent -> 'Completed Task Archiver', remove redundant group headers and pill badges, dim inactive agent placeholders
- .rules.md: add Self-Documenting UI Names rule
- New tests: test_cleanup_done.py, expanded test_app.py and test_task.py

tasks/complete/readme-upgrade-docs/.state

@@ -0,0 +1 @@
+complete

tasks/complete/readme-upgrade-docs/.state.approvals

@@ -0,0 +1 @@
+research:approved|2026-06-15T18:32:07.362325+00:00|user

tasks/complete/readme-upgrade-docs/ADVERSARIAL_BUG_REPORT.md

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

tasks/complete/readme-upgrade-docs/BUG_REPORT.md

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

tasks/complete/readme-upgrade-docs/DOC_REVIEW.md

@@ -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

tasks/complete/readme-upgrade-docs/IMPLEMENTATION.md

@@ -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`

tasks/complete/readme-upgrade-docs/SPEC.md

@@ -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

tasks/complete/readme-upgrade-docs/VERDICT.md

@@ -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