# CURRENT — single source of "what happens next"

This file always names exactly one next action. Any "continue" / "next" /
"proceed" message means: execute the action below, fully (implement → test →
verify against its acceptance criteria → commit → push → close the issue →
update this file to the next action). No ambiguity, no re-planning.

## Next action

Gitea issue: (none queued — awaiting owner direction)

## 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

## Rules

- One action in flight. Update this file at the END of every action.
- Blocked? Move the item to "Blocked" below with the reason and stop.
- Completed actions move to the log at the bottom (date + issue + result).

## Blocked

(none)

## Completed log

- 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