Productize and rebrand as Samsarix Platform Doctor

[Deathcharge]

What changed

• replaces the documentation-only prototype with the working Samsarix Platform Doctor 0.1.0 CLI
• provides strict TOML readiness checks, deterministic human/JSON output, and safe manifest initialization
• adds 37 tests, 93% branch coverage, strict typing/linting, cross-platform CI, package builds, and wheel smoke tests
• migrates every current public identifier from Helix to Samsarix
• adds the official MPL 2.0 license, Samsarix LLC attribution, brand notices, CODEOWNERS, and private support/security contacts
• rewrites architecture, quick-start, contribution, release, security, and productization documentation to match verified behavior

Why

The original repository documented a broad production platform but contained no source, tests, package metadata, or runnable workflow. This PR establishes a deliberately narrow, real product and applies the company's current Samsarix identity before the first public release.

MPL 2.0 provides file-level copyleft and contributor patent protection while allowing the covered files to be used in larger proprietary works.

User and developer impact

The installable distribution is samsarix-platform, the command is samsarix-platform, the import package is samsarix_platform, and the default manifest is samsarix-stack.toml. No compatibility alias is included because neither identity has been publicly released.

Verification

• Ruff format and lint: passed
• strict mypy: passed across 11 source files
• unittest/coverage: 37 passed, 93% branch coverage
• strict root doctor: 5 passed, 0 warnings/failures
• isolated sdist/wheel build and Twine validation: passed
• clean installed-wheel CLI/module/metadata/license smoke test: passed
• pip-audit: no known vulnerabilities
• local Markdown links: 0 broken
• official MPL 2.0 text comparison: exact after newline normalization

Remote CI status

GitHub received both push and pull-request workflow events, but no runner or workflow step started. Every job has the same platform annotation: The job was not started because recent account payments have failed or your spending limit needs to be increased. Resolve that under GitHub Billing & plans, then rerun the failed jobs; no repository code change is indicated by the logs.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 59 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: Free

Run ID: 5edeb1bc-110e-48cc-b7e7-e7e9ccc923b0

📥 Commits

Reviewing files that changed from the base of the PR and between bc98b78 and f8ececa.

📒 Files selected for processing (37)

• .github/CODEOWNERS
• .github/dependabot.yml
• .github/workflows/ci.yml
• .gitignore
• CHANGELOG.md
• CODE_OF_CONDUCT.md
• CONTRIBUTING.md
• LICENSE
• NOTICE.md
• QUICK_START.md
• README.backup.md
• README.md
• ROADMAP.md
• SECURITY.md
• docs/ARCHITECTURE.md
• docs/DEPLOYMENT.md
• docs/PRODUCTIZATION.md
• docs/RELEASING.md
• examples/README.md
• examples/agent-project/README.md
• examples/agent-project/samsarix-stack.toml
• pyproject.toml
• requirements-dev.txt
• requirements.txt
• samsarix-stack.toml
• src/samsarix_platform/__init__.py
• src/samsarix_platform/__main__.py
• src/samsarix_platform/cli.py
• src/samsarix_platform/doctor.py
• src/samsarix_platform/manifest.py
• src/samsarix_platform/py.typed
• tests/__init__.py
• tests/test_cli.py
• tests/test_doctor.py
• tests/test_example.py
• tests/test_manifest.py
• tests/test_package.py

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

_{Comment @coderabbitai help to get the list of available commands.}