← ClaudeAtlas

public-artifact-runtime-smoke-gatelisted

Verify Python packages, CLIs, MCP servers, and Agent plugins through the exact installed artifact and real runtime contract. Use when source tests pass but a published release may omit modules, expose broken entry points, depend on local paths, fail without optional credentials, or behave differently after public installation.
JinNing6/Noosphere · ★ 18 · AI & Automation · score 74
Install: claude install-skill JinNing6/Noosphere
# Public Artifact Runtime Smoke Gate Prove the artifact users install, not the source tree that produced it. Treat source tests, built artifacts, public-index resolution, installed entry points, and runtime protocol behavior as separate evidence layers. ## Required Gate 1. Identify the intended immutable release commit, version, and public registry. 2. Wait for that exact version to appear in the public registry with bounded retries. 3. Create a clean environment outside the repository and disable local project discovery. 4. Install the exact public version with caches disabled where the package manager permits. 5. Read the installed distribution's version from its own metadata. 6. Launch the installed console entry point as a subprocess. Do not substitute `python -m` against the checkout. 7. Remove optional credentials from the child environment and verify the documented anonymous or degraded behavior. 8. Exercise a representative runtime contract. For MCP stdio, send `initialize`, wait for its response, send `notifications/initialized`, then request `tools/list` before closing stdin. 9. Assert stable product-owned fields, required capabilities, exit status, and bounded runtime. 10. Record the exact version, command, environment, artifact digest, observed failure, observed success, and verification result. ## One-Minute Reproduction Use Noosphere's deterministic fixture to reproduce the source-versus-artifact failure and verify the repair without a project or token: ``