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/port-pi-guard/.state

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

tasks/port-pi-guard/ADVERSARIAL_BUG_REPORT.md

@@ -1,14 +0,0 @@
-# Adversarial Bug Report — port-pi-guard
-
-## Attack Vectors
-1. **Status.py not available**: The plugin falls open (allows all edits) — can this be triggered maliciously?
-2. **Command injection in execSync**: Is the `cmd` string safe from injection?
-3. **Bash tool regex bypass**: Can write operations evade the bash tool pattern check?
-
-## Findings
-- Fall-open when status.py is missing is acceptable for offline/local use — an attacker who can remove status.py already has system access
-- `execSync` uses hardcoded command parts + `process.cwd()` — no user input in the command string, safe
-- Bash regex could be evaded with alternative write commands (e.g., `install`, `cat >`), but this is a best-effort check and the guard primarily targets edit/write tools
-
-## Verdict
-No exploitable vulnerabilities found.

tasks/port-pi-guard/BUG_REPORT.md

@@ -1,16 +0,0 @@
-# Bug Report — port-pi-guard
-
-## Review Scope
-Pi dev guard plugin (guard.ts, package.json), integration in register-guards.sh and harness-integration.md.
-
-## Findings
-
-### No Critical Bugs Found
-The guard.ts properly implements the pi ExtensionAPI pattern with `pi.on("tool_call", ...)`. It correctly intercepts edit/write/bash tools, calls status.py, and returns block responses. The fallback to allowing when status.py is unavailable is reasonable (fail-open for offline scenarios).
-
-### Minor Observations
-- Lines 38-40 contain unreachable dead code (the import is shadowed by the child_process import below)
-- The bash tool regex check (`\b(write|tee|cp|mv|sed\b.*-i|dd\b.*of=)\b`) could miss some write patterns
-
-## Verdict
-No blocking bugs. Ready for adversarial review.

tasks/port-pi-guard/DOC_REVIEW.md

@@ -1,14 +0,0 @@
-# Doc Review — port-pi-guard
-
-## Documentation Reviewed
-- IMPLEMENTATION.md (task folder)
-- SPEC.md
-- guard.ts header comments
-- package.json description
-- contracts/harness-integration.md (Pi Dev matrix entry)
-
-## Findings
-Documentation is accurate and complete. The guard.ts has a clear header comment describing its purpose and installation. The IMPLEMENTATION.md correctly documents the new files and integration points.
-
-## Verdict
-Documentation is satisfactory. No changes needed.

tasks/port-pi-guard/IMPLEMENTATION.md

@@ -1,18 +0,0 @@
-# Port Guard to Pi Dev Implementation
-
-## Summary
-Created pi dev extension at `plugins/automaton-guard-pi/` using the `@earendil-works/pi-coding-agent` API.
-
-## Changes
-
-### New Files
-- `plugins/automaton-guard-pi/guard.ts` — Pre-edit guard for pi dev harness
-  - Intercepts `tool_call` events for edit/write/bash tools
-  - Calls `status.py --can-edit` before allowing file modifications
-  - Handles stale task detection with user notification
-  - Uses `child_process.execSync` for status.py invocation
-- `plugins/automaton-guard-pi/package.json` — Package manifest with pi-coding-agent peer dependency
-
-### Integration
-- `scripts/register-guards.sh` — Detects `pi` in PATH and installs the guard via `pi install`
-- `contracts/harness-integration.md` — Updated enforcement matrix to include Pi Dev

tasks/port-pi-guard/SPEC.md

@@ -1 +0,0 @@
-# Port Guard to Pi Dev\n\nCreate pi dev extension at plugins/automaton-guard-pi/ using @earendil-works/pi-coding-agent API.

tasks/port-pi-guard/VERDICT.md

@@ -1,13 +0,0 @@
-# Verdict — port-pi-guard
-
-## Status: PASS
-
-## Summary
-All phases completed successfully:
-1. **Implement**: Created pi dev guard plugin at plugins/automaton-guard-pi/ with full ExtensionAPI integration
-2. **Bug Find**: No critical bugs found
-3. **Adversarial Bug Find**: No security vulnerabilities found
-4. **Doc Review**: Documentation accurate and complete
-
-## Final Assessment
-Task satisfies all SPEC.md requirements. Marking complete.