[abruption]

Summary

Make current installation guidance point to publication evidence instead of the obsolete v1.3.2 preparation checkpoint. Add a separate dated publication record to all four release notes/runbooks and make the existing post-publication documentation step explicit for future releases. Correct the four paired guides' stale unreleased wording to the diagnostics published in v1.3.2.

Refs #351

The four original release-note preparation bodies and complete original runbook bodies remain byte-identical to the released source. Existing tags, immutable assets, runtime version/code, skill snapshot and operational services are untouched. Package publication remains distinct from Control deployment, receiver updates/restarts and independently managed skills.

Evidence and validation

• Fresh read-only checks on 2026-10-29 independently verified GitHub release metadata, the actual tag reference resolving to commit f5e7c49554ff02771990a151e00b52f2abf3df0a, and the PyPI record. The original PyPI file set contains exactly two non-yanked files, not a filtered subset.
• Downloaded the published release-provenance.json and authenticated its attestation against the exact repository/prepare workflow/main reference/source digest/GitHub OIDC hosted-runner identity. Its wheel/sdist hashes match the independently read PyPI hashes. This resolves source attribution beyond target_commitish alone.
• GitHub publication: 2026-10-28T01:52:40Z. PyPI wheel/sdist: 2026-10-28T01:55:11.612762Z / 2026-10-28T01:55:13.659910Z. Exact source/hash records are in the documents.
• Python 3.9.6, macOS arm64: 70 documentation/i18n/release-consistency tests pass; generator and diff checks pass. Root independently verified all eight historical bodies against the original source. Tests are consistency regressions, not substitutes for querying external publication facts.

Independent and translation review

Pre-PR Claude Code 2.1.312 (requested and response-confirmed claude-opus-5-5) and Codex CLI 0.165.0 (isolated default, actual model ID not exposed) reviewed frozen input SHA-256 23055c106a46819b7db872848d3c931e7d64362fad9542bc445c449ede0b0998 in parallel, without tools/writes/tests/network. Both requested actual tag/source evidence, which was then independently verified. Their optional checklist hierarchy/locale-anchor suggestions were applied and retested; original preparation bodies remain unchanged.

Separately, Antigravity CLI 1.4.8 / explicit gemini-3.8-flash-medium performed fresh plan+sandbox read-only translation QA on the changed English/Korean/Japanese/Simplified Chinese content (123.613 seconds, structured success, no material findings). Input SHA-256: 7d25b20c9448848500fcc8ba32c7408e381dabafa6af3f0f3f898aefde10ba2f. Codex verified metadata, links, wording and history preservation. The later heading-level-only adjustment is not claimed as a second Gemini review.

No new native/ACK/live-OAuth/fleet acceptance or advance publication claim is introduced, and no existing release is rebuilt or republished for this wording fix.

[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-29T13:20:31.308414Z	846961d	PR opened
🔒 Security Review	✅ Completed 2026-10-29T13:20:46.716932Z	846961d	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.

[abruption]

Current-head verification

Reviewed head: 846961d03e05b2ee865f77615a60184b7df792ca. All 32 checks succeeded, including CI 40880800200. The PR is Ready.

Automatic code and security reviews both report completed at this exact head. Code findings flags are false; security finding flags are null/unavailable, so they are not represented as an affirmative false result. No review threads are posted.

70 documentation tests pass. Historical preparation/runbook bodies are preserved. Fresh tag resolution, signed provenance and the exact two-file PyPI metadata/hash set support the dated publication record; existing release assets are unchanged.

GitHub closingIssuesReferences is empty: this PR references issue #351 without scheduling automatic issue closure. No merge, tag, publication or operational change was performed.