retro

1# /retro — CP-7 close the V
2 
3Every non-`tiny` shipped or escalated run gets a retro. Retro is **advisory** but strongly expected: it is how the harness improves.
4 
5## When to run
6 
7- After CP-6 ship (approved publish, merged PR, vault deliverable done)
8- After escalate (capture why verifier failed)
9- End of an `/ultragoal` phase (one retro per phase)
10- Manual: `/retro <run-dir or spec path>`
11 
12## Phase 1 — Gather evidence bundle
13 
14Read:
15 
161. Spec or card description + acceptance criteria
172. `04-projects/harness/runs/<id>/evidence/` (ledger, checkpoints.tsv, CP-* files)
183. `.claude/logs/loop-ledger.tsv` (last rows for this run)
194. `04-projects/<goal>/STATUS.md` if an ultragoal phase
20 
21## Phase 2 — Checkpoint audit
22 
23For each CP the lane required, mark Expected vs Actual vs Gap:
24 
25| CP | `tiny` | `normal` | `full` |
26|---|---|---|---|
27| CP-1 spec | skip | required | required |
28| CP-3v component | skip | required | required |
29| CP-4 integration | skip | skip | required if multi-task |
30| CP-5 acceptance | if mutate | required | required |
31| CP-6 ship | if external | if external | required |
32 
33## Phase 3 — Evidence quality pass
34 
35Ask:
36 
37- Any AC-n shipped without a PASS evidence row? (traceability violation)
38- Any PASS row where observation is tool-return not artifact? (confident-but-unchecked)
39- Any criterion that wasn't falsifiable? (fix in next spec)
40 
41## Phase 4 — Write retro
42 
43Copy `references/retro-template.md` to:
44 
45`04-projects/harness/retro/YYYY-MM-DD-<slug>.md`
46…