setup-isolated-setup-verify

Runtime routing (run before the Claude-specific checks)

Use the operator's explicitly requested runtime when supplied; otherwise use the active session's runtime. An installed executable or configuration directory alone does not select a runtime. For the routing below, treat that selection as the active harness.

When the active harness is Codex, run the verification contract in docs/adapters/codex.md: static profile lint, native rule classification, project trust, /skills visibility, and bridge preflights. Report every Codex check and then stop. Do not interpret the Claude settings checks below as Codex requirements.

When the selected runtime is Gemini CLI, follow docs/adapters/gemini.md: check the workspace profile, guard registration, skill discovery, and actual runtime behavior. Report static and live checks separately, including any checks not run and the documented isolation limits. Do not require Claude configuration; then stop before the Claude-specific checks below.