Codex roles: reconcile the RTK exceptions block (F4) with rtk 0.51.0 measurements

[seathatflowsinourveins]

Scope

Reconcile the Codex RTK exceptions with RTK 0.51.0 and repair the stale otel.environment citation. This custody update scopes the proxy recommendation to the listed exceptions and protects bare non-directory find names, including existing regular files. It refreshes the template's ten role carriers, current expected pins, native client block and checksum projections while preserving the upstream awareness block, role settings, original decision text and three historical measurement artifacts.

• Content-repair base: b0b9f7522f27661a000a9f28f2a86dbca3ac6628; source fix b5d1323311a1657da914ce780d90a22b670947fe, final head 53c5153aa661fb37ea242ee8c4ffadfe8da6e3d0. No rebase in this update.
• Lane: lane:foundation.
• Owned paths: Codex instruction template and role carriers, renderer expectations, README, one catalog citation, an appended decision amendment and a new follow-up receipt. Registry and checksums are committed last.
• The compact template is 8,191 bytes against the unchanged 8,192-byte bound.
• Exclusion behavior depends on the installed RTK configuration; an explicit RTK prefix bypasses exclusions. This PR installs no exclusion configuration, hook or trust entry; Codex rtk hook: the plan's command-output row installs and trusts it (second of two; the user's relayed pointer yes) #705 owns that route.
• The live description corrects the previous unlimited compact-log claim: upstream compact formats default to a 50-commit limit without an explicit count. The earlier 16-commit observations remain historical evidence and do not establish complete-history preservation.

Landing path: legacy READY PR assigned to this lane by command-center review023012Z, rank40. The co-op performs the new-head delta read with CI at <head>; the command center ACKs; 5f performs the single landing rebase and lands in rank order. That composition retains #803's seventh exception and #819's routing changes and must compact the combined carrier within its unchanged byte bound. Static literal preservation gives 8,191 plus the 163-byte SKILL line = 8,354, exceeding the strict <8192 bound; this is a prediction, not merged-head qualification. codex_roles.py:103-113 here and :106-116 in #803/#819 must be composed: retain the corrected bare-name/raw-diff clauses, the seven-exception citation/count and the navigation rules, rather than taking either module wholesale. The command center assigned the scoped trim and native read-back to the landing turn (A19/Q19). This content push neither lands nor changes host configuration.

SOTA sources

• rtk-ai/rtk v0.51.0, e001f773f80b22b7dc4c7a79521b30e35aaef026, find dispatch:134-147: bare non-directory inputs use legacy pattern syntax.
• Same upstream pin, compact log default:1816-1824: default 50-commit cap.
• native-agent-stack@b0b9f7522f27661a000a9f28f2a86dbca3ac6628:tools/adoption/codex_roles.py:284-287 and the repository client-config --write-blocks helper: native carrier rendering. docs/lanes.md:94-128 supplies the registry/checksum-last protocol.
• Codex rtk hook: a narrow trust tool, the qualification evidence and its decision record (first of two) #701's unchanged probe and exclusion fixture, and evidence/artifacts/rtk-f4-remeasurement-20261004/, support the prior RTK observations. Their values are preserved and no probe was replayed for this update.
• native-agent-stack@53c5153aa661fb37ea242ee8c4ffadfe8da6e3d0:examples/codex-native/README.md:199 and catalogs/foundation/upstream-surface-dispositions.json:3290 provide the exact otel.environment source locator; only the locator changes, preserving the row's recorded value, reason and review date.

Evidence-class table

Claim	Evidence class	Command / receipt
Bare-name dispatch and compact-log default	source_review	Pinned upstream locators above
Earlier RTK rewrite, exclusion and exit behavior	Historical local_integration	Existing unchanged 2026-10-04 probe artifacts; no new run
Current rendered carriers, protected bytes and role settings	local_integration	Native renderer, byte comparisons and checksum checks; custody receipt
Current expected instruction/citation controls	synthetic	Existing test modules and mutation controls; no upstream acceptance claim

Local commands run

One combined run of the six touched modules, under CI=true/umask022 and nice19/ionice-c3:

python3 -B -m unittest tests.test_codex_agents tests.test_codex_worker_lane tests.test_managed_block tests.test_codex_roles tests.test_new_wsl_client_config tests.test_upstream_surface_watch
exit0; 502 tests / 133.918 seconds / 18 skips
python3 tools/adoption/new_wsl_client_config.py --check
exit0; inherited mcp-inspector plan warnings retained
sha256sum --check --strict SHA256SUMS
exit0 in both Codex checksum directories (two carrier and three worker files)
host_receipts.register_file for 22 changed/new inputs
exit0
python3 scripts/component_matrix.py --write
exit0; no generated content diff
python3 scripts/new_host_grand_list.py --write
exit0; no generated content diff
python3 scripts/validate.py
exit0; 69 components / 10,098 registered files / 4 profiles / 202 receipts
git diff --check
exit0; final worktree clean

The full upstream-surface module includes both previously failing disposition assertions; no duplicate focused run, full repository matrix, RTK probe or model call. Complete logs are durable at lanes/codex-token-parity-work/709-20261007/. The new receipt records actual test/render checks; validator acceptance is recorded externally in the status and this body, leaving its validator field null to avoid claiming a result before validation. Independent source review confirmed the exact protected bytes, all ten role settings and the scoped citation. Last commit contains only the two Codex SHA256SUMS files and evidence registry. Fresh hosted CI and command-center acceptance at the new head remain pending.

Decision record

docs/decisions/2026-10-04-rtk-051-f4-exceptions.md, appended Amendment (2026-10-07). Original 16,010-byte decision prefix and its recorded results are byte-identical. New follow-up: evidence/artifacts/rtk-f4-custody-20261007/receipt.json.

Host evidence

No new host receipt or host change. No real client file, hook configuration, trust store, credential file or service was read or modified by this update. Historical scratch-HOME runs remain dated observations. Fresh host acceptance belongs to the command center's approved route.

Checklist

• No GitHub Actions change.
• No secret value or credential file read, printed or committed; no new required secret.
• No paid hosting or billing surface.
• Peer-owned files and worktrees preserved.
• Source owner repairs content only; co-op/command center/5f retain review, ACK and landing custody.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-05T02:41:39.365817Z	49ba964	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 49ba964d18

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".