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/changelog/.state

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

tasks/complete/changelog/BUG_REPORT.md

@@ -0,0 +1,16 @@
+# Bug Report: Changelog and Release Notes Process
+
+## Methodology
+Reviewed CHANGELOG.md and .rules.md entries.
+
+## Acceptance Criteria
+| # | Criterion | Result |
+|---|-----------|--------|
+| 1 | CHANGELOG.md exists with [unreleased] header | ✅ |
+| 2 | .rules.md mentions changelog updates | ✅ |
+| 3 | Format clean enough for release notes | ✅ |
+
+## Findings
+None.
+
+## Verdict: PASS

tasks/complete/changelog/DOC_REVIEW.md

@@ -0,0 +1,12 @@
+# Doc Review: Changelog and Release Notes Process
+
+## Documents Checked
+| Doc | Status |
+|-----|--------|
+| CHANGELOG.md | ✅ Created with [unreleased] |
+| .rules.md | ✅ Changelog process documented |
+
+## Findings
+None.
+
+## Verdict: PASS

tasks/complete/changelog/IMPLEMENTATION.md

@@ -0,0 +1,24 @@
+# Implementation: Changelog and Release Notes Process
+
+## Summary
+
+Created a root-level CHANGELOG.md and codified the changelog update process in `.rules.md`.
+
+## Changes Made
+
+### `CHANGELOG.md`
+Created at `~/.automaton/CHANGELOG.md` with:
+- `[unreleased]` header
+- `### Added` and `### Changed` sections
+- Entries for all completed tasks (additive-extension-model, framework-self-enforcement, changelog, framework-audit)
+
+### `.rules.md`
+Added "Changelog" section:
+- When a task reaches Resolution (VERDICT.md written), append an entry to CHANGELOG.md
+- Format: `- description (#task-name)` under the appropriate section
+
+## Files Created
+- `CHANGELOG.md` — root-level changelog
+
+## Files Modified
+- `.rules.md` — added changelog rules

tasks/complete/changelog/REVIEW.md

@@ -0,0 +1,3 @@
+# Review
+- **Status**: approved
+- **Timestamp**: 2026-06-13T18:00:58.458316

tasks/complete/changelog/SPEC.md

@@ -0,0 +1,33 @@
+# SPEC: Changelog and Release Notes Process
+
+## Overview
+
+There's no changelog or release note process. Completed tasks produce a VERDICT.md but there's no aggregate record of what changed. This makes it hard to generate release notes or see the project's history at a glance.
+
+## Changes
+
+### 1. `CHANGELOG.md` at `~/.automaton/`
+
+Root-level changelog file with entries appended on task completion:
+
+```markdown
+# Changelog
+
+## [unreleased]
+
+### Added
+- description (#task-name)
+
+### Fixed
+- description (#task-name)
+```
+
+### 2. Update `.rules.md`
+
+Add a rule: "When a task reaches Resolution (VERDICT.md written), append an entry to CHANGELOG.md."
+
+## Acceptance Criteria
+
+- [ ] `~/.automaton/CHANGELOG.md` exists with [unreleased] header
+- [ ] `.rules.md` mentions changelog updates as part of task completion
+- [ ] Format is clean enough to use as release notes source

tasks/complete/changelog/VERDICT.md

@@ -0,0 +1,16 @@
+# VERDICT: Changelog and Release Notes Process
+
+
+## Status: PASS
+## Summary
+Created CHANGELOG.md at root level. Added changelog update rules to .rules.md.
+
+## Phase Results
+| Phase | Result |
+|-------|--------|
+| Implementation | ✅ PASS |
+| Bug Find | ✅ PASS |
+| Doc Review | ✅ PASS |
+
+## Final Verdict
+**PASS** — All acceptance criteria met. Format is standard keepachangelog.