harness-verify-before-movelisted

# Harness — Verify Before Move Comprehensive phase-exit sweep. Ten steps run in order: gate → code → docs → notes → unused files → memory cleanup → GitHub → README → memory write → snapshot. **Destructive operations (delete, close, label-change) require explicit user confirmation. Never auto-apply.** --- ## When to trigger - User says "move to next phase", "phase complete", "sync everything", "clean slate", "project snapshot", or any intent to advance - You are about to update `position.phase` in `.harness/state.json` - Before any handover that marks a phase closed --- ## Reference files Load on demand — not all at once: - **`references/github-sync.md`** — load at Step 7 (GitHub milestone, issue, board sync) - **`references/doc-cleanup.md`** — load at Step 5 (unused document audit rules) --- ## Execution sequence Run all 10 steps. Do not skip. Do not advance the phase until Step 1 passes. **Every step reports its own confidence — not just its result.** Prefix each step's summary line with exactly one label: - `[VERIFIED]` — you ran the check directly and have observable evidence (command output, file contents read, cross-reference traced end to end) - `[ASSUMED]` — you ran the check, but the conclusion rests on inference or judgment rather than direct evidence (e.g., "this entry looks reversed" without tracing the actual code path) - `[SKIPPED — <reason>]` — a precondition was missing and the check did not run at all Do not default to `[VERIFIED]`. If you are n