[Maintain] Simplify MAINTAIN protocol from 4 phases to 2

Problems with the old protocol:
- 4 phases x 3-way consultation = 12 consultation calls per run
- Runs stalled (0006 never completed past audit)
- Last completed run was 4 months ago
- Audit findings went stale before clean phase ran

Changes:
- Collapse audit/clean/sync/verify into single "maintain" phase
- Keep one 3-way review during maintain, one before PR (review phase)
- Fix tool commands for pnpm monorepo (was npm)
- Simplify maintenance run template
- Remove per-phase prompts (audit.md, clean.md, sync.md, verify.md)
- Add consolidated maintain.md and review.md prompts
- Update both codev/ and codev-skeleton/
- Protocol version bumped to 3.0.0

Author: waleedkadous

codev-skeleton/protocols/maintain/builder-prompt.md

@@ -7,7 +7,7 @@ You are executing the MAINTAIN protocol to clean up and synchronize the codebase
 You are running in SOFT mode. This means:
 - You follow the MAINTAIN protocol yourself (no porch orchestration)
 - The architect monitors your work and verifies you're adhering to the protocol
-- Work through each phase methodically
+- Work through each step methodically
 {{/if}}
 
 {{#if mode_strict}}
@@ -20,36 +20,37 @@ You are running in STRICT mode. This means:
 ### ABSOLUTE RESTRICTIONS (STRICT MODE)
 - **NEVER edit `status.yaml` directly** — only porch commands may modify project state
 - **NEVER call `porch approve` without explicit human approval** — only run it after the architect says to
-- **NEVER skip the 3-way review** — always follow porch next → porch done cycle
 {{/if}}
 
 ## Protocol
 Follow the MAINTAIN protocol: `codev/protocols/maintain/protocol.md`
 
 ## MAINTAIN Overview
-The MAINTAIN protocol handles codebase hygiene:
 
-1. **Audit Phase**: Scan for dead code, unused dependencies, stale docs
-2. **Clean Phase**: Remove identified cruft, verify build
-3. **Sync Phase**: Update documentation (arch.md, lessons-learned.md, CLAUDE.md)
-4. **Verify Phase**: Run full test suite, confirm health
+Two phases:
+1. **Maintain**: Single pass — audit findings, clean dead code, sync docs, verify build
+2. **Review**: Create PR with 3-way consultation
 
 ## Key Rules
 - Use soft deletion (move to `codev/maintain/.trash/`)
-- Always verify build passes after removals
+- Verify build passes after each removal (`cd packages/codev && pnpm build && pnpm test`)
 - Update documentation to match current architecture
 - Don't remove anything actively used
+- One removal at a time — commit after each
+- Document every deletion with justification
+- Never use `git add -A` or `git add .`
 
 ## Handling Flaky Tests
 
 If you encounter **pre-existing flaky tests** (intermittent failures unrelated to your changes):
 1. **DO NOT** edit `status.yaml` to bypass checks
 2. **DO NOT** skip porch checks or use any workaround to avoid the failure
 3. **DO** mark the test as skipped with a clear annotation (e.g., `it.skip('...') // FLAKY: skipped pending investigation`)
-4. **DO** document each skipped flaky test in your review under a `## Flaky Tests` section
+4. **DO** document each skipped flaky test in your maintenance run file
 5. Commit the skip and continue with your work
 
 ## Getting Started
 1. Read the MAINTAIN protocol document
-2. Start with the Audit phase
-3. Document all changes made
+2. Run `porch next` to get your first task
+3. Work through audit → clean → sync → verify in a single pass
+4. Document everything in the maintenance run file

codev-skeleton/protocols/maintain/prompts/audit.md

@@ -0,0 +1,88 @@
+# MAINTAIN Phase Prompt
+
+You are executing the **maintain** phase — a single pass covering audit, cleanup, and doc sync.
+
+## Context
+
+- **Current State**: {{current_state}}
+
+## Step 1: Determine Scope
+
+```bash
+ls codev/maintain/
+```
+
+Find the last run number and its base commit. Then see what changed:
+
+```bash
+git log --oneline <base-commit>..HEAD
+```
+
+Create your maintenance run file: `codev/maintain/NNNN.md` (next number in sequence).
+
+## Step 2: Audit
+
+Identify dead code, unused dependencies, and stale documentation. Don't fix yet — catalog first.
+
+```bash
+# Dead exports
+npx ts-prune 2>/dev/null || echo "ts-prune not available"
+
+# Unused dependencies
+npx depcheck 2>/dev/null || echo "depcheck not available"
+
+# Stale arch.md references
+grep -oE '[a-zA-Z]+/[a-zA-Z/]+\.[a-z]+' codev/resources/arch.md | sort -u | while read f; do
+  [ -e "$f" ] || echo "Missing: $f"
+done
+```
+
+Record all findings in the maintenance run file.
+
+## Step 3: Clean
+
+For each audit finding:
+1. Verify it's truly unused (grep the codebase)
+2. Remove with `git rm` (tracked) or move to `codev/maintain/.trash/$(date +%Y-%m-%d)/` (untracked)
+3. Build and test: `cd packages/codev && pnpm build && pnpm test`
+4. Commit: `git add <specific-files> && git commit -m "[Maintain] Remove unused X"`
+
+One removal at a time. Verify after each. Never use `git add -A`.
+
+## Step 4: Sync Documentation
+
+**arch.md**: Read `codev/resources/arch.md`, compare with actual codebase. Update directory structure, component descriptions, key files. Remove references to deleted code. Add new components. Explain HOW things work, not just WHAT.
+
+**lessons-learned.md**: Scan `codev/reviews/` for new reviews since the base commit. Extract actionable, durable, general lessons.
+
+**CLAUDE.md / AGENTS.md**: `diff CLAUDE.md AGENTS.md` — they must be identical. Update the stale one.
+
+**Pruning**: Remove obsolete content. Document every deletion with justification (OBSOLETE, DUPLICATIVE, MOVED, VERBOSE). When in doubt, keep.
+
+Commit documentation changes:
+```bash
+git add codev/resources/arch.md codev/resources/lessons-learned.md
+git commit -m "[Maintain] Update arch.md and lessons-learned.md"
+```
+
+## Step 5: Final Checks
+
+```bash
+cd packages/codev && pnpm build && pnpm test
+```
+
+Both must pass. Update the maintenance run file with a summary of everything done.
+
+## Signals
+
+When all work is complete and build/tests pass:
+
+```
+<signal>PHASE_COMPLETE</signal>
+```
+
+If blocked:
+
+```
+<signal>BLOCKED:reason</signal>
+```