@stardeck-customer-apps/compose 0.7.0 → 0.9.0

package/SKILL.md

@@ -14,6 +14,8 @@ Compose turns that declaration into the code Next.js actually builds:
 - `apps/web/src/module-i18n.gen.ts`
 - `apps/web/src/module-init.server.gen.ts`
 - `apps/web/src/module-datastores.gen.ts`
+- `apps/web/src/module-server.gen.ts` — `MODULE_SERVER_REGISTRATIONS`, one entry
+  per composed Module that ships `server/registrations.ts`
 - one `page.tsx` / `route.ts` stub under `apps/web/src/app/**` per declared
   mount and endpoint
 
@@ -21,6 +23,7 @@ Compose turns that declaration into the code Next.js actually builds:
 
 ```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
@@ -73,6 +76,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
 
@@ -101,6 +122,19 @@ a silent fallback. It holds deployment facts: gitignore it (`apps/web/.gitignore
   compose as a route collision.
   `isMountHeadless(key)` and `isHrefHeadless(href)` are exported from
   `@/modules.gen`. Needs compose 0.7.0 or later.
+- **Server registrations.** Per-Module server wiring that the app layer runs
+  (seeds, schedule handlers, and similar) goes in the Module's
+  `server/registrations.ts`, any Module kind. Compose imports each composed
+  Module's file as a namespace into `module-server.gen.ts`:
+  `MODULE_SERVER_REGISTRATIONS` is a
+  `readonly { module: string; registrations: Readonly<Record<string, unknown>> }[]`.
+  A Module left out by `--enabled` is not imported at all, so its server code
+  drops out of the build. App code reads that array from `@/module-server.gen`
+  and narrows the exports it expects (e.g. `registrations.seed`); it must never
+  import a Module's seed or schedules directly, or a disabled Module stays in
+  the bundle. Compose does not check the export names or shapes. The file
+  counts as `server/**/*.ts`, so the Module also needs `server/index.ts`.
+  Needs compose 0.8.0 or later.
 - `@stardeck-customer-apps/compose/runtime` exports `isModuleEnabledByList`,
   the single enablement rule, and imports nothing — it is safe in client
   components.
@@ -111,5 +145,5 @@ After each run compose rewrites `apps/web/src/app/.gitignore` with one entry per
 stub it emits — stubs are scattered one-per-route and cannot be globbed. Commit
 that file: it is deterministic output, and compose rewrites it only when the set
 of stubs changes, so an unchanged compose leaves `git status` clean. It does not
-list the five `src/*.gen.ts`; a static `src/*.gen.ts` line in `apps/web/.gitignore`
+list the six `src/*.gen.ts`; a static `src/*.gen.ts` line in `apps/web/.gitignore`
 covers those. Compose refuses to touch the file if line 1 is not its own header.