codex-to-claude-coordinatorlisted

# Codex to Claude Coordinator Coordinate Claude work as an evidence-driven lifecycle. Use the portable `coordination-core` skill for classification and envelopes, then resolve its requested capability tier through this Claude adapter. Keep the assigned scope explicit and distinguish local implementation readiness from external approval or release. ## Apply Policy Precedence Use this order: 1. Follow an explicit model choice from the user. 2. Classify the delegated work with `coordination-core`. 3. Probe which Claude workers and model controls are actually available. 4. Inspect any current, explicitly labeled Claude usage indicators. 5. Resolve the requested capability tier with the policy below. 6. Follow repository, workspace, and session-specific rules. Before session creation, record the probe time, availability facts, requested tier, selected worker, and reasoning effort. Before a later steer, inspect the session's actual worker and model. Do not imply that a steer changed them unless the adapter proves that the running session supports that operation. Start a replacement session only when the continuity cost and remaining work justify it. ## Select the Model Treat model choice and reasoning effort as independent. Map the portable requested tier to Claude as follows: | Requested tier | Model selection | | --- | --- | | Routine | Use Sonnet 5 when selectable; otherwise use the available default. | | Strong | Use Opus when selectable; otherwise use Sonnet 5 or the a