docs(plan): CURRENT.md — retry lineage shipped, M9 queued for decision

docs/plans/CURRENT.md

@@ -7,13 +7,14 @@ update this file to the next action). No ambiguity, no re-planning.
 
 ## Next action
 
-Gitea issue: (none queued — awaiting owner direction)
+Owner decision on M9: mission-level capability policy (design sketch: missions may declare default tool sets; tasks inherit unless overridden; conductor validates the merge). Say "next" to proceed or name a different target.
 
 ## Queue (ordered, not started)
 
-1. Owner review of M5–M8 (workspaces, capabilities, sessions, conductor loop)
-2. M8 follow-up: retry lineage (retriedFrom field) + relative-mission-path retry limitation
-3. M9 candidates: mission-level capability policy; run-record retention; decision on auto-apply policy for worker patches
+1. M9: mission-level capability policy
+2. Run-record retention/pruning policy
+3. Second real adapter (parked — owner focused on Pi)
+4. Auto-apply policy for worker patches (deferred until capability policy exists)
 
 ## Rules
 
@@ -31,3 +32,5 @@ Gitea issue: (none queued — awaiting owner direction)
 - 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
 - 2026-09-03 — M8 conductor loop + worker-built retry (#25, #26, #27) — merged; worker authored retry in 2 refinement rounds, conductor fixed a 3-line interpolation rename; live retry verified
+- 2026-09-03 — retry lineage + relative mission resolution (#28) — merged, 36/24/14 suites + verify green
+- 2026-09-03 — M8 conductor loop + worker-built retry (#25, #26, #27) — merged; worker authored retry in 2 refinement rounds, conductor fixed a 3-line interpolation rename; live retry verified