Run Flow

Use the installed orchestrator-flow definition as the authoritative workflow.

1. Read ${CODEX_HOME:-$HOME/.codex}/agents/orchestrator-flow.toml as the authoritative workflow. Never manually adopt a raw workspace role; the preflight below decides whether effective Codex config may apply workspace routing.
2. Always query the installed global profile manager for current-workspace JSON status before adopting the workflow. A normal workspace without a profile reports global inheritance and may continue. If status cannot be verified or a configured profile's health is not ok, stop and ask the user to rerun workspace set or clear; never dispatch through an unhealthy or orphaned profile. If a configured profile's catalog_state is not current, stop before dispatch and require explicit workspace set --model-set openai or clear. If its profile_eligibility is not eligible, warn that Codex is ignoring the workspace layer and continue with global role routing. Only a healthy, eligible, current profile may route dispatched roles locally. For that eligible path, retain each role's exact saved resolved_configuration from the selected versioned model set and registered reasoning projection, including its configuration identity, version, and digest. Pass that same envelope to the formal shared resolver and trace expectations. The resolver selects effort only, so native managed normal dispatch omits a raw model; a Web session agent Job selects only the saved role model under protocols/REASONING_POLICY.md. Retired Codex model sets are not eligible for new dispatch.
3. If the global definition is absent, stop and ask for the global agents_pipeline Codex install. Do not reconstruct the workflow from memory.
4. Remove only the $run-flow token and preserve the remaining request and flags as raw input.
5. Adopt the definition in the current/main agent; do not spawn the same orchestrator merely to enter the mode.
6. Obey its task bound, delegation, verification, review, cleanup, reasoning, and final-report constraints. The formal shared resolver resolves each dispatched role's effort without changing the current/main agent. Native managed dispatch uses effective Codex role routing, normally omits a model override, and verifies the local child trace before claiming adaptive enforcement. A Web session agent Job instead selects the saved role model explicitly, applies effort only in adaptive mode, observes one Job to terminal, and follows the result and status limits in protocols/REASONING_POLICY.md; it never claims native role identity or trace enforcement. The sole native managed auto-recovery exception remains in protocols/CAPABILITY_RECOVERY.md and requires matching trace evidence. --review=max remains an exact reviewer-only effort gate: adaptive requests and verifies it on the native surface, shadow records it without applying it, and inherit conflicts. It remains deep ordinary review, never applies to a non-review role, and is unavailable on the Job surface until supported evidence exists.