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: