docs(plan): CURRENT.md - M12 shipped

docs/plans/CURRENT.md

@@ -7,13 +7,14 @@ update this file to the next action). No ambiguity, no re-planning.
 
 ## Next action
 
-Owner review of M11 (session forking) — then name the next target.
+Owner review of M12 (conductor auto-apply policy) — then name the next target.
 
 ## Queue (ordered, not started)
 
 1. Second real adapter (parked — owner focused on Pi)
-2. Auto-apply policy for worker patches (substrate exists)
+2. Session forking from a common ancestor — SHIPPED in M11; exercise via session demos
 3. UX/DX backlog #31 (grep highlight vs status colors — likely closed by owner's unalias)
+4. Push policy decision: auto-apply commits locally; push remains explicit (documented in CONDUCTOR.md)
 
 ## Rules
 
@@ -27,6 +28,12 @@ Owner review of M11 (session forking) — 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 — M11 session forking (#33) — merged, child recalls ancestor context, ancestor untouched, 58/24/14 + verify green; release 0.0.7 activated
+- 2026-09-03 — M12 conductor auto-apply policy (#34) — committed on main, 17/24/58/14 + verify green; push stays explicit
+
 - 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