docs: record v2.0.0a6 release evidence

[Deathcharge]

Summary

• advance the README's verified install path to the now-published immutable v2.0.0a6 prerelease
• close the roadmap release gate and record exact commit, tag object, workflow, asset, checksum, and provenance evidence
• update adoption/productization wording without overstating independent production use

Verified publication evidence

• release: https://github.com/Deathcharge/samsarix-core/releases/tag/v2.0.0a6
• tagged commit: f09e77877b04500aa7d23504ba21123577138543
• annotated tag object: e38fa58fcf94fac6b0525027967194f9c6d8fb64
• exact-main CI 31450834231: passed
• build-only Release run 31451018128: passed
• tag Release run 31451329609: passed, including attestation and publication
• gh release verify: passed
• gh release verify-asset: passed for wheel, sdist, and manifest
• downloaded SHA256SUMS: matched both distributions
• strict SLSA verification: bound both distributions to this repository, .github/workflows/release.yml, refs/tags/v2.0.0a6, source f09e77877b04500aa7d23504ba21123577138543, and GitHub-hosted runners
• fresh Python 3.11.9 wheel install: no dependencies or broken requirements; both namespaces reported 2.0.0a6; public example proved success, immediate rate limiting with numeric retry delay, and recovery

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 33 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: df7373f1-5609-4a49-92b9-f5df49ad2d8f

📥 Commits

Reviewing files that changed from the base of the PR and between f09e778 and d15a8cd.

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