hyper-implement-looplisted

# hyper-implement-loop Autonomous implement-hardening gate. Runs `hyper-implement` to completion first, invokes Codex `code-review --base main` through the bridge, and — on the FIRST round that carries blocking findings — spawns the `fixer` agent **once** to apply them, reusing that same agent via `SendMessage` on every later round until no blocking findings remain (judged semantically — see Step 4) or the cap is hit. A run Codex clears on its first review spawns no fixer at all. The reviewer is always the Codex bridge, never an agent — this preserves the "Claude builds, Codex reviews" invariant. ## When to use - User typed `/hyperclaude:hyper-implement-loop <plan path>`. - User wants an autonomous implement → review → fix cycle in a single gesture. Skip when: - The task is one step — use `/hyperclaude:hyper-implement` directly. - You want hands-on control over each implement / review round — use `/hyperclaude:hyper-implement` + `/hyperclaude:hyper-code-review` manually. ## Failure & recovery protocol — read first `${CLAUDE_PLUGIN_ROOT}/references/loop-protocol.md` carries the shared cross-loop protocol: **Spawn contract**, **Reply transport**, **Correctives and transport failures**, **Shared anti-patterns**. `references/failure-protocol.md` (sibling of this file) is the implement-loop binding layer: it names this loop's structured per-finding reply schema, the schema-gate accept rule, the semantic finding-map validation, the named reports, and what a transport failure