docs: record consumer task evidence

[Deathcharge]

Summary

• record the merged v0.2.7 independent consumer at exact commit 51cc3fb3f1fb4bd484ebef58d2c9ab22acc24623
• document real redaction task create/get/result/cancel, related progress, private task state, and bounded retention
• record Python 3.11 installed-wheel and Python 3.14 source-tree results plus exact artifact hashes
• preserve honest distinctions between current task evidence, earlier Inspector/VS Code evidence, hosted billing failures, and production adoption

Verification

• python -m black --check .
• python -m ruff check .
• python -m mypy
• python -m pytest — 98 passed, 94.28% branch coverage
• python -m bandit -q -r src

Consumer evidence

• consumer PR: https://github.com/Deathcharge/samsarix-integration-examples/pull/10
• merge: 51cc3fb3f1fb4bd484ebef58d2c9ab22acc24623
• Python 3.11 installed wheel: 33 passed, 90.85% branch coverage
• fresh-wheel stdio journey: task create → blocking result → completed state, two progress updates, sanitized artifact, no seeded secrets/workspace path
• PR and post-merge Actions contain zero steps because GitHub reports an account billing/spending-limit gate; they are not claimed as test evidence

[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

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: 5103f3a7-94b7-42b6-aa73-f4b71d5fbcca

📥 Commits

Reviewing files that changed from the base of the PR and between a2db31c and c053aa4.

📒 Files selected for processing (1)

• docs/ADOPTION.md

Summary by CodeRabbit

• Documentation
  • Updated the changelog, README, roadmap, and adoption/productization documentation with the latest integration evidence.
  • Documented experimental MCP task lifecycle coverage, including status, polling, progress, cancellation, retention, and result handling.
  • Added updated version, commit, validation, test, coverage, artifact, and CLI verification details.
  • Clarified VS Code configuration discovery and the remaining trust/tool-approval workflow.
  • Recorded that hosted workflows were unavailable due to billing limits.

Walkthrough

The documentation records Samsarix consumer version 0.2.7, pinned commits, experimental MCP task lifecycle validation, local verification results, package artifacts, and productization status.

Changes

Consumer MCP Evidence

Layer / File(s)	Summary
Consumer contract and lifecycle evidence README.md, ROADMAP.md, docs/ADOPTION.md	Documents consumer version 0.2.7, pinned commits, MCP task operations, discovery details, compatibility checks, and adoption evidence.
Verification and artifact records docs/ADOPTION.md	Updates local test results, Python 3.14 checks, dependency verification, package metadata, artifact hashes, and workflow links.
Release and productization records CHANGELOG.md, docs/PRODUCTIZATION.md	Records independently packaged task lifecycle evidence and updates productization completion and CI evidence.

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

Possibly related PRs

• Deathcharge/samsarix-core#3: Documents consumer validation of the MCP task lifecycle.
• Deathcharge/samsarix-core#6: Introduced the related consumer adoption evidence.
• Deathcharge/samsarix-core#16: Records earlier Samsarix consumer and VS Code/MCP validation.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the documentation change for consumer task evidence.
Description check	✅ Passed	The description directly explains the documented consumer task evidence, verification results, and billing limitations.
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-task-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: 2

🤖 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 49-59: In the adoption documentation paragraph, replace the
unsupported “production redaction tool” label with “consumer redaction tool” or
equivalent wording such as “real redaction workflow,” while preserving the
surrounding task-support and client-contract description.
- Around line 89-115: Update the adoption evidence around the installed-wheel
and release validation summaries to distinguish declared consumer support for
Python 3.11–3.13 from versions actually exercised. Either add execution results
for Python 3.12 and 3.13, or explicitly state that those versions are supported
by declaration only; retain the existing Python 3.11.9 and 3.14.6 evidence.

🪄 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: 2a285f7d-f369-46b5-b215-62b8c5d75264

📥 Commits

Reviewing files that changed from the base of the PR and between 1558624 and a2db31c.

📒 Files selected for processing (5)

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