v0.0.4 — Enforce Checkpoint 1 (manual plan review) before MAGI

Summary

The sbtdd orchestrator now enforces Checkpoint 1 (manual human review of the original plan) as an ordered gate before Checkpoint 2 (the MAGI review) in the plan gate, matching the canonical flow in the scaffolded CLAUDE.local.md §1. Previously the routing collapsed both into a single MAGI step and Checkpoint 1 was not enforced.

Changes

• references/routing.md — the plan-gate decision-table row is now "Plan gate (Checkpoint 1 → Checkpoint 2)": Checkpoint 1 stops for manual review of claude-plan-tdd-org.md; on reject it re-runs superpowers:writing-plans with the feedback; Checkpoint 2 (MAGI) runs only after Checkpoint 1 is approved.
• references/review-gates.md — new "## 0. Plan Gate" section describing Checkpoint 1 (criteria, reject loop-back) chaining into the MAGI loop, pointing to CLAUDE.local.md §1 (no rule-table duplication).
• SKILL.md — delegation row reordered to manual review (Checkpoint 1) → magi:magi (Checkpoint 2); the Gates section names both ordered stops and states MAGI never runs before Checkpoint 1 is approved.
• Tests — three row/section-scoped presence tests lock the Checkpoint 1 → Checkpoint 2 ordering and the reject loop-back.

Design

Approach A — the two checkpoints run as an ordered in-phase sequence within the single plan-gate phase (they share the same file-state window), so no new artifact and no session-state.json field were added.

Verification

• Full pytest suite green (46 tests).
• Pre-merge code review clean-to-go; MAGI design review verdict STRONG GO.
• plugin-validator structural validation: PASS.