What problem does it solve? Operators using Gemini CLI need a consistent way to inspect and drive the repo-local phase-loop orchestration runner without reimplementing phase selection, reconciliation, or event handling, and without misreading shared loop state. ## Core Features & Use Cases - Command Mapping: Maps Gemini-facing commands (handoff, status, monitor, run, dry-run, sync-skills) to the shared phase-loop / codex-phase-loop CLI surface. - Shared State Inspection: Reads .phase-loop/state.json, events.jsonl, handoff files, and per-run heartbeat/terminal-summary artifacts to report automation and verification status. - Drift and Blocker Handling: Detects installed-skill drift, frozen blockers such as missing_secret or branch_sync_conflict, and routes spec-delta closeout decisions through the runner evidence contract. - Use Case: A Gemini operator resumes an unattended phase-loop run after another harness drove the loop, starting from handoff or monitor --once --json to avoid acting on stale TUI state. ## Quick Start Ask the assistant to check the current phase-loop status and handoff state using the gemini-phase-loop bridge before resuming a bounded run with --max-phases 1.