phase-loop

Invoke the run command with an explicit bound, such as phase-loop run --max-phases 1. The bridge clamps unbounded interactive requests to a single phase and reports that TUI-initiated runs stay bounded.

Start with the handoff command or read .phase-loop/tui-handoff.md, then verify exact machine state with state --json or status --json before resuming. The handoff links to state, events, runs, and the latest log.

Yes, per-harness override SKILL.md files adapt the same bridge contract for Claude, Gemini, OpenCode, and Codex. Each override maps to the shared runner commands while preserving harness-specific launch posture and trust metadata.

The bridge preserves the blocker_class, summary, required inputs, and automation status from the frozen taxonomy, such as dirty_worktree_conflict or branch_sync_conflict. For access blockers it performs metadata-only probes and never prints secret values.

In pipeline mode with branch governance on, dispatch switches to a branch cut from origin/main, so a roadmap committed only on an unpushed local branch is refused cleanly. Push the roadmap to the base branch or pass --allow-branchgov to switch anyway.

Run sync-skills --check when the advisory bridge record reports missing_root, missing_skill, or drifted for installed bridge skills. Use --apply only when you explicitly want to repair local bridge-skill drift for manual reentry.