easy-stack

Integration suite · I001–I029

Twenty-nine boundaries working together.

Integration cases prove consumers receive the intended builds, the package and site stay coherent, and generated Playground code runs against the actual module.

Unique case catalog

  1. I001 package root resolves ESM default and named identity
  2. I002 package root resolves the CommonJS constructor identity
  3. I003 documented stack deep path maps to each root build
  4. I004 ES5 require condition maps to the shared module build
  5. I005 classic browser build exposes the Stack global
  6. I006 ES5 browser build exposes the Stack global
  7. I007 manifest declares the shared runtime and Node floor
  8. I008 lockfile mirrors the manifest Node floor
  9. I009 exports and side effects expose only supported builds
  10. I010 vanilla-test is pinned dev-only with zero runtime dependencies
  11. I011 publish whitelist and Pages homepage are exact
  12. I012 twelve primary pages and five suite catalogs exist
  13. I013 every page exposes its focused section contract
  14. I014 every local link, asset, and fragment resolves
  15. I015 every page navigation links all twelve primary routes
  16. I016 every page navigation marks exactly one current route
  17. I017 README starts with the header and routes to focused docs
  18. I018 hero CSS and repository header preserve panoramic geometry
  19. I019 social card PNG has the documented dimensions
  20. I020 test scripts and suite pages match the unique catalog
  21. I021 CI exposes suite, exact-floor, coverage, browser, package, benchmark, and publish gates
  22. I022 Pages is CI-gated and assembles every curated route and runner asset
  23. I023 repository remains JavaScript-only
  24. I024 resolver maps valid root and nested site paths
  25. I025 local server serves documentation and runner HTML
  26. I026 local server serves runner assets with MIME and CORS
  27. I027 local server serves the generated header PNG
  28. I028 prepared source executes to the same visible snapshot
  29. I029 benchmark evidence compares the tagged release with validated private-field runs

Run this suite

npm run test:integration

Package, documentation, workflow, server, and replay boundaries each have a distinct contract key. Consumer outcomes stay in Behavioral rather than being repeated here.

Next suiteRegression