docs: record external Core adoption evidence

[Deathcharge]

Summary

• link Samsarix Core to its exact-pinned independent MCP consumer
• record commits, local verification, artifact hashes, limitations, support, compatibility, and rollback
• update the roadmap and productization record without claiming third-party production adoption

Local verification

• Black
• Ruff
• strict mypy
• 59 tests, 94.08% coverage on Python 3.14
• git diff --check

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 51 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: c4f1142c-739d-4f63-abb7-85a60170a391

📥 Commits

Reviewing files that changed from the base of the PR and between fcd57da and 077aa4b.

📒 Files selected for processing (3)

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

Summary by CodeRabbit

• Documentation
  • Added adoption documentation covering compatibility evidence, verification results, build artifacts, rollback procedures, and next steps.
  • Documented an external consumer integration, tested workflows, pinned compatibility reference, and adoption record.
  • Updated the roadmap with completed productization, MCP integration, resource-bound, and synchronization work.
  • Clarified MCP lifecycle, structured output, transport limits, resource budgets, and deferred provider integrations.

Walkthrough

The PR documents an external MCP consumer, its pinned Core version, compatibility checks, adoption evidence, rollback procedures, and updated productization status.

Changes

External consumer adoption evidence

Layer / File(s)	Summary
External consumer reference README.md, docs/ADOPTION.md	Documents the external consumer, pinned Core commit, privacy-first workflow, supported API surface, and adoption evidence scope.
Verification and rollback procedures docs/ADOPTION.md, ROADMAP.md	Records local verification, artifact checks, hosted CI limitations, compatibility requirements, rollback steps, and remaining adoption signals.
Productization status docs/PRODUCTIZATION.md, ROADMAP.md	Marks dependency-free MCP work and consumer verification as complete while keeping optional adapters, release, and adoption decisions pending.

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

Possibly related PRs

• Deathcharge/samsarix-core#3: Introduced the MCP bridge documented by this consumer verification work.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: documenting external Core adoption evidence.
Description check	✅ Passed	The description directly matches the documentation, verification, compatibility, and rollback changes in the pull request.
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/external-adoption-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: 4

🤖 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 13-21: Expand the adoption evidence table in ADOPTION.md to
include Integration Guard and Orchestration provenance: exact commit, repository
URL, and package version. Add consumer manifest or resolved-install metadata
demonstrating that samsarix-core==0.2.0 resolves to commit
6f54bcdf428359f1eee654944b6abc8788575eab, preserving the existing Core and
consumer evidence.

In `@docs/PRODUCTIZATION.md`:
- Around line 246-252: Update the matrix-evidence paragraph in PRODUCTIZATION.md
to include the exact Core workflow run URL and explicitly label the “59 tests,
94.08%” result as Core-only. Preserve the separate consumer evidence and
billing-failure context documented in ADOPTION.md.

In `@ROADMAP.md`:
- Around line 47-48: Update the completed roadmap item near the consumer-owned
local-process contract fixture to narrow the “limits” claim: explicitly name
which limits are tested, and state that timeout and bounded quiescence remain
unverified if they are not covered. Keep the other listed coverage areas
unchanged.
- Around line 27-31: Update the roadmap entry following the consumer matrix
rerun so it does not imply that compatibility evidence prioritizes richer nested
schema types. Reference concrete consumer demand as the basis for schema
expansion, consistent with the guidance in ADOPTION.md and PRODUCTIZATION.md,
while retaining the matrix rerun as compatibility validation.

🪄 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: 81103c7f-3a7f-481f-baab-7b53c65b621d

📥 Commits

Reviewing files that changed from the base of the PR and between 6f54bcd and fcd57da.

📒 Files selected for processing (4)

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