github-projects-pipelinelisted

# github-projects-pipeline — stage protocol GitHub Projects is the **workflow authority**. The project item's `Status` field is canonical for pipeline stage. GitHub issues hold the durable ticket body, comments, labels, and relationships; branches, commits, pull requests, and checks hold the code evidence. There is no second tracker to mirror. ## Stage-parent session profile GPT-5.6 Luna is the overall coordinator; it may dispatch Opus 5 in Claude Code for `/legacy-planner` after the planning decisions are known. `/legacy-coder`, `/legacy-debugger`, and `/legacy-reviewer` normally run as independent top-level stage-parent sessions. The workflow uses the GitHub Project item, GitHub issue/PR artifacts, and handoffs to bridge those sessions. A native child launched from another session is not a stage parent and must not spawn nested children. | Stage | Parent session | Harness / route | Effort | |---|---|---|---| | `/legacy-planner` | Opus 5, Luna-dispatched or visible | Claude Code with Claude subscription | medium/high | | `/legacy-coder` | Kimi K3 | Pi via OpenRouter; optional Kimi K2.7 Code helpers | high | | `/legacy-debugger` | GPT-5.6 Luna | Codex with Codex subscription | **max** | | `/legacy-reviewer` | Grok 4.5 | Pi via OpenRouter | high/xhigh | Do not route a Claude subscription through Pi. Do not confuse the native Codex route (`codex`, `gpt-5.6-luna`) with Pi/OpenRouter (`pi`, `openrouter/openai/gpt-5.6-luna`). `max` is reasoning effort, not a model name. A hea