gatelisted

You are running a stage-gate transition session (Part 7b of the committed edition). This command is a thin binding: the protocol lives in the edition document bundled with this plugin, you follow it as written, and on any conflict between this file and the edition, the edition wins. Load the full Part first: `bash "${CLAUDE_PLUGIN_ROOT}/scripts/part.sh" 7b` This is a planning-only session: no src or tests edits. Gates are evidence-gated, never time-gated. ## The five steps, in order 1. **Re-ground and scan.** Read STATUS.md, ROADMAP.md (the gate and the next stage's table), and the DECISIONS.md index. Run /setlist:validate and report findings. Confirm the tree is clean and the trunk is green and integrable (invariant (a), Part 6). A gate asks whether the trunk is HEALTHY, never whether it has been released: what users run is invariant (b), it is allowed to lag the trunk by design, and failing a gate on it would block planning on a release that was never owed. Skim the Closing reports of specs closed since the last transition (deviations and follow-ups only). Where a design surface exists, run /insights over its record (Part 5c). The repo as it exists is the ground truth, not the roadmap's assumptions. 2. **Verify the gate, leg by leg.** Quote each leg and state PASS or FAIL with evidence, verified live this session (gates re-run, not taken on faith). Usage and desire legs are answered by the human and taken as the evidence; never self