@stardeck-customer-apps/compose 0.8.0 → 0.10.0

package/SKILL.md

@@ -18,11 +18,18 @@ Compose turns that declaration into the code Next.js actually builds:
   per composed Module that ships `server/registrations.ts`
 - one `page.tsx` / `route.ts` stub under `apps/web/src/app/**` per declared
   mount and endpoint
+- `apps/web/tsconfig.build.gen.json` (apps with a Module tree only) — extends
+  `tsconfig.json` and excludes every Module `--enabled` left out, plus each
+  kept Module's `enhancements/<excluded>/`. Their source stays on disk but their
+  stubs are gone, so `next build` must type-check through this file
+  (`typescript.tsconfigPath` in `next.config.ts`), never through `tsconfig.json`.
+  Gitignore it; do not hand-maintain an exclude list.
 
 ## Running it
 
 ```bash
 npx stardeck-compose [--enabled=a,b,c] [--prune] [--cwd=<repo root>]
+npx stardeck-compose --check-boundaries [--cwd=<repo root>]
 ```
 
 Run it from the repo root (the directory holding `apps/web`). The Blueprint
@@ -75,6 +82,24 @@ a silent fallback. It holds deployment facts: gitignore it (`apps/web/.gitignore
   a git checkout, and a clean one: it refuses when `git status --ignored`
   reports uncommitted or ignored files under `apps/web/src/modules`, and
   refuses outside a checkout — it is for throwaway deploy checkouts, not yours.
+  It also refuses, before deleting anything, when a file outside
+  `apps/web/src/modules` imports an excluded Module, or when a kept Module's own
+  file (tests included) would import a deleted path: an excluded Module, any
+  Module's `enhancements/<excluded>/`, a `.sql`/`.json` of theirs read by path,
+  or another kept file that does. Only a file inside the Module's own
+  `enhancements/<excluded>/` goes with the peer (with any excluded peer: a
+  booking slice may import membership when both are pruned). Fix: move the file into
+  `src/modules/<module>/enhancements/<peer>/`, or declare the peer in `uses` and
+  enable it. A test that needs two optional peers at once cannot live in one
+  `enhancements/` folder: load the second peer's harness only when
+  `isModuleEnabled(peer)` and `it.skipIf` without it. Needs compose 0.9.0 or
+  later for the Module-file check.
+- `--check-boundaries` — Blueprint lint; composes nothing. Checks every Module
+  against every feature Module it does not list in `uses` (whether it lists it
+  in `enhancements` or not), as if all of them were switched off, and exits 1
+  listing the offending files. Library Modules are always composed and never
+  count. Run it in Blueprint CI so such an import is caught before a customer
+  prunes.
 
 ## Rules