Record independent invocation-policy adoption evidence

[Deathcharge]

Summary

• update Core's external consumer record to samsarix-integration-examples 0.2.8 at merge c59ed468fc126eecb0a61559423ab7854ddacb87
• record exact Core pin, policy allow/deny behavior, clean-wheel Python 3.11 results, source Python 3.14 results, artifact hashes, and rollback boundary
• record the consumer's zero-step GitHub Actions billing gate without representing it as test evidence
• advance the roadmap now that the independent policy contract is proven

Verification

• Black, Ruff, and strict mypy pass
• 105 Core tests pass with 94.42% branch coverage
• git diff --check passes

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 56 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: d32068ce-5231-40e9-8230-d3e2b7231aba

📥 Commits

Reviewing files that changed from the base of the PR and between 14843f4 and fd45761.

📒 Files selected for processing (1)

• docs/ADOPTION.md

Summary by CodeRabbit

• Documentation
  • Updated adoption, productization, roadmap, README, and changelog records for version 0.2.8.
  • Documented invocation-policy validation, including approval of supported redaction actions and safe denial of unauthorized tools before execution.
  • Refreshed release, commit, pull request, test, coverage, artifact, and installed-package evidence.
  • Clarified remaining work for the signed-in Visual Studio Code trust and tool-approval journey.

Walkthrough

The change updates external-consumer evidence from Core 0.2.7 to 0.2.8. It documents fail-closed invocation-policy approval for the redaction contract and safe denial of unauthorized tools before execution.

Changes

Consumer policy evidence

Layer / File(s)	Summary
Policy contract evidence README.md, ROADMAP.md, docs/ADOPTION.md, docs/PRODUCTIZATION.md, CHANGELOG.md	Documents the validated redaction contract, fail-closed host-policy approval, and pre-execution denial of out-of-contract tools without private-argument disclosure.
Release and validation records README.md, ROADMAP.md, docs/ADOPTION.md, docs/PRODUCTIZATION.md	Updates Core and consumer pins, version 0.2.8 records, test and coverage results, package artifacts, workflow links, and deferred-work status.

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

Possibly related PRs

• Deathcharge/samsarix-core#6: Updates the same external-consumer adoption evidence.
• Deathcharge/samsarix-core#18: Updates related consumer evidence for task lifecycle and redaction behavior.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: recording independent invocation-policy adoption evidence.
Description check	✅ Passed	The description directly explains the updated consumer evidence, policy behavior, verification results, and roadmap changes.
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 unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/consumer-policy-evidence

---

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 `@docs/ADOPTION.md`:
- Around line 50-52: Update the wording in docs/ADOPTION.md from “production
adapter” to “consumer adapter” or “redaction adapter” so it does not imply a
documented third-party production deployment; leave the surrounding
ToolPolicyContext and ToolPolicyDecision description unchanged.

🪄 Autofix (Beta)

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: 523c0908-0bbf-4239-889c-84932bf5d868

📥 Commits

Reviewing files that changed from the base of the PR and between 33f2baa and 14843f4.

📒 Files selected for processing (5)

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