Player–Coach: Adversarial Implementation Loop

Orchestrate one implementation run. A player turn is one player invocation and its commit or no-op. A verification run is one verify invocation, including a same-turn rerun. What the run publishes is the ordered commits and accurate PR state; what it remembers is the run ledger on local disk. The PR's implementation journey synthesizes both for a reviewer, and is the only prose this loop publishes.

The default outcome is a ready PR only after verification and CI pass. --no-ci hands an approved open PR/MR to its caller while preserving the observed draft or ready state. --no-pr is an explicit local-only opt-out from pushing anything.

This loop owns the local development environment until it returns. The player writes code; the orchestrator owns branches, commits, pushes, verification, PR state, and CI.

Phase 0: Set up the run

Resolve plan and arguments