Distribution and onboarding readiness¶
This matrix separates repository contract evidence from physical/product evidence. A file existing in the repository is not enough to mark a surface verified. Historical Claude Code and Codex host runs are retained in the dated agent-host evidence index. They do not establish current host/skill/extension compatibility; see #1219.
| Surface | Current status | Objective evidence | Notes |
|---|---|---|---|
CLI / uvx |
Existing verified surface | tests/e2e/test_stdio_startup.py, Python release workflow |
Remains the first-class power-user and automation path. |
| PyPI | Existing release surface | .github/workflows/publish-python.yml, release-evidence tests |
PCM does not replace Python distribution. |
| npm launcher | Existing release surface | .github/workflows/publish-npm.yml, npm package CI |
Separate launcher for supported MCP clients. |
| MCPB | Existing release surface | .github/workflows/publish-mcpb.yml, tests/unit/test_release_hardening.py |
Attested/versioned release asset contract. |
| Docker / GHCR | Existing release surface | .github/workflows/publish-mcp-container.yml, container tests |
No change from PCM work. |
| Desktop | Existing release surface | GUI CI/release workflows and desktop/backend compatibility tests | Exact-release backend compatibility remains independent of PCM. |
| KiCad PCM | Physical Linux + Windows verified; macOS physical host pending | Linux physical evidence, Windows physical evidence, tests/unit/test_kicad_pcm_packaging.py, tests/unit/test_companion_context.py, .github/workflows/publish-kicad-pcm.yml |
Linux install/restart/health/MCP/update/incompatible/uninstall/rollback is physically verified on two independent Linux hosts. Windows physical PCM flow verified for install/restart/health/MCP/incompatible/uninstall/rollback. macOS physical host unavailable, so CI is not presented as physical evidence. |
| Claude Code guided config | Real client connect verified | Linux physical evidence, tests/unit/test_issue_731_onboarding.py |
Claude Code 2.1.238 used its native mcp add/mcp get flow against the live loopback backend and reported Status: Connected; user configuration was isolated. |
| Codex guided config | Real client connect verified | Linux physical evidence, tests/unit/test_issue_731_onboarding.py |
Codex CLI 0.150.1 completed initialize/initialized/tools-list and a real read-only kicad_get_version tool call after negotiated-protocol compatibility was fixed in #813. |
| Cursor guided config | Physical guided transaction verified | Linux physical evidence, tests/unit/test_issue_731_onboarding.py |
A disposable project-scoped config exercised side-effect-free preview, explicit write, unrelated-key preservation, backup, exact-targeting, and hash-exact restore. A Cursor binary connect is not claimed. |
| VS Code / Copilot config | Existing config contract | tests/unit/test_setup.py, docs/agents/vscode-copilot.md |
Physical PCM-guided onboarding is not claimed by this tranche. |
| Official PCM listing | Not submitted | KiCad PCM submission plan | Submission waits for a public release asset plus physical package evidence. |
Promotion rule¶
The PCM surface may be described as physically verified on Linux and Windows. Two independent Linux hosts and one Windows host demonstrate the versioned artifact through install/update or clean install, restart/discovery, backend health, MCP lifecycle/read-only smoke, incompatible-version fail-closed behavior, uninstall, and rollback. Full cross-platform Verified status remains blocked only because the macOS physical host unavailable boundary is explicitly documented as CI-only rather than physical evidence.
Physical evidence must identify the exact source revision and artifact SHA256 without exposing local credentials, private paths, or unrelated desktop content.
Client rows similarly distinguish unit-level transaction safety from a real installed-client flow. A successful config unit test does not prove the external client binary accepted or used that config.