New-WSL: Codex 0.160.0 profile pins, main-checkout Codex trust grant, Opus 5.5 model (follow-up to #626) - #683

Scope

• What this PR changes: the coordinator's follow-up to Codex 0.159.3 -> 0.160.0 with the Python SDK pair: pins, qualification receipt, tests and checkpoint #626 for the new WSL distribution (NativeStack2604). (1) The new-WSL profile, its overview, handbook and handbook receipt move the Codex CLI and the Python SDK (openai-codex) to 0.160.0. (2) The client-config builder pre-trusts the main repository checkout in Codex as an authorization setting. (3) The builder pins NativeStack2604's Claude main model to Opus 5.5 (claude-opus-5-5).
• Base commit: f77a35eb2bf30bc4bf6f3b4ee51bc9ce5397b4c5 (the merge of Codex 0.159.3 -> 0.160.0 with the Python SDK pair: pins, qualification receipt, tests and checkpoint #626; origin/main had not moved at push time)
• Lane: lane:foundation (all paths are foundation-owned per docs/lanes.md; the manifests/evidence.json change is only the hot-file re-registration)
• Owned paths touched: adoption/new-wsl-profile.{json,md}, adoption/new-wsl/client-config-map.json, tools/adoption/new_wsl_client_config.py, tools/adoption/codex_home.py, docs/new-wsl-handbook.{json,md}, docs/decisions/2026-10-02-new-wsl-client-configuration.md, evidence/artifacts/new-wsl-handbook-20261001/receipt.json, tests/test_new_wsl_profile.py, tests/test_new_wsl_client_config.py, tests/test_bootstrap_full_profile.py, manifests/evidence.json (last commit, alone)

SOTA sources

• openai/codex rust-v0.160.0 (release published 2026-10-01T20:19:13Z, target commit a956835d020762cb2b570053af06f643a11c0ecc; read 2026-10-04):
  • codex-rs/tui/src/config_update.rs L264-279: a project's trust entry is found by exact key, case-insensitively only for a Windows path. L305-337: the lookup tries the cwd, then the project root, then the git trust root. L338-366: a saved trusted level asks nothing.
  • codex-rs/git-utils/src/trust.rs L12-24: resolve_root_git_project_for_trust resolves a linked worktree to the main repository's root.
  • Upstream tests codex-rs/core/src/git_info_tests.rs L829-968: a worktree and its nested directories resolve to the main root; missing metadata, a mismatched backlink, a mismatched commondir and a symlinked .git are refused.
  • codex-rs/config/src/loader/mod.rs L131-133: project config layers are "loaded but disabled when untrusted".
  • openai/codex#49160, merge commit 0d7b8117d3cc6d9ffe21d22375d70307133e9f16, an ancestor of rust-v0.160.0 (compare: behind_by 0): "Let /cd request folder trust".
  • Release-asset digests from https://api.github.com/repos/openai/codex/releases/tags/rust-v0.160.0: codex-package-x86_64-unknown-linux-musl.tar.gz 4fcc47ab…, codex-x86_64-unknown-linux-musl.tar.gz 30686541….
• npm @openai/[email protected] (https://registry.npmjs.org/%40openai%2Fcodex/0.160.0): tarball integrity sha512-kEtVGzj…, equal to the local rehash. PyPI openai-codex==0.160.0 (https://pypi.org/pypi/openai-codex/0.160.0/json): wheel sha256 61d2d855….
• Claude Code model configuration, https://code.claude.com/docs/en/model-config (read 2026-10-04T07:03Z): the opus alias resolves to Opus 5.5 on the Anthropic API; "To pin to a specific version, use the full model name, for example claude-opus-5-5"; Opus 4.7 and later run with the 1M window on the Anthropic API without a [1m] suffix.
• In-repo references followed: Codex 0.159.3 -> 0.160.0 with the Python SDK pair: pins, qualification receipt, tests and checkpoint #626 (merge f77a35eb2) and its withdrawn profile commits f51b3e06, fbbd9393, 5cb4d06f and the withdrawal 9bb0b1e9; adoption/pins-linux-x86_64.json, manifests/stack.json, adoption/sdk/requirements-linux-x86_64-py313.lock and evidence/artifacts/runtime-sdk-20261003/{receipt,qualification-facts}.json at main; the handbook generator record docs/decisions/2026-10-01-new-wsl-handbook-generator.md L665 (receipt hashes follow the regenerated files); the client-config record's open observation at L699-702 (trust pieces belong in the authorization class).

What changed and why

1. Codex 0.160.0 in the new-WSL profile (commit c320b11ee). Every version-bound field of the Codex and Codex Python SDK rows reapplies Codex 0.159.3 -> 0.160.0 with the Python SDK pair: pins, qualification receipt, tests and checkpoint #626's withdrawn values unchanged: tarball name, URL, sha256 37351776… and 4,902 bytes; wheel URL and sha256 61d2d855…; install, README and quickstart sources at rust-v0.160.0; release tag and published_at; source_commit a956835d; the native-update floor; and the two release-asset digests. Each value was checked against main's pins, stack manifest, SDK lock and Codex 0.159.3 -> 0.160.0 with the Python SDK pair: pins, qualification receipt, tests and checkpoint #626's receipt, and live against GitHub, npm and PyPI. Both archives were downloaded and rehashed again on 2026-10-04.
   • Provenance differs from the withdrawn hunks on purpose. They said "pending_pr_626" because Codex 0.159.3 -> 0.160.0 with the Python SDK pair: pins, qualification receipt, tests and checkpoint #626 was open then. Codex 0.159.3 -> 0.160.0 with the Python SDK pair: pins, qualification receipt, tests and checkpoint #626 merged at f77a35eb2 on 2026-10-04T06:53:20Z, so the rows follow the Qualify Codex 0.159.3 and align the SDK pair #580 pattern already in the file: sdk_gate Codex 0.159.3 -> 0.160.0 with the Python SDK pair: pins, qualification receipt, tests and checkpoint #626, sdk_gate_status: merged_at_2026-10-04T06:53:20Z and accepted_main: f77a35eb2….
   • Unchanged: the TypeScript SDK row (Codex 0.159.3 -> 0.160.0 with the Python SDK pair: pins, qualification receipt, tests and checkpoint #626 pinned no @openai/codex-sdk), the top-level source_head (bound by the test's HEAD) and the dated codex update --help observation.
   • Regeneration: the test hunk is Codex 0.159.3 -> 0.160.0 with the Python SDK pair: pins, qualification receipt, tests and checkpoint #626's, verbatim. The handbook was regenerated with build_new_wsl_handbook.py --write. In the receipt, only profile_sha256 and the two outputs hashes move; the generator hash and the inventory are unchanged.
2. Main-checkout Codex trust grant (commit 8d5817f96). The shared Codex template already has a templated piece, projects."${PROJECT_ROOT}".trust_level, and NativeStack2604's host template sets PROJECT_ROOT to the native-agent-stack checkout in the home. No new template slot or literal path is needed.
   • Map entry: the piece gets its own entry, citing the sources above and the coordinator's decision of 2026-10-04 (R16 review: the dialog is acceptable, our roots pre-trusted, unknown projects still prompting).
   • Class authorization:, not practice: the tool's own definition ("suppresses a confirmation") and the record's open observation both say so. is_authorization_piece gains one pattern, codex/*/projects.*.trust_level. The grant is rendered and written only with --with-authorization-settings, and never over a file's own answer. The publication checkout's grant stays not wired.
   • Fresh Codex home: codex_home.py dropped every [projects] table from a config.toml it created, so the apply would have reported the grant "added" without writing it. It gains an additive --keep-project-trust (the mirror of --keep-hook-trust), which the builder passes. The bootstrap passes neither flag, so its output is byte-identical.
   • Merge report: the merge looked an authorization piece up by its template path. A grant the file already had was therefore reported "added". The lookup now fills placeholders as the render does.
3. NativeStack2604 model Opus 5.5 (same commit). A practice map entry overrides the shared template's model with claude-opus-5-5 for the new distribution only, quoting the user's choice of 2026-10-04. The additions file cannot carry it: merge_additions refuses a key the shared template defines, and a map override is the builder's mechanism for that. advisorModel stays fable.
4. Hot-file re-registration (commit 6b68939ac, alone): seven files main's manifest lists. component_matrix.py --write and new_host_grand_list.py --write changed nothing.

Deviations from the brief

• Part 3 premise. No builder input held sonnet. The builder already rendered the shared template's opus[1m], which resolves to Opus 5.5 on the Anthropic API today. The "sonnet" is most likely a live host's saved /model choice: the docs say /model saves to the settings model, and docs/decisions/2026-09-29-sonnet-5-5-dispatch.md L31 records a Sonnet 5.5 user setting on the workstation. This PR does not change the resolved model; it pins NativeStack2604 to the user's explicit choice, independent of the shared template. The next builder --apply overwrites a saved sonnet, because template scalars win (Decision 12).
• The trust grant needs the option. The recipe's F9 --apply line is the plain one, so the grant is written only when the coordinator adds --with-authorization-settings, exactly as for approval_policy = "never" today.
• Two changes outside the three listed builder files: tools/adoption/codex_home.py (additive flag) and the 2026-10-02 decision record (generated tables, counts and a 2026-10-04 addendum, all required by its tests).
• Not changed: the recipe's F9 paragraph (adoption/platforms/linux-wsl2-new-distro.md L1013-1027) lists the authorization settings without the new grant. Its statements remain true for its plain --apply line. The page is hash-bound by the handbook and by blueprints/convergence-practice/wsl-new-distro-image-20261001/experiment.json, so updating it is a separate re-freeze.

Evidence-class table

Nothing here is native_proven. No client ran and no model was called. Nothing was applied to NativeStack2604 or to any host.

Local commands run

$ python3 -m unittest tests.test_new_wsl_profile tests.test_new_wsl_handbook tests.test_install_claude_profile tests.test_render_config
Ran 204 tests ... OK            (exit 0)
$ python3 -m unittest tests.test_new_wsl_client_config tests.test_bootstrap_full_profile tests.test_new_wsl_definitive_defaults
Ran 267 tests ... OK            (exit 0)
$ python3 -m unittest <14 other modules that load codex_home.py, the map, the builder, the profile or the record>
Ran 1848 tests ... OK (skipped=13)   (exit 0)
$ python3 tools/adoption/new_wsl_client_config.py --check
pieces: 385; wired: 293; not wired: 79; authorization: 13 / check passed   (exit 0)
$ python3 scripts/build_new_wsl_handbook.py --check
"status": "passed"              (exit 0)
$ python3 scripts/new_host_grand_list.py --check ; python3 scripts/component_matrix.py --check
passed / checked                (exit 0, exit 0)
$ python3 scripts/validate.py
{"components": 69, "hashed_files": 9864, "profiles": 4, "receipts": 195, "status": "passed"}   (exit 0)

Decision record

docs/decisions/2026-10-02-new-wsl-client-configuration.md, "Addendum 2026-10-04: the main checkout's Codex trust grant and the model". It names the sources, the alternative classes and what would overturn each decision: Codex matching trust by a parent directory or another key form; a decision that the root should ask again; or the user choosing another model or the floating opus alias.

Host evidence

Not applicable: no file under evidence/hosts/ changes.

Checklist

• New/changed GitHub Actions are pinned to a full commit SHA with a version comment (none changed).
• New/changed workflows declare top-level permissions: contents: read (none changed).
• No secrets are printed, logged or committed; no new required secret was added.
• No new paid hosting, subscription or billing surface was introduced.
• Peer-owned untracked files and worktrees were preserved (work done only in the owned worktree).

🤖 Generated with Claude Code