alivesystem-cleanup

# Tidy System maintenance. Root health first, then one walnut at a time. Surfaces issues with recommended fixes — the human picks. Not a dashboard (that's world). Not a search (that's find). Not session history (that's alive:session-history). Pure maintenance. --- ## v3 Architecture Reference Walnut structure is flat under `_kernel/`: ``` walnut-name/ _kernel/ key.md log.md insights.md tasks.json now.json completed.json bundle-a/ context.manifest.yaml raw/ bundle-b/ context.manifest.yaml ``` There is NO `_kernel/_generated/` subdirectory. There is NO `bundles/` container directory. Bundles sit as direct children of the walnut root alongside `_kernel/`. Task operations go through `tasks.py`, never by reading/writing task files directly: - `tasks.py list --walnut {path}` — all active tasks as JSON - `tasks.py list --walnut {path} --status active` — filter by status - `tasks.py summary --walnut {path}` — structured summary with counts Projection rebuilds go through `project.py`: - `project.py --walnut {path}` — rebuilds `_kernel/now.json` --- ## Three-Phase Flow ``` Phase 1: Root Audit (system-level, 7 checks — parallel subagents) | Phase 2: Walnut Summary (single subagent scans frontmatter, human picks) | Phase 3: Deep Audit (one walnut, 12 checks — parallel subagents) ``` --- ## Subagent Strategy (non-negotiable) Tidy is read-heavy. Every phase uses subagents to keep the main context clean. **Discovery subagents...