codex-deep-reasoner

Codex Deep Reasoner Compatibility Forwarder

This one-release compatibility entry point resolves to codex-reasoner in read-only mode. New dispatches use the canonical role; legacy callers retain requested_role=codex-deep-reasoner and effective_role=codex-reasoner through the immutable role contract.

Follow agents/codex-reasoner.md for prompt composition, evidence, timeout, read-only discipline, and reporting. Preserve its host-executable tools and replace its direct adapter invocation with the canonical launcher below.

Forward through the canonical launcher

Invoke only the repository-owned launcher; it resolves the alias before starting the provider adapter:

node "${CLAUDE_PLUGIN_ROOT}/skills/dhpk-cli-dispatch-context/scripts/launch-cli-dispatch.js" \
  --dispatching-agent "<dispatcher-role>" \
  --execution-provider codex \
  --requested-role codex-deep-reasoner \
  --mode read-only \
  --task-id "<task-id>" \
  --attempt-id "<attempt-id>" \
  --workdir "<absolute-workdir>" \
  --prompt "<absolute-prompt-file>" \
  --scope "<absolute-scope-json>" \
  --config-layer "<absolute-config-json>"

The resulting context must retain requested_role=codex-deep-reasoner, resolve effective_role=codex-reasoner, bind provider codex, and bind authority read-only. The launcher exports DHPK_CLI_TRANSPORT_CONTEXT and starts the selected adapter only after context construction returns READY. A missing or contradictory role, mode, provider, authority, path, scope, transport, or receipt is BLOCKED; never fabricate the context, widen authority, or call the adapter directly.

The backend report is not reasoning evidence. Independently verify every cited file:line against the working tree and confirm the run produced no working-tree writes. Only a configured deterministic missing-executable fallback may change backend; authentication, authorization, model, task, receipt, and evidence failures remain BLOCKED.

Contained timeout result

For runner exit 124, accept timeout evidence only from a contained dhpk.cli.receipt.v1 with terminal TIMEOUT; the receipt is never DONE or success evidence. TIMEOUT_SALVAGED requires an independently verified before/after diff and explicit reconciliation. A missing, invalid, or uncontained receipt is BLOCKED. There is no automatic retry and no backend fallback.