Skip to main content

​
CLI And Pack Smoke

CLI and pack-smoke validation prove the shipped package behavior, not just the source-tree runtime behavior.

​
What this layer covers

  • CLI command routing
  • generated artifacts in a packaged install
  • tarball import/export validation
  • scenario generation in a real installed package
  • release readiness gates

​
Main commands

npm run test:pack-smoke
npm run test:coverage

​
CLI coverage map

Use the CLI test matrix for exact command ownership:

​
When pack smoke is required

  • package exports changed
  • generator output changed
  • docs/examples changed in the shipped tarball surface
  • scenario generation changed
  • release validation is being prepared