create-ailk 0.4.0 → 0.6.0

package/dist/module-architecture.js

@@ -21,8 +21,8 @@
  * `architecture.yaml` template files — a fixed template IS the drift this
  * removes.
  */
-import { readFileSync, readdirSync } from "node:fs";
-import { dirname, join, sep } from "node:path";
+import { sep } from "node:path";
+import { importClosure } from "./lib/import-graph.js";
 import { PAID_MODULES } from "./lib/module-tier.js";
 import { RECOGNIZED_MODULES } from "./parse-args.js";
 /**
@@ -124,6 +124,31 @@ export const ARCHITECTURE_BASE = {
         },
     ],
 };
+/**
+ * The workspace asset store (#5854), CO-OWNED by the `workspace` and
+ * `multi-tenant` slices.
+ *
+ * `server.ts` registers both of its routes under
+ * `isModuleEnabled("workspace") || isModuleEnabled("multi-tenant")`, and a file
+ * behind a two-module disjunction must be deliverable by BOTH bundles — or
+ * whichever module lacks it throws ERR_MODULE_NOT_FOUND during `build()`. One
+ * array spread into both `ownedFiles` lists makes the two copies incapable of
+ * drifting, which matters because a drift only surfaces in a scaffolded
+ * customer repo rather than here.
+ *
+ * `routes/assets/index.ts` is listed although it registers nothing: the
+ * template-exclusion closure runs over IMPORTERS, so a shared-constants module
+ * that is imported BY the routes and imports neither of them is never reached
+ * from them, and an unlisted one would ship into the keyless Free starter.
+ */
+const ASSET_STORE_FILES = [
+    "apps/api/src/routes/assets/index.ts",
+    "apps/api/src/routes/assets/upload.ts",
+    "apps/api/src/routes/assets/read.ts",
+    // The manage routes — list, PATCH, DELETE (#6093 D16).
+    "apps/api/src/routes/assets/manage.ts",
+    "apps/api/src/lib/asset-store.ts",
+];
 /**
  * The per-module slices. Authored for every `RECOGNIZED_MODULES` value; only
  * `marketing` (the default) is validated end-to-end against a golden.
@@ -246,6 +271,11 @@ export const MODULE_SLICES = {
             // The Fumadocs source pair — both whole, both loaders (D3).
             "apps/web/source.config.ts",
             "apps/web/lib/source.ts",
+            // The runtime source `lib/source.ts` resolves to under
+            // CONTENT_ADAPTER=database (#5878). Listed explicitly: the exclusion
+            // closure grows over DEPENDENTS, not dependencies, so being imported by
+            // `lib/source.ts` does not pull this file into the bundle by itself.
+            "apps/web/lib/runtime-source.ts",
             // The route adapters and the jest stub for the codegen output.
             "apps/web/lib/blog-list-data.ts",
             "apps/web/lib/blog-post-data.ts",
@@ -253,39 +283,46 @@ export const MODULE_SLICES = {
             // The module's own /llms.txt variant; the bundle installs it onto
             // app/llms.txt/route.ts (#5365 D9, install-path mapping owned by #5373).
             "apps/web/lib/slices/docs-blog/llms-route.ts",
-            // The two shells and the six components, each off its public barrel and
-            // reachable only from the slice barrel that leaves with them (D-45, D5).
-            "packages/templates/src/shells/BlogShell.tsx",
-            "packages/templates/src/shells/DocsShell.tsx",
-            "packages/templates/src/shells/slices/docs-blog.ts",
-            "packages/ui/src/blocks/DocsActionBar.tsx",
-            "packages/ui/src/blocks/DocsArticleHeader.tsx",
-            "packages/ui/src/blocks/DocsFeedback.tsx",
-            "packages/ui/src/blocks/DocsSearch.tsx",
-            "packages/ui/src/blocks/DocsTocButton.tsx",
-            "packages/ui/src/chrome/DocsSidebar.tsx",
-            "packages/ui/src/chrome/slices/docs-blog.ts",
+            // The two shells and the six components moved to packages-paid/ui-docs-blog
+            // (#5581) — that package is a physical part of the tree, not a listed
+            // ownedFiles entry, and is installed via this slice's `patches` block below.
         ],
         // pageContributions (spec 5478; parent § D6 shape 1) — the two route
         // surfaces this module mounts, each with the seed MDX it renders. The
-        // three MDX files are exactly the three on the tree and cannot come from
+        // nine MDX files are exactly the nine on the tree and cannot come from
         // the `templates/` snapshot: `apps/web/content` is in build-templates.mjs's
         // EXCLUDE_TEMPLATE_DIRS and `template-overlay/` carries no blog or docs
         // stub. They ride this module's own bundle, consistent with the route
-        // files above — STAGING them into it is #5481's change to
-        // build-module-bundles.mjs, since `collectModuleFiles` unions `ownedFiles`
-        // with `installMap` keys and nothing else. This unit only DECLARES them.
+        // files above: `collectModuleFiles` in build-module-bundles.mjs stages
+        // every `pageContributions[].content` entry alongside `ownedFiles` and
+        // the `installMap` keys, and `copyTree` lands each at this same path.
+        //
+        // #5618 D6.2 — the module OWNS its sample content (Rule B): the blog
+        // listing, four sample posts and the three docs pages moved here out of
+        // `site-templates/marketing-site/`, so any template requiring docs-blog
+        // gets the samples and a keyed `--modules docs-blog` scaffold with no
+        // template lands them too. `launching-ailk.mdx` stays the module's fifth
+        // seed post; the Pro template maps its own post 05 ONTO that path as a
+        // copy override (D6.2a — spec § 7 finding 9 carries the seed's fate).
         pageContributions: [
             {
                 route: "/blog",
                 content: [
                     "apps/web/content/en/blog/index.mdx",
+                    "apps/web/content/en/blog/01-8-things-that-prove-coding-skills-are-directly-linked-to-successfully-assembling-ikea-furniture.mdx",
+                    "apps/web/content/en/blog/02-5-ways-to-guarantee-your-startup-goes-nowhere-fast.mdx",
+                    "apps/web/content/en/blog/03-10-ideas-that-will-guarantee-1000x-growth.mdx",
+                    "apps/web/content/en/blog/04-7-keys-to-saas-success-the-elite-doesnt-want-you-to-know.mdx",
                     "apps/web/content/en/blog/launching-ailk.mdx",
                 ],
             },
             {
                 route: "/docs",
-                content: ["apps/web/content/en/docs/getting-started.mdx"],
+                content: [
+                    "apps/web/content/en/docs/getting-started.mdx",
+                    "apps/web/content/en/docs/configure.mdx",
+                    "apps/web/content/en/docs/deploy.mdx",
+                ],
             },
         ],
         // patches (spec 5418 § 3 D1, Group G) — every Group G row that edits a
@@ -330,6 +367,8 @@ export const MODULE_SLICES = {
                             "fumadocs-core": "^16.10.4",
                             "fumadocs-mdx": "^15.0.12",
                             "@working-theory/fumadocs-schema": "workspace:*",
+                            // #5581 — the docs-blog module's paid component package (D5).
+                            "@working-theory/ui-docs-blog": "workspace:*",
                         },
                     },
                     {
@@ -396,13 +435,13 @@ export const MODULE_SLICES = {
     //
     // The FEAT-042 Organization → Workspace → Membership tenancy layer:
     // schema (auth/content namespaces) + workspace-scoped API (apps/api) +
-    // the authed workspace app surface (apps/workspace). Single-tenant sites
+    // the authed Admin app surface (apps/admin). Single-tenant sites
     // (module absent) ship none of this — same base apps/web, fixed scope.
     "multi-tenant": {
         apps: {
-            workspace: {
-                path: "apps/workspace",
-                description: "Next.js — authed workspace app (Organization → Workspace → Membership). Hosts the organization-plugin Better Auth handlers; imports the database only via lib/prisma-for-auth.ts (auth-adapter exception); all domain data via apps/api's workspace-scoped routes over HTTP.",
+            admin: {
+                path: "apps/admin",
+                description: "Next.js — authed Admin app (Organization → Workspace → Membership). Hosts the organization-plugin Better Auth handlers; imports the database only via lib/prisma-for-auth.ts (auth-adapter exception); all domain data via apps/api's workspace-scoped routes over HTTP.",
                 may_import_from: [
                     "database",
                     "packages/templates",
@@ -411,10 +450,10 @@ export const MODULE_SLICES = {
                     "packages/validation",
                     // The `workspace` module's shared settings components (#5371 req. 6)
                     // — the scaffolded-site twin of the root architecture.yaml grant on
-                    // `apps_paid.workspace`. Pro Plus inherits Pro's module set, so a
+                    // `apps_paid.admin`. Pro Plus inherits Pro's module set, so a
                     // saas-product scaffold carries both modules and this app composes
                     // the identical panels apps/web does, with no forked copy.
-                    "packages/workspace-ui",
+                    "packages/admin-ui",
                 ],
                 may_not_import_from: [
                     "apps/api",
@@ -486,12 +525,12 @@ export const MODULE_SLICES = {
                 description: "Stripe SDK wrapper + webhook signature verification",
                 may_import_from: ["packages/validation"],
             },
-            // apps/workspace presentation deps. templates is net-new here; theme/ui/
+            // apps/admin presentation deps. templates is net-new here; theme/ui/
             // validation duplicate the marketing slice's definitions VERBATIM so the
             // Object.assign merge in deriveArchitecture is order-independent (a
             // multi-tenant-only selection stays self-consistent).
             templates: {
-                description: "Shell/Chrome composition — AppShell (tier-5 shell); WorkspaceShell + ArtifactEditorShell ship inside this module itself, not the public package (D-45)",
+                description: "Shell/Chrome composition — AppShell (tier-5 shell); AdminShell + ArtifactEditorShell ship inside this module itself, not the public package (D-45)",
                 may_import_from: ["packages/theme", "packages/ui", "packages/validation"],
             },
             theme: {
@@ -553,11 +592,12 @@ export const MODULE_SLICES = {
         // ownedFiles (S1, #5088). Verified against the current filesystem and
         // server.ts's module-conditional registration (isModuleEnabled('multi-tenant')).
         //
-        // apps-paid/workspace/** is a single glob — the whole app (43 files as of
+        // apps-paid/admin/** is a single glob — the whole app (43 files as of
         // this pass, excluding __tests__/node_modules), just moved here from
-        // apps/workspace by a parallel workstream on this same branch. Unlike
-        // every other entry below, this one is intentionally a glob, not an
-        // enumeration.
+        // apps/workspace by a parallel workstream on this same branch. Later
+        // renamed in place from its former Workspace-prefixed directory name by
+        // #5637, the Admin-vocabulary rename. Unlike every other entry below,
+        // this one is intentionally a glob, not an enumeration.
         //
         // apps/api/src/routes/project-listings/ is MIXED (free anonymous surface
         // + tenant dashboard sharing one directory) — only the tenant-guarded
@@ -646,6 +686,11 @@ export const MODULE_SLICES = {
             "apps/api/src/routes/workspaces/index.ts",
             "apps/api/src/routes/workspaces/sessions.ts",
             "apps/api/src/routes/workspaces/config.ts",
+            // Co-owned with `workspace` (#5853): the content-write scope is gated on
+            // content-write AND (workspace || multi-tenant) and this file imports
+            // lib/tenant-db.ts, so each tenancy slice must deliver it.
+            "apps/api/src/routes/workspaces/content.ts",
+            ...ASSET_STORE_FILES,
             "apps/api/src/routes/billing/index.ts",
             "apps/api/src/routes/billing/portal.ts",
             "apps/api/src/routes/billing/read.ts",
@@ -662,8 +707,42 @@ export const MODULE_SLICES = {
             "apps/api/src/middleware/tenant.ts",
             "apps/api/src/services/tenant-context.ts",
             "apps/api/src/services/waitlist-dashboard.ts",
+            // #6258 — the file waitlist-dashboard.ts imports for the pinned
+            // platform-operator read scope. It rides BOTH slices for the same
+            // reason its importer does: an unlisted import target breaks a
+            // signal-collectors-without-multi-tenant scaffold at build() time.
+            "apps/api/src/services/waitlist-operator-reads.ts",
+            // #6204/#6280 CI fix — `listUnhandledMessages`/`markMessageHandled`
+            // (the "Needs-you" message read/write over `tenantDb(tenant).leads`)
+            // moved here off `services/leads-inbox.ts`, a BASE-tier file every
+            // scaffold ships. Importing `lib/tenant-db.ts` from that base file
+            // walked `paidModuleTemplateExclusions()`'s companion closure
+            // (`lib/import-graph.ts`) BACKWARD into `leads-inbox.ts` itself and
+            // then into every one of `apps/api/src/{server,cli,index,
+            // vercel-handler}.ts` — all of which reach it through
+            // `routes/leads/list.ts` — dropping them from a keyless scaffold
+            // (`__tests__/paid-module-exclusions.test.ts`'s `MUST_SHIP` guard,
+            // #5678's cascade shape recurring a third time).
+            //
+            // #6216 — now reached: `routes/workspaces/messages.ts` (below)
+            // consumes `getMessage` alongside the two functions above. That route
+            // registers under `isModuleEnabled("workspace") ||
+            // isModuleEnabled("multi-tenant")` — the SAME gate
+            // `workspaces/general.ts`/`members.ts` register under, NOT the
+            // multi-tenant-only family `workspaces/meetings.ts`/`config.ts` sit
+            // in — so this file and `routes/workspaces/messages.ts` are now
+            // CO-OWNED with `workspace` too (see that slice's entry below), the
+            // asset-store precedent: a file behind an OR gate must be
+            // deliverable by BOTH bundles.
+            "apps/api/src/services/inbox-messages.ts",
+            "apps/api/src/routes/workspaces/messages.ts",
             "apps/api/src/lib/tenant-db.ts",
             "apps/api/src/lib/ws-token.ts",
+            // #6157 D16 — the magnet Admin authoring surface, co-owned with
+            // `signal-collectors` below for the SAME reason #5677 co-owns the
+            // review surface under both: its scope is registered under the
+            // widened `multi-tenant || signal-collectors` gate.
+            "apps/api/src/routes/magnets/index.ts",
             "apps/web/app/[locale]/(authed)/waitlist/page.tsx",
             "apps/web/app/[locale]/(authed)/waitlist/[experimentId]/page.tsx",
             "apps/web/app/[locale]/(authed)/waitlist/[experimentId]/signups/[leadId]/page.tsx",
@@ -674,15 +753,36 @@ export const MODULE_SLICES = {
             "apps/web/app/[locale]/(authed)/waitlist/components/SignupsTable.tsx",
             "apps/web/app/[locale]/(authed)/waitlist/components/WaitlistComparisonTabs.tsx",
             "apps/web/app/[locale]/(authed)/waitlist/components/status-badges.tsx",
-            "apps-paid/workspace/**",
+            "apps-paid/admin/**",
         ],
+        // The whole-app glob above lands its files at their REPO-relative path
+        // unless something re-roots them (`installBundleTree`'s `copyTree`
+        // excludes only `installMap` KEYS from its verbatim copy), so without a
+        // rename rule a keyed install left a stray source-tree-relative
+        // directory in the scaffold instead of the working `apps/admin` app
+        // this slice's own `apps.admin.path` (and `paid-paths.ts`'s
+        // `introducedAppPaths()`) already declares (#5626 D3/D4). The fix lives
+        // here, on the module, so `--modules multi-tenant` alone is fixed too —
+        // never as a per-template workaround.
+        //
+        // `installRoot`, not a literal `installMap` (#5644 D1): a committed
+        // 58-entry literal map — one line per staged file's proprietary source
+        // path — put every one of those paths into this OSS-shipped file's
+        // SOURCE TEXT, the exact leak class `scripts/check-oss-strip.sh` exists
+        // to catch. `build-module-bundles.mjs`'s `deriveGlobInstallMap` derives
+        // the equivalent per-file `installMap` at bundle-build time instead —
+        // one entry per file `expandEntry` yields for the glob entry above,
+        // byte-identical to the literal map it replaces — and the mock registry
+        // fixture calls the same derivation so it cannot drift from the
+        // producer's. See `installRoot`'s own doc on `ModuleSlice` above.
+        installRoot: "apps/admin/",
     },
     // ── workspace — Pro module: the single-workspace settings shell (D-27/D-49)
     //
-    // `/workspace` in apps/web's `(authed)` segment — General (rename), Site
+    // `/admin` in apps/web's `(authed)` segment — General (rename), Site
     // (identity / SEO / theme, over the already-shipped apps/api config routes)
     // and Team (a read-only roster). The three panels live in the shared
-    // `packages/workspace-ui` package so the multi-tenant workspace app (the
+    // `packages/admin-ui` package so the multi-tenant Admin app (the
     // Pro Plus app) composes the identical components rather than a fork.
     //
     // No `apps` / `namespaces` / `forbiddenPatterns` block: this module
@@ -692,14 +792,14 @@ export const MODULE_SLICES = {
         // A PERMISSION, not a physical slice (#5371 D1a) — the identical shape
         // docs-blog uses for `packages/fumadocs-schema`. `packages/` is never in
         // SNAPSHOT_DIRS, so the package reaches a buyer as an npm/bundle
-        // dependency under `node_modules/`, never as a `packages/workspace-ui`
+        // dependency under `node_modules/`, never as a `packages/admin-ui`
         // source sibling; the `patches` entry below is what puts it in the
         // buyer's apps/web/package.json.
-        webImports: ["packages/workspace-ui"],
+        webImports: ["packages/admin-ui"],
         packages: {
-            "workspace-ui": {
-                description: "Shared workspace-settings components — the settings shell plus the General / Site / Team panels, presentational only (data + save callbacks as props)",
-                // packages/templates is required because WorkspaceSettingsShell
+            "admin-ui": {
+                description: "Shared Admin-settings components — the settings shell plus the General / Site / Team panels, presentational only (data + save callbacks as props)",
+                // packages/templates is required because AdminSettingsShell
                 // composes AppShell from @working-theory/templates/shells — the same
                 // composition apps/web's own account page uses.
                 may_import_from: [
@@ -713,7 +813,7 @@ export const MODULE_SLICES = {
         // SOURCE files only, and only the ones this module physically owns: the
         // three apps/web route files and the two apps/api route files.
         //
-        // `packages/workspace-ui/**` is deliberately NOT listed (D1a). It is a
+        // `packages/admin-ui/**` is deliberately NOT listed (D1a). It is a
         // whole package that is paid end to end, whose strip disposition is
         // carried by architecture.yaml's `commercial_tier_moves_to` field (its
         // future paid-tree home) rather than by a per-file inventory —
@@ -733,11 +833,21 @@ export const MODULE_SLICES = {
         // Test companions (`__tests__/`) are never listed — the SOURCE-files-only
         // rule above.
         ownedFiles: [
-            "apps/web/app/[locale]/(authed)/workspace/page.tsx",
-            "apps/web/app/[locale]/(authed)/workspace/site/page.tsx",
-            "apps/web/app/[locale]/(authed)/workspace/team/page.tsx",
+            "apps/web/app/[locale]/(authed)/admin/page.tsx",
+            "apps/web/app/[locale]/(authed)/admin/site/page.tsx",
+            "apps/web/app/[locale]/(authed)/admin/team/page.tsx",
             "apps/api/src/routes/workspaces/general.ts",
             "apps/api/src/routes/workspaces/members.ts",
+            // Co-owned with `multi-tenant` (#6216) — see that slice's entry: the
+            // route registers under the SAME workspace||multi-tenant gate as the
+            // two lines above, and its service function imports `lib/tenant-db.ts`
+            // (a multi-tenant-owned file), so both must be deliverable by either
+            // bundle alone.
+            "apps/api/src/routes/workspaces/messages.ts",
+            "apps/api/src/services/inbox-messages.ts",
+            // Co-owned with `multi-tenant` (#5853) — see that slice's entry.
+            "apps/api/src/routes/workspaces/content.ts",
+            ...ASSET_STORE_FILES,
         ],
         // patches — the dependency add that delivers the shared package to the
         // buyer's apps/web, mirroring docs-blog's own fumadocs-schema merge-keys
@@ -754,7 +864,7 @@ export const MODULE_SLICES = {
                         op: "merge-keys",
                         path: ["dependencies"],
                         entries: {
-                            "@working-theory/workspace-ui": "workspace:*",
+                            "@working-theory/admin-ui": "workspace:*",
                         },
                     },
                 ],
@@ -770,8 +880,10 @@ export const MODULE_SLICES = {
     //                 the ONLY holder of the scheduling credential.
     //   api           apps/api's own /v1/schedule/availability + /v1/schedule/book.
     //   presentation  the `booker` section (packages/ui, no iframe) rendered by
-    //                 the `schedule` route surface, plus the module-owned
-    //                 confirmation page at /schedule/confirmed.
+    //                 the `meet` route surface, plus the per-booking-type page
+    //                 and the module-owned confirmation page at /meet/:slug and
+    //                 /meet/confirmed (renamed from the schedule/ directory by
+    //                 #5563).
     //
     // The four forbidden patterns below are the module's whole security
     // argument, restated as boundary rules rather than left in a comment: the
@@ -864,16 +976,19 @@ export const MODULE_SLICES = {
         // consumer — unlike packages/validation below, a strip tool CAN delete
         // exactly these files without touching anything another module needs.
         //
-        // BOTH apps/web/app/[locale]/schedule pages are listed (#5182 Q9, disposed
-        // 2026-09-11). confirmed/page.tsx says outright in its own doc comment that
-        // "The module OWNS this page... a scaffold without the module has no such
-        // route", and its sibling page.tsx is the SOLE production constructor of a
-        // `booker` section: it builds the section literally in TypeScript
-        // (page.tsx:60, `type: "booker"`) rather than reading it from content, and
-        // its own header calls the route API-backed with "no content file that
-        // could disagree with the calendar". The create-ailk scaffolder already
-        // gates the whole `schedule` route surface (src/surfaces.ts), so the two
-        // pages arrive and depart together.
+        // ALL THREE apps/web/app/[locale]/meet pages are listed (#5182 Q9, disposed
+        // 2026-09-11; directory renamed from schedule/ to meet/ by #5563).
+        // confirmed/page.tsx says outright in its own doc comment that "The module
+        // OWNS this page... a scaffold without the module has no such route", and
+        // its sibling page.tsx is the SOLE production constructor of a `booker`
+        // section: it builds the section literally in TypeScript (page.tsx:60,
+        // `type: "booker"`) rather than reading it from content, and its own
+        // header calls the route API-backed with "no content file that could
+        // disagree with the calendar". [slug]/page.tsx is the third — the
+        // per-booking-type page #5563 added, composing its calLink from the same
+        // configured owner rather than reading one of its own. The create-ailk
+        // scaffolder already gates the whole `meet` route surface (src/surfaces.ts),
+        // so all three pages arrive and depart together.
         //
         // packages/sections-registry/src/registry.ts (the `booker:` entry) and
         // packages/validation/src/schemas/page-sections.ts (BookerSectionDataSchema,
@@ -902,39 +1017,111 @@ export const MODULE_SLICES = {
         // scheduling-specific. This is a judgment call, not covered by this
         // card's explicit checklist: flagged for reviewer confirmation.
         //
-        // `packages/ui/src/sections/slices/scheduling.ts` (#5214) is the slice's own
-        // registration entry point: it statically imports Booker and registers it as
-        // the `booker` renderer, so it is the one file inside packages/ui that may
-        // reach a scheduling component — because it strips alongside them. The three
-        // files that path added on the OSS side — `SectionRenderer.tsx`,
-        // `slice-renderers.ts` and `ModuleAbsent.tsx` — are deliberately NOT listed
-        // here: they ship, and listing one would take the whole dispatch table with it.
+        // The Booker components and the slice's registration entry point (#5214)
+        // moved to packages-paid/ui-scheduling (#5581 U3); that package is a
+        // physical part of the tree, not a listed ownedFiles entry, and reaches a
+        // keyed scaffold through this slice's `patches` block below (D5). The
+        // three files the old in-packages/ui path added on the OSS side —
+        // `SectionRenderer.tsx`, `slice-renderers.ts` and `ModuleAbsent.tsx` — are
+        // deliberately NOT listed here: they ship, and listing one would take the
+        // whole dispatch table with it.
         ownedFiles: [
             "apps/api/src/routes/schedule/index.ts",
             "apps/api/src/services/scheduling/index.ts",
             "apps/api/src/services/scheduling/cal-provider.ts",
             "apps/api/src/services/scheduling/types.ts",
+            // #6182 (S9a) — the Cal adapter's own suite. Individually, never as a
+            // glob (§ D12 above, property 1: a glob entry is a silent no-op, so
+            // `__tests__/**` would ship no test at all to a keyed scaffold).
+            "apps/api/src/services/scheduling/__tests__/cal-provider.test.ts",
             "apps/mcp/src/tools/list_availability.ts",
             "apps/mcp/src/tools/get_event_meta.ts",
             "apps/mcp/src/tools/create_booking.ts",
-            "packages/ui/src/sections/Booker.tsx",
-            "packages/ui/src/sections/BookerIsland.tsx",
-            "packages/ui/src/blocks/BookerPanel.tsx",
-            "packages/ui/src/blocks/BookerSlotGrid.tsx",
-            "packages/ui/src/blocks/BookerAttendeeFields.tsx",
-            "packages/ui/src/blocks/BookerEventHeader.tsx",
-            "packages/ui/src/blocks/BookerDateStrip.tsx",
-            "packages/ui/src/sections/slices/scheduling.ts",
-            "apps/web/app/[locale]/schedule/page.tsx",
-            "apps/web/app/[locale]/schedule/confirmed/page.tsx",
+            "apps/web/app/[locale]/meet/page.tsx",
+            "apps/web/app/[locale]/meet/[slug]/page.tsx",
+            "apps/web/app/[locale]/meet/confirmed/page.tsx",
+            // #6085 (brief H7) — the six files the webhook receiver + the
+            // tenant-guarded appointments read add. Individually, never as a
+            // glob (§ D12 / this card's own comment above, property 1: a glob
+            // entry is a silent no-op, so __tests__/** would ship no test at all
+            // to a keyed scaffold). `apps/api/src/routes/webhooks/index.ts` is
+            // NOT added — it is the mixed barrel that also registers the Stripe
+            // receiver, the same "mixed barrel is never listed" precedent this
+            // slice already records for `routes/project-listings/index.ts`.
+            // `apps/api/src/routes/schedule/index.ts` is already listed above and
+            // stays (it re-exports `listAppointmentsRoute` alongside the three
+            // anonymous routes it already re-exports).
+            "apps/api/src/routes/webhooks/calcom.ts",
+            "apps/api/src/routes/webhooks/__tests__/calcom.test.ts",
+            "apps/api/src/services/scheduling/appointments.ts",
+            "apps/api/src/services/scheduling/__tests__/appointments.test.ts",
+            "apps/api/src/routes/schedule/appointments.ts",
+            "apps/api/src/routes/schedule/__tests__/appointments.test.ts",
+            // #6086 (brief H7) — the SITE's appointments page, the visible half of
+            // the read above. The co-located suite is listed EXPLICITLY alongside
+            // its page: `EXCLUDE_TEMPLATE_DIRS` below drops only the three
+            // top-level `apps/web/**/__tests__` directories, and the import-graph
+            // closure walks FORWARD from an owned file — a test that imports
+            // `../page` is a dependent, not a companion, so it is never swept
+            // along. Without the second entry a keyless scaffold would carry a
+            // test for a page it does not have.
+            "apps/web/app/[locale]/(authed)/appointments/page.tsx",
+            "apps/web/app/[locale]/(authed)/appointments/__tests__/page.test.tsx",
+            // #6183 S9b — the enabled-meeting-slugs gate. `meetings.ts` is its own
+            // file (not folded into `routes/workspaces/config.ts`, which is
+            // `workspace`/`multi-tenant`-owned) precisely because its GET reaches
+            // `services/scheduling/` — the SAME reason `routes/schedule/
+            // appointments.ts` above is its own file rather than a row on an
+            // existing route. `lib/public-meetings-config.ts` is the public-read
+            // boundary `routes/schedule/meeting-types.ts` (the anonymous read,
+            // already reached via the already-listed `routes/schedule/index.ts`)
+            // calls into.
+            "apps/api/src/routes/workspaces/meetings.ts",
+            "apps/api/src/routes/workspaces/__tests__/meetings.test.ts",
+            "apps/api/src/lib/public-meetings-config.ts",
+            "apps/api/src/routes/schedule/meeting-types.ts",
+            "apps/api/src/routes/schedule/__tests__/meeting-types.test.ts",
+            // meetings.ts is the FIRST scheduling-gated route to use the generic
+            // tenantDb() scope layer directly (its sibling, appointments.ts, does
+            // its own scoped read in services/scheduling/appointments.ts instead)
+            // — and `workspaceMeetings` is now in architecture.yaml's tenant-scope
+            // forbidden_pattern (#6183), so meetings.ts cannot bypass tenantDb()
+            // with a raw prisma call. Co-owned with `multi-tenant` below (the
+            // SAME two files, same reason `content.ts`'s own comment there
+            // records: "each tenancy slice must deliver it").
+            "apps/api/src/lib/tenant-db.ts",
+            "apps/api/src/services/tenant-context.ts",
         ],
-        // pageContributions (spec 5478; parent § D6 shape 1) — the booker and its
-        // confirmation page, whose route files `ownedFiles` above already carries.
-        // Neither row names seed content: both render from the /v1/schedule/*
-        // routes, not from an MDX file.
+        // pageContributions (spec 5478; parent § D6 shape 1) — the booker, the
+        // per-booking-type page and the confirmation page, whose route files
+        // `ownedFiles` above already carries. No row names seed content: all
+        // three render from the /v1/schedule/* routes, not from an MDX file.
         pageContributions: [
-            { route: "/schedule" },
-            { route: "/schedule/confirmed" },
+            { route: "/meet" },
+            { route: "/meet/[slug]" },
+            { route: "/meet/confirmed" },
+            // #6086 — the authed appointments page. Bracket (roster) grammar and no
+            // `content` key, for the same reason the three /meet rows carry none:
+            // it renders from `/v1/schedule/appointments`, not from an MDX file.
+            { route: "/appointments" },
+        ],
+        // patches (#5581 U3, D5) — delivers the extracted component package to a
+        // keyed scaffold's apps/web, mirroring the signal-collectors slice's
+        // identical merge-keys op below.
+        patches: [
+            {
+                target: "apps/web/package.json",
+                kind: "json",
+                ops: [
+                    {
+                        op: "merge-keys",
+                        path: ["dependencies"],
+                        entries: {
+                            "@working-theory/ui-scheduling": "workspace:*",
+                        },
+                    },
+                ],
+            },
         ],
     },
     // ── signal-collectors — flows, deliverables, project listings, waitlist
@@ -1089,6 +1276,94 @@ export const MODULE_SLICES = {
             "apps/api/src/bin/seed-waitlist-experiments.ts",
             "apps/mcp/src/tools/get_flow.ts",
             "apps/mcp/src/tools/submit_flow_step.ts",
+            // ── The review surface (#5677) — CO-OWNED with multi-tenant ──────────
+            //
+            // Every path below is ALSO a multi-tenant `ownedFiles` entry and stays
+            // one. Listing a file under two modules is additive, not a transfer:
+            // `paidModuleTemplateExclusions()` unions every paid module's entries,
+            // so the `templates/` snapshot is unchanged, and a multi-tenant scaffold
+            // keeps receiving these from the multi-tenant bundle exactly as before.
+            // What changes is that a signal-collectors bundle now carries them too.
+            //
+            // WHY THEY MUST BE HERE. #5677 widened `server.ts`'s review-surface
+            // registration from `multi-tenant` to `multi-tenant || signal-collectors`,
+            // because signal-collectors is the module that SELLS the instruments
+            // these routes read back. Registration and DELIVERY are separate layers:
+            // the widened gate calls `sliceRoutePlugin("waitlistExperimentRoutes")`
+            // and imports `projectListingTenantRoutes`, so on a scaffold whose
+            // `AILK_ENABLED_MODULES` names signal-collectors but whose tree lacks
+            // these files, `loadSlice` throws ERR_MODULE_NOT_FOUND during `build()`
+            // — construction, so EVERY route 500s rather than one. That is not a
+            // feature gap; it is the outage shape `lib/slice-load.ts` exists to
+            // diagnose.
+            //
+            // It is not hypothetical: `marketing-site` — the Pro flagship in
+            // `template-manifest.ts` — declares
+            // `requires: ["marketing", "docs-blog", "scheduling", "signal-collectors"]`,
+            // i.e. signal-collectors WITHOUT multi-tenant. That is exactly the
+            // configuration that would crash, which is why the gate and the delivery
+            // land together rather than the delivery being deferred.
+            //
+            // The closure is tight, verified by grep rather than assumed: none of
+            // these files imports `lib/tenant-db.ts` or `services/tenant-context.ts`
+            // (both multi-tenant-only). #5677 retargeted `waitlist-dashboard.ts`'s
+            // type import of `tenant-context.js` to the base `services/default-tenant.ts`,
+            // which severed the one cross-slice edge that existed.
+            //
+            // `routes/project-listings/{start,patch-draft,submit,public,me,respond,
+            // resume-token,patch-copy}.ts` are NOT listed — they are the free
+            // anonymous surface and the mixed barrel, covered by the note above this
+            // array, and they already ship unconditionally.
+            "apps/api/src/routes/waitlist-experiments/index.ts",
+            "apps/api/src/routes/waitlist-experiments/list.ts",
+            "apps/api/src/routes/waitlist-experiments/comparison.ts",
+            "apps/api/src/routes/waitlist-experiments/signup.ts",
+            "apps/api/src/routes/waitlist-experiments/signups.ts",
+            "apps/api/src/routes/waitlist-experiments/respond.ts",
+            "apps/api/src/services/waitlist-dashboard.ts",
+            // #6258 — the file waitlist-dashboard.ts imports for the pinned
+            // platform-operator read scope. It rides BOTH slices for the same
+            // reason its importer does: an unlisted import target breaks a
+            // signal-collectors-without-multi-tenant scaffold at build() time.
+            "apps/api/src/services/waitlist-operator-reads.ts",
+            // #6157 D14/D16 — the magnet Admin authoring surface's own sibling
+            // tenant scope is gated `multi-tenant || signal-collectors` (D4,
+            // the SAME expression this review-surface block co-owns files
+            // under), so both its route file AND `lib/tenant-db.ts` (the ONE
+            // data path it reads/writes through, FR3) must be delivered here
+            // too. `lib/tenant-db.ts` is ALSO listed under `multi-tenant` above
+            // — additive, not a transfer (the same reasoning this array's own
+            // header comment already states for every other file in it).
+            //
+            // The closure stays tight WITHOUT dragging in `tenant-context.ts` or
+            // the multi-tenant guard assembly behind it, because `tenant-db.ts`'s
+            // own type import was retargeted from `tenant-context.js` to the
+            // BASE-tree `services/default-tenant.js` in this same unit (D15) —
+            // the identical one-line class of move #5677 made for
+            // `waitlist-dashboard.ts` two paragraphs above this one.
+            "apps/api/src/routes/magnets/index.ts",
+            "apps/api/src/lib/tenant-db.ts",
+            "apps/api/src/routes/project-listings/get.ts",
+            "apps/api/src/routes/project-listings/list.ts",
+            "apps/api/src/routes/project-listings/patch.ts",
+            // The dashboard itself. Without these the Pro scaffold would boot with
+            // reachable review routes and no UI to read them through, and the two
+            // files that DO already ship into every scaffold
+            // (`waitlist/format.ts`, `waitlist/components/ForbiddenState.tsx` — never
+            // owned by any module) would stay orphaned. They import only
+            // `@working-theory/api-client`, `@working-theory/ui` and
+            // `@working-theory/validation`, all base packages, so this pulls in no
+            // multi-tenant dependency.
+            "apps/web/app/[locale]/(authed)/waitlist/page.tsx",
+            "apps/web/app/[locale]/(authed)/waitlist/[experimentId]/page.tsx",
+            "apps/web/app/[locale]/(authed)/waitlist/[experimentId]/signups/[leadId]/page.tsx",
+            "apps/web/app/[locale]/(authed)/waitlist/components/ExperimentsTable.tsx",
+            "apps/web/app/[locale]/(authed)/waitlist/components/OfferFunnelTable.tsx",
+            "apps/web/app/[locale]/(authed)/waitlist/components/RollupTicker.tsx",
+            "apps/web/app/[locale]/(authed)/waitlist/components/ScoreTrace.tsx",
+            "apps/web/app/[locale]/(authed)/waitlist/components/SignupsTable.tsx",
+            "apps/web/app/[locale]/(authed)/waitlist/components/WaitlistComparisonTabs.tsx",
+            "apps/web/app/[locale]/(authed)/waitlist/components/status-badges.tsx",
             // apps/web/app/[locale]/flows/** deliberately NOT listed here (unlike
             // the docs-blog precedent's own `blog`/`docs` page.tsx entries above),
             // even though every file under it is signal-collectors territory and
@@ -1115,18 +1390,29 @@ export const MODULE_SLICES = {
             // `NESTED_FOREIGN_MODULE_ENTRIES` for the companion fix that keeps its
             // presence from falsely reading as "projects carried".
             "apps/web/app/[locale]/projects/apply/ListingApplicationClient.tsx",
-            "packages/ui/src/sections/ListingApplicationFlow.tsx",
-            "packages/ui/src/sections/ProjectListingShelves.tsx",
-            "packages/ui/src/sections/FlowStepper.tsx",
-            "packages/ui/src/blocks/FlowSidePanel.tsx",
-            "packages/ui/src/blocks/ListingFullPreview.tsx",
-            "packages/ui/src/blocks/ListingQuestionReview.tsx",
-            "packages/ui/src/blocks/ListingTilePreview.tsx",
-            "packages/ui/src/blocks/ListingPrivacyNotice.tsx",
-            "packages/ui/src/blocks/ProjectListingCard.tsx",
-            "packages/ui/src/blocks/ResponseChart.tsx",
-            "packages/ui/src/blocks/ResultsReveal.tsx",
-            "packages/ui/src/sections/slices/signal-collectors.ts",
+            // #5581 U4 — the eleven signal-collectors components + the slice's own
+            // re-export entry point moved to packages-paid/ui-signal-collectors;
+            // the package is delivered to a keyed scaffold via `patches` below,
+            // not via `ownedFiles`/`installMap` (D5).
+            // #5562 — the report reader at `/reports/<slug>`. UNLIKE the flow routes
+            // above, this one DOES belong in `ownedFiles`, and for the same reason
+            // `projects/apply/ListingApplicationClient.tsx` does: `/reports` is a URL
+            // segment `MODULE_SURFACES["signal-collectors"] = ["flows"]` does not gate,
+            // so `excludedRoutePaths()` would leave it in a keyless scaffold. It has no
+            // upgrade-path fixture to protect either — it is net-new here, so nothing
+            // in `templates/` can regress by its absence.
+            "apps/web/app/[locale]/reports/[slug]/page.tsx",
+            //
+            // The two sections that route composes — `report-header` and
+            // `reports-list` — are deliberately NOT owned here. They are
+            // `SectionRenderer` DISPATCH entries with static imports, so stripping
+            // them would leave the renderer with dangling imports in a keyless
+            // scaffold; the escape hatch for a slice-owned dispatch entry is the
+            // `ModuleAbsent` placeholder (`booker`, `payment-receipt`), which is
+            // machinery neither of these needs. `document-viewer` (#5270) — the
+            // reader this route is built around, and the section with the strongest
+            // claim to being deliverables-only — is likewise unowned base
+            // `packages/ui`. A section is vocabulary; the ROUTE is the module.
         ],
         // pageContributions (spec 5478; parent § D6 shape 2) — the three flow
         // routes, named exactly as `surfaces.ts`'s ROUTE_SINCE keys name them.
@@ -1146,6 +1432,61 @@ export const MODULE_SLICES = {
             { route: "/flows/[slug]" },
             { route: "/flows/[slug]/start" },
             { route: "/flows/[slug]/results/[payload]" },
+            // #5562 — the report reader. Unlike the three rows above, this row's
+            // code IS this module's own `ownedFiles` (see the note beside it), so
+            // the contribution and the delivery shape carrying it agree here.
+            { route: "/reports/[slug]" },
+        ],
+        // installMap (#5618 D6.3) — the module's ten sample files, moved here out
+        // of `site-templates/marketing-site/` so the module OWNS its samples
+        // (Rule B) and a keyed `--modules signal-collectors` scaffold with no
+        // template lands them. Their in-repo home is
+        // `packages/create-ailk/module-templates/signal-collectors/**`, mirroring
+        // `commerce.installMap` below — the only other slice-level map — because
+        // an `installMap` KEY is a repo-relative source the producer copies
+        // literally, and `content/en/ProjectsList/projects.mdx` is ALSO this
+        // repo's own live marketing copy (a different file), which
+        // build-templates.mjs keeps out of every scaffold: under
+        // `module-templates/` the two never meet.
+        //
+        // Four entries are real renames (the flow and waitlist seeds the API
+        // reads, and the report PDF under apps/web/public/); the six MDX entries
+        // are self-addressed because no `pageContributions` row declares
+        // `/projects`, `/projects/[slug]` or `/thanks/[slug]` yet (spec § 7
+        // finding 7 — declaring them changes the enabled-surface set and so the
+        // Pro scaffold's file set, a separate decision). Once those rows exist
+        // the six move to `pageContributions[].content` with no further
+        // migration. `generate-sample-report.py` keeps its root-level
+        // destination (finding 1 — AC7 forbids changing the Pro file set).
+        installMap: {
+            "packages/create-ailk/module-templates/signal-collectors/content/en/ProjectsList/projects.mdx": "content/en/ProjectsList/projects.mdx",
+            "packages/create-ailk/module-templates/signal-collectors/content/en/Project/fit-check-funnel.mdx": "content/en/Project/fit-check-funnel.mdx",
+            "packages/create-ailk/module-templates/signal-collectors/content/en/Project/launch-site-in-fourteen-days.mdx": "content/en/Project/launch-site-in-fourteen-days.mdx",
+            "packages/create-ailk/module-templates/signal-collectors/content/en/ThankYouPage/contact.mdx": "content/en/ThankYouPage/contact.mdx",
+            "packages/create-ailk/module-templates/signal-collectors/content/en/ThankYouPage/newsletter.mdx": "content/en/ThankYouPage/newsletter.mdx",
+            "packages/create-ailk/module-templates/signal-collectors/content/en/ThankYouPage/apply.mdx": "content/en/ThankYouPage/apply.mdx",
+            "packages/create-ailk/module-templates/signal-collectors/flows/fit-check.flow.json": "database/flows/fit-check.flow.json",
+            "packages/create-ailk/module-templates/signal-collectors/waitlist/launch-waitlist.experiment.json": "database/waitlist/launch-waitlist.experiment.json",
+            "packages/create-ailk/module-templates/signal-collectors/reports/sample-report.pdf": "apps/web/public/reports/sample-report.pdf",
+            "packages/create-ailk/module-templates/signal-collectors/reports/generate-sample-report.py": "reports/generate-sample-report.py",
+        },
+        // patches (#5581 U4, D5) — delivers the extracted component package to a
+        // keyed scaffold's apps/web, mirroring the workspace slice's identical
+        // merge-keys op above.
+        patches: [
+            {
+                target: "apps/web/package.json",
+                kind: "json",
+                ops: [
+                    {
+                        op: "merge-keys",
+                        path: ["dependencies"],
+                        entries: {
+                            "@working-theory/ui-signal-collectors": "workspace:*",
+                        },
+                    },
+                ],
+            },
         ],
     },
     // ── commerce — per-site paid add-on (D-47, amending D-26) ─────────────────
@@ -1189,18 +1530,14 @@ export const MODULE_SLICES = {
             },
         },
         packages: {
-            // Duplicated VERBATIM from the multi-tenant slice's own "stripe-client"
-            // entry (§7 Q1 — a multi-tenant deployment using the Stripe billing
-            // portal or org-billing webhook routing also installs commerce, so
-            // both slices can be selected together) — the same order-independence
-            // reason the multi-tenant/scheduling slices state for `validation`
-            // below: `deriveArchitecture` merges `packages` blocks with
-            // `Object.assign`, so two slices declaring this key differently would
-            // make the derivation depend on module order.
-            "stripe-client": {
-                description: "Stripe SDK wrapper + webhook signature verification",
-                may_import_from: ["packages/validation"],
-            },
+            // `stripe-client` is deliberately NOT declared here (#5823). It was,
+            // duplicated verbatim from the multi-tenant slice, while the package was
+            // paid and commerce-owned. Since #5810 it is `commercial_tier: oss`,
+            // published public, and since #5812 its sole `apps/api` importer
+            // (`lib/stripe.ts`) is a base file — so the package is base, not a
+            // commerce slice member. The `packages/stripe-client` entries in the
+            // `may_import_from` lists above and in the base/multi-tenant slices are
+            // unaffected: those declare who may reach the package, not who owns it.
             // Duplicated VERBATIM from the marketing slice for the same
             // order-independence reason the multi-tenant/scheduling slices state.
             validation: {
@@ -1221,54 +1558,40 @@ export const MODULE_SLICES = {
         // ownedFiles (S1, #5088). SOURCE files only (#5182 D6) — no __tests__/,
         // no .stories.tsx, no .text.ts... except .text.ts siblings ARE source
         // (they ship as runtime copy modules, not test fixtures), so the ten
-        // annotated below are listed. 42 in all: 9 apps/api + 26 packages/ui
+        // annotated below are listed. 36 in all: 4 apps/api + 26 packages/ui
         // (15 components + 10 .text.ts siblings + this slice's own
         // sections/slices/commerce.ts) + 7 apps/web.
+        //
+        // THE PRIMITIVES LEFT THIS SLICE (D-64, epic #5770, #5796). The checkout
+        // launcher, the Stripe webhook receiver, customer mapping and the
+        // `lib/stripe.ts` shim are BASE TREE now: `apps/api/src/server.ts`
+        // registers them unconditionally and gates them at CALL time on the JWT
+        // `commerce` claim (`apps/api/src/lib/require-commerce-claim.ts`), so a
+        // keyless scaffold must CARRY them. Claiming them here is what deleted
+        // them from that scaffold while the server still loaded them —
+        // ERR_MODULE_NOT_FOUND inside build(), every route 500ing, which is the
+        // exact defect `tools/lint-slice-registration.ts` (#5701) exists to
+        // catch. The six that left: lib/stripe.ts,
+        // routes/checkout/{index,sessions}.ts, routes/webhooks/{index,stripe}.ts
+        // and routes/webhooks/README.md. The four below STAY — they are commerce
+        // OVERLAY, still registered behind `isModuleEnabled("commerce")` and
+        // still carrying their `// oss: false` markers.
         ownedFiles: [
-            "apps/api/src/lib/stripe.ts",
-            "apps/api/src/routes/checkout/index.ts",
-            "apps/api/src/routes/checkout/sessions.ts",
-            "apps/api/src/routes/webhooks/index.ts",
-            "apps/api/src/routes/webhooks/stripe.ts",
-            // README.md documents the Stripe webhook receiver — not a test/
-            // generated file, and its absence is exactly what left a stray
-            // apps/api/src/routes/webhooks/ directory in a keyless templates/
-            // snapshot (empirically found, #5364 build pass): the import-graph
-            // closure only scans source extensions, never markdown, so once
-            // index.ts and stripe.ts are excluded this is the one file left
-            // behind. Same defect class #5366 found and fixed the same way for
-            // routes/flows/README.md — see that entry above.
-            "apps/api/src/routes/webhooks/README.md",
             "apps/api/src/routes/flow-checkouts/index.ts",
             "apps/api/src/routes/flows/recommender.ts",
             "apps/api/src/services/recommender-capture.ts",
             "apps/api/src/services/flow-checkouts.ts",
-            "packages/ui/src/blocks/CheckoutForm.tsx",
-            "packages/ui/src/blocks/CheckoutForm.text.ts",
-            "packages/ui/src/blocks/CheckoutPriceCard.tsx",
-            "packages/ui/src/blocks/PaymentLinkCard.tsx",
-            "packages/ui/src/blocks/PaymentLinkCard.text.ts",
-            "packages/ui/src/blocks/PaymentLinkForm.tsx",
-            "packages/ui/src/blocks/PaymentLinkForm.text.ts",
-            "packages/ui/src/blocks/PaymentLinkList.tsx",
-            "packages/ui/src/blocks/InvoiceForm.tsx",
-            "packages/ui/src/blocks/InvoiceForm.text.ts",
-            "packages/ui/src/blocks/InvoiceList.tsx",
-            "packages/ui/src/blocks/InvoiceList.text.ts",
-            "packages/ui/src/blocks/SubscriptionStatus.tsx",
-            "packages/ui/src/blocks/SubscriptionStatus.text.ts",
-            "packages/ui/src/blocks/StripeActionButton.tsx",
-            "packages/ui/src/blocks/PaymentStatusBadge.tsx",
-            "packages/ui/src/blocks/PaymentStatusBadge.text.ts",
-            "packages/ui/src/blocks/PaymentResult.tsx",
-            "packages/ui/src/blocks/PaymentResult.text.ts",
-            "packages/ui/src/blocks/PortalEntry.tsx",
-            "packages/ui/src/panels/InvoiceDetail.tsx",
-            "packages/ui/src/panels/InvoiceDetail.text.ts",
-            "packages/ui/src/sections/PaymentReceipt.tsx",
-            "packages/ui/src/sections/PricingTable.tsx",
-            "packages/ui/src/sections/PricingTable.text.ts",
-            "packages/ui/src/sections/slices/commerce.ts",
+            // #6038 — the buyer-scoped subscription-status route pair (the
+            // update-your-card banner's read + portal handoff). Commerce OVERLAY,
+            // same posture as the four flow-checkouts/recommender entries above.
+            "apps/api/src/routes/subscription/index.ts",
+            "apps/api/src/routes/subscription/me.ts",
+            "apps/api/src/routes/subscription/portal.ts",
+            "apps/api/src/services/subscription.ts",
+            // #5581 U5 — the fifteen commerce components (+ ten .text.ts extractors
+            // + the slice's own re-export entry point) moved to
+            // packages-paid/ui-commerce; the package is delivered to a keyed
+            // scaffold via `patches` below, not via `ownedFiles`/`installMap` (D5).
             "apps/web/app/[locale]/flows/[slug]/checkout.actions.ts",
             "apps/web/app/[locale]/flows/[slug]/results/[payload]/page.tsx",
             "apps/web/app/[locale]/flows/[slug]/results/[payload]/ResultsClient.tsx",
@@ -1298,7 +1621,32 @@ export const MODULE_SLICES = {
             "packages/create-ailk/module-templates/commerce/.claude/skills/scaffold-commerce/templates/portal-route.template.ts": ".claude/skills/scaffold-commerce/templates/portal-route.template.ts",
             "packages/create-ailk/module-templates/commerce/.claude/skills/scaffold-commerce/templates/stripe-config.template.ts": ".claude/skills/scaffold-commerce/templates/stripe-config.template.ts",
             "packages/create-ailk/module-templates/commerce/.claude/skills/scaffold-commerce/templates/subscription-route.template.ts": ".claude/skills/scaffold-commerce/templates/subscription-route.template.ts",
+            // The commerce-boundary rule (#6039/#6070, this entry #6041): ships to
+            // a commerce-keyed scaffold's project root so an agent working there
+            // reads the money/live-mode/personal-data classification before it
+            // acts. One more literal entry alongside the ten scaffold-commerce
+            // skill entries above, for the same reason — a directory source is
+            // rejected by `validateInstallMap`.
+            "packages/create-ailk/module-templates/commerce/.claude/rules/commerce-boundary.md": ".claude/rules/commerce-boundary.md",
         },
+        // patches (#5581 U5, D5) — delivers the extracted component package to a
+        // keyed scaffold's apps/web, mirroring the workspace slice's identical
+        // merge-keys op above.
+        patches: [
+            {
+                target: "apps/web/package.json",
+                kind: "json",
+                ops: [
+                    {
+                        op: "merge-keys",
+                        path: ["dependencies"],
+                        entries: {
+                            "@working-theory/ui-commerce": "workspace:*",
+                        },
+                    },
+                ],
+            },
+        ],
     },
 };
 /**
@@ -1346,9 +1694,98 @@ export function normalizeModules(modules) {
  *   Passed in rather than derived from `import.meta.url`, which ts-jest cannot
  *   load — the same reason `sync-routes.ts` documents for staying pure.
  */
+/**
+ * Scaffold destinations that MORE THAN ONE module's `ownedFiles` declares —
+ * the co-ownership the `#5618 D4` install-time ownership registry must treat
+ * as intentional rather than as an overwrite (#5702 follow-up).
+ *
+ * Co-ownership is how a file reaches a scaffold under either of two modules
+ * without being transferred away from the other. #5677 needed it for the
+ * submissions review surface: the routes register under
+ * `multi-tenant || signal-collectors`, so BOTH bundles must be able to
+ * deliver them, or the module that lacks them throws
+ * `ERR_MODULE_NOT_FOUND` during `build()`.
+ *
+ * `validateLayerOwnership` (`lib/extract-module-bundle.ts`) refuses a
+ * destination an earlier layer already wrote, because a silent
+ * last-writer-wins between two modules that disagree is the bug `#5618 D4`
+ * exists to catch. Two modules that both DECLARE the same repo file are not
+ * that case: they stage the same bytes from the same source, so whichever
+ * lands second writes what is already there. Without this allowance a
+ * scaffold selecting both modules — `saas-product`, whose `requires` names
+ * `signal-collectors` AND `multi-tenant` — aborts mid-install, after the
+ * first module's files are on disk.
+ *
+ * Only a DECLARED overlap is allowed. A destination two layers collide on
+ * without both naming it in `ownedFiles` is still refused, which is the
+ * whole invariant.
+ */
+export function coOwnedModuleDestinations() {
+    const seen = new Map();
+    for (const slice of Object.values(MODULE_SLICES)) {
+        // A module's own list is deduplicated first: repetition within one slice
+        // is not co-ownership and must not license an overlap on its own.
+        for (const file of new Set(slice.ownedFiles ?? [])) {
+            seen.set(file, (seen.get(file) ?? 0) + 1);
+        }
+    }
+    const coOwned = new Set();
+    for (const [file, count] of seen) {
+        if (count > 1)
+            coOwned.add(file);
+    }
+    return coOwned;
+}
+// Template-relative directories excluded from the snapshot outright (#4154).
+//   - apps/web/__tests__ — this repo's own harness tests. Several import route
+//     modules across multiple surfaces (resources-downloads-integrations-phase2,
+//     standalone-informational-routes, routes/blog-route, blog-dir-resolution),
+//     so they fail outright in a scaffold whose surfaces are gated off. The
+//     co-located app/[locale]/<surface>/__tests__ suites travel with their
+//     surface and are unaffected.
+//   - apps/web/app/[locale]/__tests__ — same class: page-renderer-migration
+//     reaches across surfaces (`../launch-service/page`), so it breaks in a
+//     scaffold that gated launch-service off. The PER-SURFACE co-located
+//     suites (app/[locale]/<surface>/__tests__) import only their own route and
+//     travel with their surface, so they are kept.
+//   - apps/web/content — the blog/docs sample posts (the launching-ailk class).
+//     Replaced by neutral stubs from template-overlay/.
+//   - apps/web/app/[locale]/(authed)/edit — the Pro content host's editor
+//     routes (#5977; added to apps/web by #5957, spec 5872 FR1/FR2). Both
+//     pages are `// oss: false` and the [type]/[slug] page imports
+//     `@working-theory/admin-ui`, which a keyless (Free) scaffold does not
+//     carry — so shipping them puts two files importing an absent package
+//     into the scaffold and fails both co-located `__tests__` suites under
+//     verify-scaffold's `apps/web` jest run. The directory is taken whole,
+//     `__tests__` with it, since a test of an excluded route has nothing to
+//     test.
+//
+//     WHY AN EXCLUSION AND NOT A MODULE SLICE. Spec 5872 D11 settled the two
+//     constraints that rule out the alternatives, quoted rather than
+//     re-derived:
+//       1. "content-write cannot be a MODULE_SLICES key"
+//          (`module-architecture.ts:214-222` — a key would make
+//          `--modules content-write` a valid selection).
+//       2. "the workspace slice is the wrong owner" (#5853 §4.2/D14 — it
+//          would bind the Pro editor to a Pro Plus bundle).
+//     So there is no correct `ownedFiles` owner for these files today. This
+//     entry is the INTERIM: a flat exclusion that keeps the keyless scaffold
+//     honest until a content-write delivery path exists, at which point the
+//     routes move to that path's owner and this entry comes back out. The
+//     routes stay registered in `ROUTE_SINCE` (src/surfaces.ts) meanwhile —
+//     see that entry, and sync-routes' AC-5 coverage test, which reads this
+//     list so the resulting ROUTE_SINCE-vs-template absence is justified
+//     rather than reported stale.
+export const EXCLUDE_TEMPLATE_DIRS = [
+    "apps/web/__tests__",
+    "apps/web/app/__tests__",
+    "apps/web/app/[locale]/__tests__",
+    "apps/web/app/[locale]/(authed)/edit",
+    "apps/web/content",
+];
 export function paidModuleTemplateExclusions(snapshotRoots, repoRoot) {
     const roots = new Set(snapshotRoots);
-    const excluded = new Set();
+    const seeds = new Set();
     for (const moduleName of PAID_MODULES) {
         for (const owned of MODULE_SLICES[moduleName]?.ownedFiles ?? []) {
             const rel = owned.split(sep).join("/");
@@ -1356,103 +1793,11 @@ export function paidModuleTemplateExclusions(snapshotRoots, repoRoot) {
                 continue;
             if (rel.includes("*"))
                 continue;
-            excluded.add(rel);
-        }
-    }
-    // Companion closure by import graph, to a fixed point — never a filename
-    // stem rule (#5182 D7), which misses eleven files and over-marks three.
-    const candidates = listFilesUnder(repoRoot, [...roots]);
-    for (;;) {
-        let grew = false;
-        for (const file of candidates) {
-            if (excluded.has(file))
-                continue;
-            const imports = relativeImportsOf(join(repoRoot, file));
-            for (const spec of imports) {
-                const target = resolveRelativeImport(file, spec, candidates);
-                if (target !== undefined && excluded.has(target)) {
-                    excluded.add(file);
-                    grew = true;
-                    break;
-                }
-            }
-        }
-        if (!grew)
-            break;
-    }
-    return [...excluded].sort();
-}
-const SOURCE_EXTS = [".ts", ".tsx", ".js", ".jsx", ".mjs", ".cjs"];
-/** Every source file under the given repo-relative roots, as "/"-joined paths. */
-function listFilesUnder(repoRoot, roots) {
-    const out = new Set();
-    const skip = new Set(["node_modules", ".next", "dist", ".turbo", ".source"]);
-    const stack = roots.map((r) => r);
-    while (stack.length > 0) {
-        const rel = stack.pop();
-        const abs = join(repoRoot, rel);
-        let entries;
-        try {
-            entries = readdirSync(abs, { withFileTypes: true });
-        }
-        catch {
-            continue;
-        }
-        for (const entry of entries) {
-            if (skip.has(entry.name))
-                continue;
-            const childRel = `${rel}/${entry.name}`;
-            if (entry.isDirectory())
-                stack.push(childRel);
-            else if (SOURCE_EXTS.some((e) => entry.name.endsWith(e)))
-                out.add(childRel);
+            seeds.add(rel);
         }
     }
-    return out;
-}
-/** The relative import specifiers a source file names (static imports + re-exports). */
-function relativeImportsOf(absPath) {
-    let src;
-    try {
-        src = readFileSync(absPath, "utf8");
-    }
-    catch {
-        return [];
-    }
-    const out = [];
-    for (const m of src.matchAll(/(?:^|\n)\s*(?:import|export)[\s\S]{0,400}?from\s*["'](\.[^"']*)["']/g))
-        out.push(m[1]);
-    for (const m of src.matchAll(/\bimport\s*\(\s*["'](\.[^"']*)["']\s*\)/g))
-        out.push(m[1]);
-    return out;
-}
-/**
- * Resolve a relative specifier against the candidate set. TypeScript ESM writes
- * `./x.js` for `./x.ts`, so the `.js` → `.ts`/`.tsx` rewrite is the common case.
- */
-function resolveRelativeImport(fromFile, spec, candidates) {
-    const base = posixJoin(dirname(fromFile.split("/").join(sep)), spec);
-    const stem = base.replace(/\.(js|jsx|mjs|cjs)$/, "");
-    for (const cand of [
-        base,
-        ...SOURCE_EXTS.map((e) => stem + e),
-        ...SOURCE_EXTS.map((e) => `${stem}/index${e}`),
-    ])
-        if (candidates.has(cand))
-            return cand;
-    return undefined;
-}
-/** Join and normalize a "/"-separated path, resolving `.` and `..` segments. */
-function posixJoin(dir, spec) {
-    const parts = `${dir.split(sep).join("/")}/${spec}`.split("/");
-    const out = [];
-    for (const part of parts) {
-        if (part === "" || part === ".")
-            continue;
-        if (part === "..")
-            out.pop();
-        else
-            out.push(part);
-    }
-    return out.join("/");
+    // Companion closure by import graph, to a fixed point — the shared walker
+    // (`lib/import-graph.ts`), so `tools/lint-slice-registration.ts` asks the
+    // question with the same resolution this answer was computed with (#5701).
+    return [...importClosure(repoRoot, [...roots], seeds)].sort();
 }