ci: add trusted release provenance

[Deathcharge]

Summary\n- smoke-install the one built wheel across Python 3.10–3.13\n- add immutable-action and version-consistency supply-chain contract tests\n- add a tag/version-gated release workflow with exact-source tests, GitHub SLSA provenance, and PyPI Trusted Publishing\n- document one-time owner setup, manual approval, verification, rollback, and incident response\n- disable checkout credential persistence and release dependency caching\n\n## Safety boundary\nMerging or manually dispatching this workflow cannot publish. Publication requires a new matching version tag, a configured PyPI Trusted Publisher, and approval through the protected pypi environment. No long-lived PyPI secret is used.\n\n## Verification\n- Ruff lint/format: passed\n- strict mypy: passed\n- pytest: 133 passed\n- source/wheel build and Twine checks: passed\n- hosted tests and package builds: green\n- hosted installed-wheel smoke tests: green on Python 3.10–3.13\n- workflow YAML accepted by GitHub Actions\n- zizmor 1.29.0 offline audit: no findings (9 intentionally suppressed informational contexts)\n- all third-party actions pinned to immutable commits\n\n## Primary guidance\n- PyPA recommends OIDC Trusted Publishing for GitHub-hosted packages\n- the official publisher produces PyPI attestations by default\n- GitHub �ctions/attest records SLSA provenance for the built distributions\n\n## Bootstrap note\nGitHub cannot manually dispatch a new workflow until it exists on the default branch (pre-merge API response: 404). A non-publishing manual run will be executed and verified immediately after merge.

[coderabbitai]

Warning

Review limit reached

@Deathcharge, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 57ef4147-a625-447a-a391-8167ab73a9b2

📥 Commits

Reviewing files that changed from the base of the PR and between 86fa3a3 and d2d6eee.

📒 Files selected for processing (6)

• .github/workflows/ci.yml
• .github/workflows/release.yml
• CHANGELOG.md
• README.md
• docs/RELEASING.md
• tests/test_release_contract.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}