chore: prepare 2.0.0a6 release

[Deathcharge]

Summary

• bump Samsarix Core to 2.0.0a6 for the merged per-tool token-bucket contract
• close the changelog entry and update release/install/API/roadmap metadata
• record the independent samsarix-integration-examples 0.2.11 adoption at consumer merge a446c4a80295928e6161627a8c03cc2bca4a8f27, pinned to Core 6492495a426b1ae9856bf27f331d7cfec67006e6

Local release gate

• Black: 22 files unchanged
• Ruff: passed
• strict mypy: 18 source files passed
• Bandit: passed
• pytest: 151 passed, 94.56% branch coverage on Python 3.11.9
• isolated build: wheel and sdist passed strict Twine checks
• candidate wheel: 48,580 bytes, SHA-256 03a3bb0cef9933d7b06f99daabb720be90d199dbc3b4a0875eb9a82f46054901
• candidate sdist: 126,488 bytes, SHA-256 5cbdb751e9217e74903873a2b4535cf670e20cb922bb1211c14f402ba1dbfbc9
• clean wheel environment: pip check passed; both public namespaces reported 2.0.0a6; import resolved from site-packages; the public example proved success, immediate rate_limited rejection with numeric retry hint, and recovery after the hint

Independent consumer evidence

The fresh exact-pin consumer environment passed Ruff, strict mypy, Bandit, and 37 tests at 91.64% branch coverage. Its isolated 0.2.11 wheel/sdist passed strict Twine checks, and a second clean wheel environment executed the real rate-limit contract. GitHub runs 31447006222 and 31448580817 were stopped before checkout by the account billing/spending-limit gate, so they are documented as infrastructure failures rather than hosted test evidence.

Publication boundary

Merge only after the complete Core matrix and package job pass. The immutable v2.0.0a6 tag will then be created from the exact default-branch merge commit and independently verified after the release workflow publishes checksummed, attested assets.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 54 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: 96d610ee-cb4b-442b-9927-5e8aaa7d49d2

📥 Commits

Reviewing files that changed from the base of the PR and between aadb39b and 8b7af36.

📒 Files selected for processing (1)

• README.md

Summary by CodeRabbit

• Release

  • Updated the project to prerelease version 2.0.0a6, dated August 10, 2026.

• Documentation

  • Updated installation instructions and API references for version 2.0.0a6.
  • Added verified integration evidence for per-tool rate limiting, including retryable responses, artifact preservation, and accurate metrics.
  • Updated compatibility, adoption, and productization records with the latest verification results.

Walkthrough

The project version changed to 2.0.0a6. Release documentation and installation commands were updated. Consumer evidence now records process-local per-tool rate limiting, including retryable results, suppressed artifacts, and metric updates.

Changes

Release and adoption updates

Layer / File(s)	Summary
Release identity and publication records CHANGELOG.md, CITATION.cff, README.md, docs/API_REFERENCE.md, ROADMAP.md, pyproject.toml, src/samsarix_core/_version.py	Release metadata, package declarations, installation commands, API documentation, and the release-candidate milestone now reference 2.0.0a6.
Consumer rate-limit evidence CHANGELOG.md, README.md, ROADMAP.md, docs/ADOPTION.md, docs/PRODUCTIZATION.md	Consumer records document exact-tool token-bucket behavior, including successful first calls and safe rate_limited results for immediate second calls.
Installation and verification records docs/ADOPTION.md, docs/PRODUCTIZATION.md	Verification records now identify consumer version 0.2.11, Python 3.11.9, 37 passing tests, updated coverage, artifact hashes, and workflow references.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• Deathcharge/samsarix-core#6: Both PRs update external consumer adoption evidence across the project documentation.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the primary release-preparation changes for version 2.0.0a6.
Description check	✅ Passed	The description directly covers the release metadata updates, adoption evidence, validation results, and publication conditions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/release-2.0.0a6

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Around line 44-52: Update the README release-installation block to reference
the latest published v2.0.0a5 release, including its link, download filename,
attestation target, and pip install command. Do not publish or reference
v2.0.0a6 until its release assets and attestation are verified.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 3eb921e0-3756-4b18-80b9-ebe62f8afa49

📥 Commits

Reviewing files that changed from the base of the PR and between 6492495 and aadb39b.

📒 Files selected for processing (9)

• CHANGELOG.md
• CITATION.cff
• README.md
• ROADMAP.md
• docs/ADOPTION.md
• docs/API_REFERENCE.md
• docs/PRODUCTIZATION.md
• pyproject.toml
• src/samsarix_core/_version.py