docs: record v2.0.0a7 release evidence

[Deathcharge]

Summary

• update the default installation path to immutable prerelease v2.0.0a7
• record the exact tag, source commit, CI/release runs, published asset digests, and SLSA identity
• record fresh downloaded-wheel installation and circuit recovery evidence
• close the a7 roadmap publication gate without claiming PyPI, stable API, or production adoption

Published evidence

• release: https://github.com/Deathcharge/samsarix-core/releases/tag/v2.0.0a7
• tagged commit: 766189a035c8a076a2b23f10b28576af586d5474
• annotated tag: 56308ee653c91a6ea35e410165a519b61297390b
• release workflow: https://github.com/Deathcharge/samsarix-core/actions/runs/31460562784
• exact-main CI: https://github.com/Deathcharge/samsarix-core/actions/runs/31460476424

Verification

• gh release verify and all three gh release verify-asset checks passed
• downloaded SHA256SUMS matched wheel and sdist
• wheel and sdist SLSA attestations verified against this repository
• fresh Python 3.11.9 wheel install passed pip check, canonical/legacy version checks, and failed → circuit-open → recovered smoke
• Black, Ruff, strict mypy, Bandit, and 177 tests (94.73% coverage) passed after the documentation update

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 21 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: b4934ac2-d391-4d63-b00d-fba805352bac

📥 Commits

Reviewing files that changed from the base of the PR and between 766189a and 9299313.

📒 Files selected for processing (6)

• CHANGELOG.md
• README.md
• ROADMAP.md
• docs/ADOPTION.md
• docs/PRODUCTIZATION.md
• docs/RELEASING.md

---

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.}