Codex rtk hook decision: record the 705h acceptance, its two boundaries and the refresh that landed

[seathatflowsinourveins]

Scope

• What this PR changes, in one or two sentences: records in the Codex rtk hook decision record that 705h (Sol, through 5f) accepted the guard at 14a8b119f with no P1 or P2, adds its two unverified boundaries to the residuals (no atomic snapshot across listing, loading and the trust grant; no enforcement after a later change of the rules, filters, HOME or XDG paths or the hook's environment) and notes that the head that landed (118f579ff) differs from the accepted one only in the regenerated new-WSL handbook outputs and their receipt. It also qualifies the record's opening Status paragraph (written 2026-10-04) with the landed pull requests: PR 684 ba1f6876c, the first of the two Codex rtk hook: a narrow trust tool, the qualification evidence and its decision record (first of two) #701 287514581, the second Codex rtk hook: the plan's command-output row installs and trusts it (second of two; the user's relayed pointer yes) #705 0ce953696 (5f's read of 79622e8e7, one P2). Record-only; no code, plan or generated file changes.
• Base commit: 0ce953696
• Lane: lane:foundation (the same lane as Codex rtk hook: the plan's command-output row installs and trusts it (second of two; the user's relayed pointer yes) #705)
• Owned paths touched: docs/decisions/2026-10-04-codex-rtk-hook-qualified.md and its registry row in manifests/evidence.json (last commit, hot-file protocol).

SOTA sources

• No new source: a record-only follow-up to Codex rtk hook: the plan's command-output row installs and trusts it (second of two; the user's relayed pointer yes) #705, which cites its sources in full. The facts added here rest on the same ones: rtk-ai/rtk v0.51.0 (e001f773f80b22b7dc4c7a79521b30e35aaef026); openai/codex rust-v0.159.3 (01fc69f4026735edfdf6789820549727a4867b11: codex-rs/tui/src/hooks_rpc.rs L58-L91, trust written by config/batchWrite) and rust-v0.160.0 (a956835d0207: codex-rs/core/src/exec_policy.rs L1121-L1170, the rules read when a session loads them).
• The 705h read is our own cross-family review of the integration (Sol through 5f), recorded as a review, not as an upstream source.

Evidence-class table

Claim	Evidence class	Command / receipt
705h accepted 14a8b119f: no P1, no P2, both 705g P1s fixed against the real binaries, two boundaries not verified	source_review (cross-family read; verdict held by 5f)	the decision record's review-rounds paragraph
28 of the 31 owned files are patch-id-equal between the accepted head and the landed head; the other three are regenerated handbook outputs and their receipt	local_integration (git diff -U0 per file, git patch-id --stable)	computed on the #705 branch before the merge; reproducible from 14a8b119f against its base and 118f579ff against cb339488e
The probes ran codex-cli 0.159.3 and rtk 0.51.0; rust-v0.160.0 was read from source; no fresh model session	local_integration and source_review	already recorded by #705; restated as the boundary

Local commands run

$ python3 scripts/validate.py
{"components": 69, "hashed_files": 10169, "profiles": 4, "receipts": 204, "status": "passed"}
$ python3 scripts/validate_convergence.py --all-recorded
record[30]: valid
$ python3 -m unittest tests.test_component_matrix tests.test_evidence_manifest tests.test_new_host_grand_list tests.test_validate tests.test_codex_hook_trust
Ran 253 tests ... OK
(no test module names the decision record; gitleaks on each commit: no leaks found)

Decision record

docs/decisions/2026-10-04-codex-rtk-hook-qualified.md (the residuals and review-rounds paragraphs).

Host evidence

Not applicable (no files under evidence/hosts/).

Checklist

• New/changed GitHub Actions are pinned to a full commit SHA with a version comment (no workflow changed).
• New/changed workflows declare top-level permissions: {} (no workflow 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.

🤖 Generated with Claude Code

[seathatflowsinourveins]

Claude session native-agent-stack-5f: landing at head e80d25b4b22c6a14dfd2821f79bcd29c8dd00e98. The command center (wsl-architecture-design) gave its ACK at this exact head; under the user's 2026-10-04 decision it owns merges that touch the hot registry. The read-only cross-family review (GPT-6.1 Sol max, the packaged Codex SDK worker) returned FINDINGS at 79622e8e7adf; this head is reached from it through recorded carry edges (equal owned patch-ids, or a cross-family delta read returning ACCEPT at the edge's target), with no P1 item.

Observed main bea3d7f24f091ca19fcf264f5bce32a8e476c936. coordination/merge_tree_landing_check.py (sha256 a11649fcf2e5844c…) exit 0:

main bea3d7f24f091ca19fcf264f5bce32a8e476c936 head e80d25b4b22c6a14dfd2821f79bcd29c8dd00e98 base 0ce9536963644940fdf68b578269e838b8c098ee merged-tree 0a10bc39c7132371a31537c61dea40d11e161c1c merge-tree-exit 0
ok   1: clean three-way merge
ok   2: merged-vs-main paths 2, outside PR-owned 0 []
ok   3: main drift 85 paths, overlap with PR-owned inputs (registry excluded) []
ok   4: registry foreign rows equal True, order preserved True, PR-owned rows 1, unowned top-level keys differing []
ok   5: merged files[] sorted by path with no duplicates: True (10187 rows)
LANDABLE
condition 5: merged files[] sorted and unique (tree 0a10bc39c7132371a31537c61dea40d11e161c1c)

Required checks at this head: 7 pass . Unresolved review threads: 0.

[seathatflowsinourveins]

Claude session native-agent-stack-5f: post-merge observation. Landed as 9e955327702e6b7a8dd1909b2884196726a15ba5 (parent bea3d7f24f091ca19fcf264f5bce32a8e476c936), tree 0a10bc39c7132371a31537c61dea40d11e161c1c. The landed tree equals the checked merged tree and the parent is the observed main.