Skip to content

OmniRoute 20128 at max effort for gpt-6.1-sol: upstream PR 15167 on the running build, lsof shim v2, restart record - #534

Merged
seathatflowsinourveins merged 1 commit into
mainfrom
res-omni-sol-max-20260930
Sep 30, 2026
Merged

seathatflowsinourveins merged 1 commit into
mainfrom
res-omni-sol-max-20260930

Conversation

@seathatflowsinourveins

Copy link
Copy Markdown
Owner

Scope

  • What this PR changes: records the 2026-09-30T06:32:50Z restart of the 20128 gateway (omniroute.service, only) onto build cf6748d04: the running build plus upstream PR #15167, so gpt-6.1-sol reaches max effort (before it, every max request was sent as xhigh: 1154 of 1495 rows since 00:00Z). It adds the qualification (upstream's check:pack-artifact and check:pack-boot, boot smoke, 147 of 147 targeted tests), the offline wire table, the probe gate before and after, the owner records before and after, the switch output and unit diff, and a new lsof shim v2 in the new prefix that keeps a client's dead connection from blocking a restart (found on the way; reproduced and tested with kept outputs). It also records the 05:50Z to 05:55Z incident on 20129's sharedgw node (my probe; repaired by the dashboard's Test connection). Text changes: the decision record (update section, deltas table, residual), docs/foundation-stack.md, the unit template's shim comment, and the omniroute row text of manifests/stack.json (build ids, the carry, the shim).
  • Not in this PR: any change to 20129, hindsight-live, settings, combos or the pool; the component pin (version stays 3.8.50); compression on 20128 (still an open user decision); a fix for the sharedgw hazard (upstream has none and I have no reference implementation).
  • Base commit: 7d0189117028907261d06926dee86844c1ae8f1e (main after OmniRoute 3.8.51 from npm: install, boot smoke, provenance and signature receipt (the component pin stays 3.8.50) #533).
  • Lane: lane:shared: the omniroute row of manifests/stack.json is a shared hot file (docs/lanes.md); the trading lane's acknowledgement at this head is needed before merge. No trading path is touched.
  • Owned paths touched: evidence/artifacts/omniroute-sol-max-20260930/, docs/decisions/, docs/foundation-stack.md, adoption/templates/systemd/omniroute.service, manifests/stack.json (omniroute row only), manifests/evidence.json (registration, last commit).

SOTA sources

  • Upstream PR #15167 "feat(models): add GPT-6.1 Sol to Codex catalog and pricing", head f5d8e150b79e0901fa18241c7f29bff889b87c14, one commit, 5 files +23/-0 on release/v3.8.52 (a1a2dce1a64a4b123f80ec899fc88bb2aa34d1a4); carried like #13788: a cited upstream change, cherry-picked with its stable patch-id verified equal (14ec6648f50fc499d430f28d2af7840cd2d46055).
  • Upstream source read at 2f42a9ac19d1a247ec9ce5473b790843724b3061 (the build's base): open-sse/executors/codex/reasoningSuffix.ts (alias sets, suffix parser), open-sse/executors/codex.ts (clampEffort, effort resolution), bin/cli/utils/pid.mjs findListeningPids and bin/cli/commands/serve.mjs resolveServeBusyPids (the preflight and its #14518 bind-probe fallback, unchanged on release/v3.8.52 and main), src/lib/contextWindowResolver.ts, src/lib/db/models/syncedAvailableModelPersistence.ts, src/shared/services/modelSyncScheduler.ts, src/sse/services/authTerminalStatus.ts (the bare-401 rule behind the sharedgw expiry).
  • Codex 0.159.2's own bundled catalog (codex debug models --bundled, offline): gpt-6.1-sol supports low to ultra including max.
  • Precedent: docs/decisions/2026-09-30-omniroute-rebuild.md and its artifacts (OmniRoute rebuild 2026-09-30: decision record, evidence artifacts, owner-record script, unit templates (records what runs; compression on 20128 not applied) #530).

Evidence-class table

Claim Evidence class Command / receipt
The PR is one commit of 5 files, its patch-id equals the cherry-pick's, and Codex 0.159.2 lists max for the model source_review receipt C1; checks/upstream-pr-15167-identity.txt, checks/codex-bundled-catalog-0159.2.txt
Before the restart 20128 sent max as xhigh (1154 of 1495 rows); astra was sent as requested local_integration (read-only call_logs counts) C2; checks/calllog-effort-counts-before-switch.json
Offline, exactly five gpt-6.1-sol requests change their wire model and effort and eight others do not local_integration C3; checks/effort-wire-*.json
The candidate built with upstream's scripts, check:pack-artifact and check:pack-boot pass, boot smoke health 200, targeted tests 147 of 147 equal to the baseline native_proven for upstream's checks on our build, local_integration for the rest C4; checks/qualification-*.txt
Preflight trap reproduced with shim v1 (restart refused), fixed with v2 (health 200 in 5 s), a second real instance still refused local_integration C5; checks/preflight-*
The restart changed three unit lines, 20129 and hindsight-live are untouched, read-back clean local_integration C6, C8; checks/switch-output.txt, checks/readback-after-switch.txt, checks/owner-record-*.json
After the restart max is sent as max, the suffix ids and the bare id answer 200, a 0.157.1 client request answers 200 native_proven (live calls through the gateway, effort read from call_logs) C7; checks/probe-gate-*.json
An unknown id through the sharedgw node parked its connection for 4.5 minutes; the repair and its state local_integration (a transcription of printed outputs) C9; checks/sharedgw-connection-expiry-20260930.txt

Local commands run

$ python3 scripts/validate.py
{"components": 69, "hashed_files": 8421, "profiles": 4, "receipts": 175, "status": "passed"}                                             exit 0
$ python3 scripts/evidence_manifest.py --check
{"files": 8421, "status": "passed"}                                                          exit 0
$ python3 -B -m unittest tests.test_foundation_stack_pins tests.test_omniroute_gateway_unit tests.test_adoption_contract tests.test_freeze_snapshot tests.test_catalogs tests.test_stack_lifecycle
Ran 268 tests in 112.480s ... OK                                                                exit 0

The full unittest discovery runs in CI's validate check.

Decision record

docs/decisions/2026-09-30-omniroute-rebuild.md, "Update 2026-09-30, 06:32Z" (alternatives, the comparison that would overturn each choice, residuals), and evidence/artifacts/omniroute-sol-max-20260930/receipt.json.

Host evidence

This PR adds an artifact directory under evidence/artifacts/, not evidence/hosts/.

  • scripts/validate.py (exit 0 above) validates the registered artifacts.
  • Independent review: requested in this PR; the Gate A owner independently reproduced the 06:33Z owner record (same digest except taken_utc) and verified the shim hashes.
  • No platform_status change.

Checklist

  • No workflows or Actions are changed.
  • No secrets are printed, logged or committed.
  • No new paid hosting, subscription or billing surface.
  • Peer-owned untracked files and worktrees were preserved.

🤖 Generated with Claude Code

…he running build, lsof shim v2, restart record (2026-09-30T06:32:50Z)

Records the restart of 20128 (only) onto build cf6748d04 = the running build plus the one commit of upstream PR 15167, so gpt-6.1-sol reaches max
(before it every max request was sent as xhigh: 1154 of 1495 rows since 00:00Z), with its qualification (upstream's check:pack-artifact and
check:pack-boot, boot smoke, 147 of 147 targeted tests), the offline wire table, the probe gate before and after, the owner records and the switch output.
Adds lsof shim v2 to the new prefix (a client's dead connection no longer blocks a restart; reproduced and tested) and records the sharedgw connection
expiry of 05:50Z to 05:55Z and its repair. Text: decision record update, foundation-stack.md, the unit template's shim comment and the omniroute row
text of manifests/stack.json (build ids, carry, shim). 20129 and hindsight-live untouched; no settings write; the component pin stays 3.8.50.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@seathatflowsinourveins seathatflowsinourveins added the lane:shared Touches files owned by both lanes; needs both lanes' acknowledgement label Sep 30, 2026
@seathatflowsinourveins

seathatflowsinourveins commented Sep 30, 2026 •

Copy link
Copy Markdown
Owner Author

Trading lane acknowledgement (docs/lanes.md:146-150). Reviewed at head 2196413dee1a3a80d0c0b9a792a0e314a36c3c6b (base 7d0189117028907261d06926dee86844c1ae8f1e, which is origin/main at review time) by native-agent-stack-e0, which holds the trading lane.

  • Shared hot files (docs/lanes.md:26): in manifests/stack.json, 69 rows before and after with the same ids and order; only the omniroute row differs, in upstream_sources, freshness and command_scope; its version stays 3.8.50; no top-level key changes. manifests/evidence.json changes the entries of four files this PR edits (manifests/stack.json now sha256 265bcff0ed17a7f328abb783829fa6a8598f888badc31431e32f9874fe46e61e, 98,938 bytes, equal to the head's file) and adds 48 entries, all under evidence/artifacts/omniroute-sol-max-20260930/; no entry is removed and no other key changes (docs/lanes.md:94-97).
  • Trading paths: none of the 55 files is trading-owned (docs/lanes.md:25), and the added row text names no trading, paper, broker or us-equities component. No paper, recovery, monitor or overnight unit calls OmniRoute, so the 2026-09-30T06:32:50Z restart of 20128 recorded here touched no paper step.

No objection. Merge with this head pinned and 8/8 required checks in bucket pass (docs/lanes.md:153-167); if the head moves, this acknowledgement carries over only when the manifests/stack.json diff between the two heads is empty (docs/lanes.md:181-190).

@seathatflowsinourveins
seathatflowsinourveins merged commit cc1f6ce into main Sep 30, 2026
26 checks passed
@seathatflowsinourveins
seathatflowsinourveins deleted the res-omni-sol-max-20260930 branch September 30, 2026 07:17
seathatflowsinourveins pushed a commit that referenced this pull request Sep 30, 2026
main moved during this rebase: #534 restarted OmniRoute 20128 at
2026-09-30T06:32:50Z onto build cf6748d04, carrying the open upstream PR #15167
that adds gpt-6.1-sol to reasoningSuffix.ts's alias sets. The addendum's gateway
item read the earlier build (before 04:52Z) and stated the xhigh clamp in the
present tense. It now keeps that source reading in the past tense and adds what
#534's record shows (1,154 of 1,495 gpt-6.1-sol rows sent at xhigh before the
restart; cx/gpt-6.1-sol with body max sent at max after it; 20129 unchanged);
the Decision sentence and the preregistered comparison's reason for native
Codex follow. Nothing on either port was observed again here. The routing
record's attribution line says gateway-effort evidence.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
seathatflowsinourveins pushed a commit that referenced this pull request Sep 30, 2026
main moved during this rebase: #534 restarted OmniRoute 20128 at
2026-09-30T06:32:50Z onto build cf6748d04, carrying the open upstream PR #15167
that adds gpt-6.1-sol to reasoningSuffix.ts's alias sets. The addendum's gateway
item read the earlier build (before 04:52Z) and stated the xhigh clamp in the
present tense. It now keeps that source reading in the past tense and adds what
#534's record shows (1,154 of 1,495 gpt-6.1-sol rows sent at xhigh before the
restart; cx/gpt-6.1-sol with body max sent at max after it; 20129 unchanged);
the Decision sentence and the preregistered comparison's reason for native
Codex follow. Nothing on either port was observed again here. The routing
record's attribution line says gateway-effort evidence.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
seathatflowsinourveins pushed a commit that referenced this pull request Sep 30, 2026
main moved during this rebase: #534 restarted OmniRoute 20128 at
2026-09-30T06:32:50Z onto build cf6748d04, carrying the open upstream PR #15167
that adds gpt-6.1-sol to reasoningSuffix.ts's alias sets. The addendum's gateway
item read the earlier build (before 04:52Z) and stated the xhigh clamp in the
present tense. It now keeps that source reading in the past tense and adds what
#534's record shows (1,154 of 1,495 gpt-6.1-sol rows sent at xhigh before the
restart; cx/gpt-6.1-sol with body max sent at max after it; 20129 unchanged);
the Decision sentence and the preregistered comparison's reason for native
Codex follow. Nothing on either port was observed again here. The routing
record's attribution line says gateway-effort evidence.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
seathatflowsinourveins added a commit that referenced this pull request Sep 30, 2026
…ult GPT-6.1 Sol/Ultra with Astra escalation (unit D4) (#542)

* Pin Codex CLI 0.159.2 in the Linux pins; guard pin/manifest version agreement

adoption/pins-linux-x86_64.json codex entry: 0.157.1 -> 0.159.2 (npm wrapper
cf1e5d7b..., 4,904 bytes; platform package 84a6b35f..., 162,475,310 bytes), both
matched npm dist.integrity, npm audit signatures verified signatures and
attestations, SLSA provenance names rust-release.yml at refs/tags/rust-v0.159.2
(ff6aec96). The note now records that from 0.159.x the npm platform package's
vendor tree is the complete native package (44 files byte-identical to the
GitHub codex-package asset listed in codex-package_SHA256SUMS).

tests/test_adoption_status.py: PinManifestAgreementTests checks that every Linux
pin names manifests/stack.json's version of the same component (a " @ <commit>"
suffix is ignored), with a mutation self-check. It fails at this commit
(codex: pin 0.159.2, manifests/stack.json 0.157.1) and passes once the manifest
row moves in the last commit of this branch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Codex template default: GPT-6.1 Sol at ultra (user decision 2026-09-30); model-currency addendum

adoption/templates/codex.config.template.toml: model gpt-6-astra -> gpt-6.1-sol,
model_reasoning_effort stays ultra, with a comment naming the addendum; the
client-pin comment now cites the 0.159.2 qualification receipt. The judgment
lanes keep their gpt-6-astra bindings (stack-worker profile, landscape-sweep
lane, cx/gpt-6-astra OmniRoute profile), and tests/test_codex_worker_lane.py's
K2 assertion now reads the template's (model, effort) pair.

docs/decisions/2026-09-27-model-currency.md: dated addendum 2026-09-30 with the
GPT-6.1 Sol release (Codex changelog and models page, read 2026-09-30; the
announcement page answered 403), the client gate (rust-v0.159.1 bundled
catalog; offline codex debug models), the OmniRoute xhigh clamp for unregistered
ids read from the installed build's reasoningSuffix.ts and codex.ts, the user's
decision (6.1 Sol ultra default, Astra ultra for complex workflows), and the
preregistered #359-style comparison (A0, S1, S61-0, S61-1; the -0.02 micro-F1
bound) that overturns the lane tiers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Fold the Codex coordinator lane's Sol-primary routing defaults (2026-09-30)

Folded from the Codex coordinator lane's 2026-09-30 work in the main checkout
(snapshot tracked.diff sha256 5de56d6d81453ed3), D4's assigned files only:

- adoption/templates/codex.config.template.toml: both hunks, reconciled with
  this branch's header into one: Sol/Ultra coordinator with its rust-v0.159.2
  citations and the routing record; [agents] default_subagent_model
  gpt-6.1-sol with default_subagent_reasoning_effort max (child_config.rs
  L62-73, L204-249).
- adoption/templates/codex.stack-worker.config.toml: worker profile Sol/Max,
  Astra substitution for judgment or escalation (applied unchanged).
- tests/test_render_config.py (all hunks), tools/adoption/prove_codex_lane.py
  (live-worker line), recipes/README.md (worker command and effort paragraph):
  applied unchanged with git apply --include.
- tests/test_codex_worker_lane.py: only the profile-model, worker_pins,
  worker_command and recipe assertions; the TOP_RULE_SHA256 and word-count
  hunks are F1's; the template-model hunk is already covered by this branch's
  (model, effort) assertion.
- docs/harness-defaults.md: only the "Sol-primary quality defaults" paragraph.
- docs/decisions/2026-09-30-sol-primary-quality-defaults.md: verbatim, plus a
  dated attribution line linking the model-currency addendum.
- docs/decisions/2026-09-27-model-currency.md: the addendum now names that
  record as the routing contract and follows its routes (workers and generic
  children Sol/Max; Astra kept by the lanes that name it).

The Gate A runbook and preregistration arms, which pass -m gpt-6-astra
explicitly, are untouched. Hash registrations follow in the last commit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Codex 0.159.2 qualification receipt and the records that mirror the pin version

evidence/receipts/codex-01592-qualification-20260930.json (native_cli_e2e,
mirroring codex-01571-qualification-20260926): npm and GitHub artifact integrity
with failing controls, byte identity of the existing tools/codex-0.159.2 prefix
(49/49), credential-free bwrap checks of 0.159.2 against 0.157.1 (version, help,
mcp list/get shapes, features, prompt-input marker, offline bundled catalog),
source identity of the exec --json layer at the two tag commits,
prove_codex_lane.py --help and static checks, apply_codex_lane.py dry run, and a
read-only rollout/item-shape check with the repository's own parsers over the
host's 19 rollouts written by 0.159.2. No live model call; the host launcher
already resolved to 0.159.2 and this unit changed nothing on the host.

Records that mirror the manifest version, as the 0.157.1 switch (#348) moved
them: catalogs/landscape/upstream-snapshot.json codex entry (selected 0.159.2;
repo and releases/latest re-checked 2026-09-30, the rust-v0.159.2 commit through
git protocol after REST 403s), blueprints/token-native-focus/saturation-audit.json
codex row (version and the new receipt), tests/test_adoption_bootstrap_macos.py
MAC_PIN_LAGS_LINUX (Mac 0.155.1, Linux 0.159.2). The manifests/stack.json codex
row and the evidence registration follow in the branch's last commit
(docs/lanes.md hot-file protocol).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Codex worker lane: CODEX_VERSION 0.159.2 with the Linux pin; guard the two agree

tools/adoption/apply_codex_lane.py: CODEX_VERSION 0.157.1 -> 0.159.2, so the lane
applies on a host at the Linux pin (the dry run refused 0.159.2 with "[fail] codex
version: codex-cli 0.159.2 (pin 0.157.1)"). The exact-equality check is unchanged.
Its source citations were compared at the two tag commits (36650394, ff6aec96)
through raw.githubusercontent.com: config_manager_service.rs, agent-roles
loader.rs and discovery.rs are byte-identical; rmcp_client.rs keeps the 30 s
DEFAULT_STARTUP_TIMEOUT and its unwrap_or at L105 and L344 (L103 and L342 before).

tests/test_codex_worker_lane.py: the fake codex answers --version and doctor
--json as 0.159.2; the module, fake and ApplyFlowTests docstrings and the
integration skip message name 0.159.2; the DOCTOR shape note records that
doctor.rs differs at rust-v0.159.2 only in a handshake-error match arm. New
TemplateTests.test_the_lane_pins_the_linux_codex_pin checks CODEX_VERSION against
adoption/pins-linux-x86_64.json; it failed first ('0.157.1' != '0.159.2').

Opt-in CodexIntegrationTests against the 0.159.2 prefix's native binary
(sha256 1748767b...): 10/10 OK; with 0.157.1 on PATH all 10 skip.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Current-pin prose at Codex 0.159.2; macOS follow-up for the 6.1 Sol template default

recipes/README.md: the codex archive-hash row names rust-v0.159.2's
codex-package asset (9e2d29a7..., equal to its API digest and its
codex-package_SHA256SUMS line); the codex component row names 0.159.2 with its
release link and npm prefix, scopes the --search and daemon_auto_start
measurements to the versions that ran them, and points to the 0.159.2 receipt;
the stack-worker bullet describes the folded profile (gpt-6.1-sol at max, Astra by
-m on escalation); the rmcp_client.rs, mcp add --help, exec_events.rs and two
strict-config statements now also cite 0.159.2 where it was checked (source
compared at ff6aec96; the strict cases re-run through CodexIntegrationTests); the
PreToolUse/MCP sentence is scoped as not re-checked at 0.159.2.

adoption/bootstrap.md, adoption/platforms/linux-wsl2.md and macos-arm64.md: the
Linux codex pin history reads 0.155.1 -> 0.157.1 -> 0.159.2; the WSL2 terminal
measurement keeps its Codex 0.157.1 condition, now marked as before the move;
the macOS pin stays 0.155.1, and both pages name the follow-up: macOS needs its
own 0.159.x qualification before the template default applies there.

docs/decisions/2026-09-27-model-currency.md (addendum 2026-09-30): the worker_pins
line citation follows the file (298-304); the CODEX_VERSION move is recorded as
done here; a new follow-up paragraph records the macOS gap (bundled catalogs of
the Linux 0.155.1 and 0.157.1 builds lack gpt-6.1-sol, offline) and where a
per-platform model override would go (render_config.py render_one,
resolve_socraticode_version, pinned_version), not implemented.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Codex 0.159.2 receipt: the lane's constant move, its integration run and the macOS gap

evidence/receipts/codex-01592-qualification-20260930.json, amended in data and
text (id, kind and components unchanged):
- claim: the apply dry run failed its version precondition while CODEX_VERSION
  was 0.157.1 and passes after the move ('[ok] codex version: codex-cli 0.159.2
  (pin 0.159.2)', the 0.157.1 control now [fail]); the opt-in
  CodexIntegrationTests passed 10 of 10 on the prefix's native binary and skip on
  0.157.1; the static prove checks re-run byte-identical with this branch's file;
  the 0.155.1 build's bundled catalog also lacks gpt-6.1-sol.
- limitations: the constant move is no longer outside this unit; the npm-launcher
  and /tmp-bwrap runs of the integration tests and why they fail are recorded;
  the list of what moves now includes the lane and the current-pin prose; a new
  item names the macOS follow-up (its own 0.159.x qualification before the
  template default applies there) and the render_config.py override site.
- data: lane_checks gains prove_static_rerun, apply_dry_run_after_constant_move
  and integration_tests (the original dry-run line now names the base file);
  source_checks.lane_citations records the compared sources;
  checks_after_the_constant_move holds mcp add --help, the offline bundled
  catalogs of 0.155.1, 0.157.1 and 0.159.2, and the strict-config stderr.
- provenance: the base-sha entries of prove_codex_lane.py and apply_codex_lane.py
  now say so, and this branch's two files, the test module and the two new
  scratch scripts are listed with their sha256.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Model-currency addendum: 20128's 6.1 Sol effort after #534's restart

main moved during this rebase: #534 restarted OmniRoute 20128 at
2026-09-30T06:32:50Z onto build cf6748d04, carrying the open upstream PR #15167
that adds gpt-6.1-sol to reasoningSuffix.ts's alias sets. The addendum's gateway
item read the earlier build (before 04:52Z) and stated the xhigh clamp in the
present tense. It now keeps that source reading in the past tense and adds what
#534's record shows (1,154 of 1,495 gpt-6.1-sol rows sent at xhigh before the
restart; cx/gpt-6.1-sol with body max sent at max after it; 20129 unchanged);
the Decision sentence and the preregistered comparison's reason for native
Codex follow. Nothing on either port was observed again here. The routing
record's attribution line says gateway-effort evidence.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Codex 0.159.2 receipt: withhold the quoted host client configuration

data.host_resolution.config_toml_top_level_model quoted the two top-level model
keys of the host's active ~/.codex/config.toml. AGENTS.md keeps machine-specific
active client configuration out of evidence, so the value is withheld; the entry
still records that the file was read once, read-only, at 2026-09-30T05:37:50Z.
Claim and limitations are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Codex 0.159.2 receipt: scope the dry-run refusal to what each run printed

The claim said each dry run after the constant move refused only on the three
preconditions an empty scratch home cannot meet; the 0.157.1 control printed a
fourth [fail] line, its codex version. The claim now scopes "only the three" to
the 0.159.2 run and says the control adds its version line.
data.amended_at_utc is the time of this last amendment.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Codex user template: CODEX_MODEL from the platform's Codex pin (review of #542)

The template set model and default_subagent_model to "gpt-6.1-sol" on every platform, while
adoption/pins-macos-arm64.json pins Codex 0.155.1, whose bundled catalog has no GPT-6.1 entry. Both keys now read
${CODEX_MODEL}, which tools/adoption/render_config.py fills from the selected platform's Codex pin as it fills
SOCRATICODE_VERSION: gpt-6.1-sol from Codex 0.159.1, gpt-6-astra before it. --set CODEX_MODEL=<model> names
another; --out and --check print a derived value with its pin and sources.

The threshold is 0.159.1, not 0.159.0: openai/codex codex-rs/models-manager/models.json has no "gpt-6.1-sol" slug
at rust-v0.159.0 (687a119f) and one at rust-v0.159.1 (8e68a98e, line 178), whose release notes read "Added GPT-6.1
Sol as the default model in the bundled catalog". At rust-v0.155.1 (be2951ea) models.json lists gpt-6-astra with
efforts low to ultra, and config/src/config_toml.rs L694-696 reads both [agents] default_subagent keys.

The stack-worker profile keeps its literal gpt-6.1-sol: apply_codex_lane.py installs it verbatim, worker_pins()
passes its model as -m, and the lane refuses any codex but CODEX_VERSION (the Linux pin). test_profile_template
now asserts that the literal equals the rule for lane.CODEX_VERSION.

Tests: CodexModelTests (both platforms, the 0.159.0/0.159.1 boundary, a host override, a platform without pins
failing closed, the --out/--check note) failed first against the unchanged renderer and template (9 run: 6
failures, 12 errors). The K2 check in test_omniroute_profile_template reads a Linux render, and the strict-config
integration fixture fills CODEX_MODEL from the rule.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Docs and receipt: CODEX_MODEL keeps gpt-6-astra on Codex pins before 0.159.1

- docs/decisions/2026-09-27-model-currency.md, addendum 2026-09-30: the template lines now read the placeholder
  (lines 7-8 and 30-31), the table row cites the Linux render, the "Still open" list names the rule, and the macOS
  follow-up records the placeholder, its upstream source and the offline prompt-input check instead of "It is not
  implemented here".
- evidence/receipts/codex-01592-qualification-20260930.json: limitations[12] states the placeholder, and the new
  data.checks_after_the_constant_move.template_model_per_platform records the per-platform renders and a
  no-network `codex debug prompt-input` check: the 0.155.1 build over the macOS render includes Ultra's
  multi_agent_role and multi_agent_mode developer messages, drops both when only the two model values are set to
  gpt-6.1-sol, and 0.159.2 includes both over either render. Linux builds only; no model call.
- adoption/platforms/macos-arm64.md and adoption/bootstrap.md: one clause each on the macOS render and the new
  derived placeholder.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Provenance wording for the folded Sol-defaults record: no inferred author (Codex runtime lane's request)

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* Sol-defaults record: Astra/Ultra coordinates a complex workflow, Astra/Max takes a single consequential judgment

The user's 2026-09-30 selection named "astra ultra when tasks needed suitable for complex workflow"; the catalog
semantics in this record (Ultra = proactive delegation with xhigh reasoning, Max = the highest reasoning effort)
split the escalation accordingly. Docs only.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* Re-register the changed hash-listed files in manifests/evidence.json (hot-file protocol)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Scout <scout@local>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lane:shared Touches files owned by both lanes; needs both lanes' acknowledgement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant