feat(orchestration): retry <runId> — authored by headless pi worker (#26, #27)

Collaboration record (conductor loop, docs/plans/CONDUCTOR.md):
- round 1 (worker session worker-1, 2m28s): retry implemented per spec
- conductor live test exposed spec gap: direct invocation lacked
  launcher env exports
- round 2 (same worker session, 59s): spawnEnv made self-sufficient,
  but used PI_* where compose interpolates MOSAIC_*
- conductor hotfix: 3-line rename to MOSAIC_PROVIDER/MOSAIC_MODEL/
  MOSAIC_DATA_ROOT

Final: node scripts/mosaic-task.mjs retry <runId> re-executes a run's
task snapshot as a new run; live retry replied REMEMBERED; all suites
green (24/32/14 + verify).

Known limitation: retrying a run whose task used a RELATIVE mission path
resolves it against the temp dir; lineage tracking deferred.

Closes #25, closes #26, closes #27

docs/plans/CURRENT.md

@@ -11,9 +11,9 @@ Gitea issue: (none queued — awaiting owner direction)
 
 ## Queue (ordered, not started)
 
-1. Owner review of M5–M7 (workspaces, capabilities, sessions) — hands-on
-2. M8 candidate: mission-level capability policy (defaults per mission)
-3. M9 candidate: run-record retention + `retry <runId>` convenience
+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
 
 ## Rules
 
@@ -30,3 +30,4 @@ Gitea issue: (none queued — awaiting owner direction)
 - 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
+- 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