docs(plan): CURRENT.md - M10 shipped, retention next in review

docs/plans/CURRENT.md

@@ -7,14 +7,14 @@ update this file to the next action). No ambiguity, no re-planning.
 
 ## Next action
 
-Owner review of M9 (mission capability policy) — then name the next target.
+Owner review of M10 (retention) — then name the next target.
 
 ## Queue (ordered, not started)
 
-1. Run-record retention/pruning policy
+1. Second real adapter (parked — owner focused on Pi)
-2. Second real adapter (parked — owner focused on Pi)
+2. Auto-apply policy for worker patches (substrate now exists)
-3. Auto-apply policy for worker patches (capability policy now exists as its substrate)
+3. Session forking from a common ancestor (pi JSONL trees make this native)
-4. Session forking from a common ancestor (pi JSONL trees make this native)
+4. UX/DX backlog #31 (grep highlight vs status colors — likely closed by owner's unalias)
 
 ## Rules
 
@@ -28,6 +28,10 @@ Owner review of M9 (mission capability policy) — then name the next target.
 
 ## Completed log
 
+- 2026-09-03 — M9 mission capability policy (#30) — merged, least-privilege intersection
+- 2026-09-03 — test UX: green OK/red FAIL status colors (#31 adjacent) — terminal-only, pipe-safe
+- 2026-09-03 — M10 run-record retention (#32) — merged, prune keep-N/dry-run/receipt, 49/24/14 + verify green
+
 - 2026-09-03 — M5 workspaces + capability envelope (#20, #21) — merged, tests green
 - 2026-09-03 — M6 named sessions + resume (#22, #23) — merged, teach/recall verified
 - 2026-09-03 — M7 run inspection + release 0.0.6 (#24) — merged, activated