profile-gated-deliverylisted

# profile-gated-delivery The preserved factory in one skill: **legacy-planner → legacy-coder → legacy-debugger → legacy-reviewer**, with an evidence gate between each stage. The point is not the stages. It is that **each stage's entry condition is the previous stage's proof** — and that the maker of a change is never its reviewer. ## Stage-parent sessions GPT-5.6 Luna is the overall coordinator. It may dispatch Opus 5 in Claude Code for planning after the human decisions are known. Kimi, Codex, and Grok are independent top-level parent sessions for the remaining stages: | Stage | Parent / harness | Effort | |---|---|---| | **planner** | Opus 5 / Claude Code subscription, Luna-dispatched or visible | medium/high | | **coder** | Kimi K3 / Pi via OpenRouter; optional Kimi K2.7 Code helpers | high | | **debugger** | GPT-5.6 Luna / Codex subscription | **max** | | **reviewer** | Grok 4.5 / Pi via OpenRouter | high/xhigh | A stage parent may coordinate one level of helpers when its own harness supports it. A native child launched from another session cannot spawn nested children. The GitHub Project item, GitHub issues/PRs, and handoffs are the bridge between stage-parent sessions. Keep stages serial and one ticket in flight. ## The four roles | Role | Queue | Loads | Produces | State effect | |---|---|---|---|---| | **planner** | Planned | `github-projects-pipeline` → `legacy-planner` | plan doc and ready tickets | Planned → Agent Ready when blockers are done | | **coder**