[SaladDay]

Codex now applies the official Session updates and review: auto_review from each root Turn on (Agents API pin 3.45.0). It needs one protocol change, which the Claude Code change builds on.

Protocol (Core–Runtime 0.25.0)

• proto.TurnSettings gains review (auto_review; empty is none). Core fills it from the Turn's bound settings.
• A retained Executor no longer counts turn in its identity. Declaration.ValidateSessionUpdate(previous, next) decides every difference. Core uses the same function on Session update.
  • A setting the Harness declares changeable may differ, and so may review when the Harness declares a review value.
  • Any other difference stays configuration_conflict.
• The Runtime validates turn once, in dispatch, against the registered declaration. The adapter-level ValidateTurnSettings calls are deleted.
• The registry keeps one declaration per kind; the configurations map is gone.
• Docs: runtime-protocol.md (the turn and identity rows) and harness-onboarding.md (Binding, and the adapter's obligation to apply a changed turn natively before input). Both have zh mirrors.

Codex

• Every turn/start carries:

  • model;
  • effort, when set;
  • serviceTier, the tier or null for auto;
  • approvalPolicy and approvalsReviewer: none sends never/user, and auto_review sends on-request/auto_review.

  These go on every Turn because a cold thread/resume restores the persisted values.

• The declaration supports changing model, effort and service tier. It does not support resetting effort, because Codex cannot clear it. Reviews: auto_review.

• An escalation that still reaches the client gets JSON-RPC -32601, and Codex turns that reply into a denial. This is the official "deny manual approval fallbacks"; a new test covers it.

• Docs updated, with their zh mirrors: harness-capabilities.md, the Codex guide, the unattended paragraph of harness-onboarding.md, and the ledger.

Verification

• go vet passes.
• go test passes for agent/..., dispatch, wireconformance, harnessconfig/... and Core execution.
• check-runtime-contract, check-harness-catalog and check-translations pass.
• Tests added:
  • A retained Executor accepts a declared change, and StartTurn receives it.
  • An undeclared change or reset is still a conflict.
  • turn/start carries the five fields for none and auto_review, and a second Turn sends the new model.

Review fixes

• The review value check joins the ValidateTurnSettings loop, and ValidateReview is deleted.
• ResolveExecutor now returns the declaration with the factory, so the second registry lookup is gone.
• The Session update compares the model in SQL (MarkSessionModelSource) instead of decoding it twice in Go.
• An effort reset that the Harness cannot apply now says "cannot be reset to null".
• Docs:
  • The ledger links the Session update line to the capability table instead of repeating it.
  • It records that an empty agent.model returns 400.
  • It records what Codex auto_review reviews (below).

Real-model run (test cluster, MiniMax-M2.7)

• Codex.
  • A model change takes effect on the next Turn (M2.7 → M3), and so does an effort change (high → low).
  • An effort reset returns 400 and leaves the Session unchanged.
  • A Turn queued before an update keeps its bound model.
• Codex auto_review. turn/start carried on-request/auto_review, and an escalated rm -rf was denied with no required action reaching Core. Two native limits are now in the ledger, by owner decision:
  • Codex reviews only what it escalates, because it has full filesystem access inside the sandbox.
  • Its reviewer calls codex-auto-review through the Session's provider, so a provider that does not serve that model denies every escalated action with its own error.

---

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}