[thirtytwobits]

Release creation can succeed while GitHub's releases list still omits the new draft. The script then stops even though CI passed. This replaces the release flow with one command that publishes the header's X.Y.Z version and continues matching interrupted attempts automatically.

• Remove prerelease versions, promotion paths, and the separate version/resume options. The version comes from the committed public header.
• Verify the exact main push, all required CI jobs, and its bundle before creating a tag. A failed verification leaves that version available for a corrected commit.
• Retain creation/publication responses and use release and immutable asset IDs for subsequent reads and downloads. Request fresh metadata and retry delayed asset/publication visibility. Recover lost write responses without creating or publishing twice.
• Deploy the published documentation archive through a separate main-only Pages workflow. Trusted main code verifies tag ancestry, successful source CI, bundle identity/checksums, and the displayed version before deployment.
• Remove synthetic CI release tags and repeated compiler builds for documentation deployment. Keep immutable tag/asset checks and protection against rolling documentation backward.
• Reduce RELEASING.md to the normal command and automatic retry behavior.

Validation:

• 78 tests passed on Python 3.14.6, including stale release lists, delayed asset listings, lost creation/publication responses, failed CI followed by a corrected commit with the same version, and merged/unmerged deployment tags, and asset downloads when tag discovery or server digests are unavailable.
• Pyright reports zero errors/warnings. Both workflows pass actionlint; git diff --check passes.
• Downloaded real documentation from main CI, verified its displayed 2.0.0 version, generated/verified a stable bundle, and compiled/ran C++14 and C++20 consumers using its extracted headers.
• Verified a live asset-ID download against the official GitHub CLI checksum asset, including byte length and server SHA-256 digest.
• Checked each workflow action's latest official release and declared runtime before editing.

Existing remote releases, tags, and Pages content were left unchanged. Hosted CI runs on this PR.

[thirtytwobits]

@codex review

[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-24T22:10:54.673229Z	bafcf5f	Manual request

ℹ️ 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: Didn't find any major issues. Nice work!

Reviewed commit: bafcf5f9c6

ℹ️ 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".