The CLI package is published on npm with provenance attestation to verify build origin, including only dist, templates, and metadata—source files are excluded. The published CLI exports a ./contract entry point that provides types and runtime interfaces for consuming the package API.
The CLI package is published publicly on npm with provenance attestation (provenance: true).[1] Published to npm, the package includes only dist, templates, manifest.json, and README.md — source files are excluded.[1] The CLI package exports a ./contract entry point with types at dist/src/contract.d.ts and runtime at dist/src/contract.js.[1] The CI workflow (.github/workflows/cicd.yml) does not gate PR merges on CLI version changes; version management is deferred to the release workflow. The release workflow (.github/workflows/release.yml) enforces semver validation as a preflight check at publish time.
Sources