Skip to main content
Public launch verification is the final release proof wrapper for the SDK repo. It composes the existing docs, npm, Eve, registry, plugin, and distribution checks without replacing those lower-level verifiers. Before public release, run: 
pnpm verify:launch:local
pnpm verify:launch:evidence
pnpm verify:launch:evidence-file public-launch-evidence.json
pnpm verify:launch:evidence writes public-launch-evidence.json. The file uses schema budscollab.public-sdk-launch-evidence.v1 and records:
  • the launch contract version and status
  • the verifier ids, schema versions, and statuses
  • hosted inputs when running hosted verification
  • claims allowed by the evidence
  • claims still not allowed by the evidence
pnpm verify:launch:evidence-file public-launch-evidence.json audits a saved evidence file against public-launch-verification-contract.json. Use it during release review when the evidence file is attached to a release, issue, or pull request. After docs, npm, Eve artifacts, and hosted registry routes are live, run: 
pnpm verify:launch:hosted --docs-url https://docs.budscollab.com --app-url https://app.budscollab.com --npm-registry-url https://registry.npmjs.org --artifact-dir ./generated-app --out public-launch-evidence.json
Hosted launch verification must prove:
  • the Mintlify docs and agent discovery paths are reachable
  • exact SDK package versions are visible on npm
  • the Eve artifact directory contains the declared handoff artifacts
  • hosted registry routes accept validated artifacts and stay fail-closed until signing and install policy are complete
Even hosted evidence does not mean marketplace install is ready. Install still requires publisher verification, stored review evidence, artifact signing, and host install policy returning a signed installable registry row.