create-ailk 0.7.0 → 0.9.0

package/dist/template-manifest.js

@@ -1,5 +1,7 @@
 import { classifyModules } from "./lib/module-tier.js";
 import { MODULE_SLICES, normalizeModules, } from "./module-architecture.js";
+import { ALIASES, SHAPE_ROSTERS, SHAPE_STARTER_ALIASES, } from "./starter-grid.js";
+import { RECOGNIZED_TEMPLATES } from "./template-names.js";
 /**
  * The closed **shape** enum (starter-template contract § The three axes,
  * operator-disposed 2026-09-24) — `<primary node>-<offering node>` in
@@ -17,28 +19,13 @@ export const STARTER_SHAPES = [
 ];
 /**
  * The closed **design** enum (same contract section) — the look applied to
- * any shape; orthogonal to it by construction.
+ * any shape; orthogonal to it by construction. Each name RESOLVES to a
+ * package at `site-templates/designs/<name>/` (#6813 D2/D3, D11 pins this set
+ * equal to that directory listing): `resolveDesign` (`design-scaffold.ts`)
+ * reads the package's own `layout`, `colors` and treatments — no design fact
+ * lives in this module, or anywhere in `packages/create-ailk/src`, any more.
  */
 export const STARTER_DESIGNS = ["standard", "minimalism"];
-/**
- * Each design's layout knobs (#6638) — the part of a design that is chrome,
- * so a template names `design:` instead of re-typing a `layout` block, and any
- * shape can wear any design. `resolveSiteChrome(layout, design)` reads it:
- * an explicit `TemplateManifest.layout` wins field by field, then this, then
- * `DEFAULT_SITE_CHROME`. `standard` declares nothing — it IS the defaults, so
- * spelling them out here would be a second copy of them to drift. A plain
- * object, not a file: this module touches no disk. The design's documented
- * look lives in `site-templates/designs/<design>/DESIGN.md`.
- */
-export const DESIGN_LAYOUTS = {
-    standard: {},
-    minimalism: {
-        nav: "mark-only",
-        footer: "centered",
-        announcementBanner: false,
-        home: "deck",
-    },
-};
 /**
  * The base layer's directory under `site-templates/` (#5618 D1) — the seed
  * files every template reaches by declaring `extends`, installed by
@@ -69,386 +56,178 @@ export class TemplateError extends Error {
     }
 }
 /**
- * The three pages every starter carries whatever its shape (#6658 D5,
- * `docs/decisions/starter-roster-page-set.md` D4/D7): a glossary, a newsletter
- * signup and a book-a-call page. Each is a module-less `GATEABLE_SURFACES`
- * entry the roster enables, with its seed in `_base`. A template carrying the
- * scheduling module overrides `BookCall/book-call.mdx` in its own tree, so the
- * call to action opens `/meet` rather than `/contact`.
+ * Compose one alias into its manifest (#6753 D5, extended #6757 D7): the
+ * shape's standard roster, minus the alias's `drop` routes, with its `add`
+ * rows inserted before the `before` route (appended when there is none),
+ * then each `insert` group's rows spliced before ITS OWN `before` route, in
+ * array order — the one alias with more than one anchor point
+ * (`minimalism-site`) uses this to interleave its own rows into the shape's
+ * row order. Rows are pushed by reference, never cloned, so
+ * `manifest.roster.includes(row)` identity checks downstream keep working.
+ * Every refusal names the alias, so a malformed table fails at load — the
+ * shipped one — or in the test that injected it.
+ *
+ * @throws TemplateError on a `drop`, `before` or an `insert` group's `before`
+ *   naming a route the shape (or the roster built so far) does not carry, a
+ *   `before` with nothing to add, an `insert` group with empty `rows`, an
+ *   `add`/`insert` row whose route a kept shape row already claims, or two
+ *   `add`/`insert` rows naming one route.
  */
-const SHAPE_INDEPENDENT_ROWS = [
-    { route: "/glossary", content: ["content/en/GlossaryList/glossary.mdx"] },
-    {
-        route: "/newsletter",
-        content: ["content/en/NewsletterSignup/newsletter.mdx"],
-    },
-    { route: "/book-a-call", content: ["content/en/BookCall/book-call.mdx"] },
-];
+function composeManifest(name, alias) {
+    const rows = SHAPE_ROSTERS[alias.shape];
+    const { drop = [], add = [], before, insert = [] } = alias.differences ?? {};
+    for (const route of drop) {
+        if (!rows.some((row) => row.route === route)) {
+            throw new TemplateError(`alias "${name}": differences.drop names "${route}", which shape "${alias.shape}" does not carry`);
+        }
+    }
+    const kept = rows.filter((row) => !drop.includes(row.route));
+    let roster;
+    if (before === undefined) {
+        roster = [...kept, ...add];
+    }
+    else {
+        const at = kept.findIndex((row) => row.route === before);
+        if (at === -1) {
+            throw new TemplateError(`alias "${name}": differences.before names "${before}", which shape "${alias.shape}" does not carry after its drops`);
+        }
+        if (add.length === 0) {
+            throw new TemplateError(`alias "${name}": differences.before names "${before}" but differences.add is empty`);
+        }
+        roster = [...kept.slice(0, at), ...add, ...kept.slice(at)];
+    }
+    for (const group of insert) {
+        const at = roster.findIndex((row) => row.route === group.before);
+        if (at === -1) {
+            throw new TemplateError(`alias "${name}": differences.insert names "${group.before}", which shape "${alias.shape}" does not carry after its drops`);
+        }
+        if (group.rows.length === 0) {
+            throw new TemplateError(`alias "${name}": differences.insert names "${group.before}" but its rows is empty`);
+        }
+        roster = [...roster.slice(0, at), ...group.rows, ...roster.slice(at)];
+    }
+    const shapeRoutes = new Set(kept.map((row) => row.route));
+    const added = new Set();
+    for (const row of [...add, ...insert.flatMap((group) => group.rows)]) {
+        if (shapeRoutes.has(row.route)) {
+            throw new TemplateError(`route "${row.route}" is claimed by both shape "${alias.shape}" and alias "${name}"`);
+        }
+        if (added.has(row.route)) {
+            throw new TemplateError(`alias "${name}": differences.add names route "${row.route}" twice`);
+        }
+        added.add(row.route);
+    }
+    return {
+        name,
+        requires: alias.modules,
+        ...(alias.layout && { layout: alias.layout }),
+        categories: alias.categories,
+        shape: alias.shape,
+        design: alias.design,
+        extends: BASE_LAYER_DIR,
+        roster,
+    };
+}
 /**
- * The rows every `organization-product` template brings itself — one declared
- * page set, whichever layer carries each seed. Re-derived by #6658 from the
- * standard (`derive-roster.py --entity-type software --offering-type software
- * --primary-goal convert --scale global`, the `--shape organization-product`
- * equivalent), edited only by the deviations the Free manifest's § 3a records
- * with their reasons. With a template named, `scaffold()` keeps a `_base` or
- * overlay seed only when a merged roster row names it (#6646 D1): the roster
- * decides what installs, and the manifest generator's `--check` proves it.
- *
- * Two layers, one roster:
- *
- *   - `/`, `/software/[slug]`, `/use-cases`, `/about`, `/faq`, `/contact` and
- *     `/purchase-policy` take their content from the overlay
- *     (`template-overlay/content/en/**`, copied whole into `templates/` by
- *     `build-templates.mjs`). `/software/[slug]` is the product's own detail
- *     page (`/software/product`, a SoftwareProduct), which replaced the
- *     `/features` stand-in (#6658 D3); its route is core, like `/about`.
- *     `/use-cases` lists the three UseCase pages at `/use-cases/[slug]`
- *     (#6658 D4).
- *   - `/pricing`, `/privacy`, `/terms`, `/glossary`, `/newsletter`,
- *     `/book-a-call` and the three UseCase pages take their content from the
- *     base layer (`site-templates/_base/content/**`, #5618 D1), which every
- *     template reaches by declaring `extends` — installed before the module
- *     bundles and the template's own tree, so a template may override a base
- *     page by shipping the same path. Their surfaces are module-less by
- *     construction (parent § D16, #6658 D5): a template enables them by
- *     NAMING them in its roster — `scaffold()` selects their
- *     `GATEABLE_SURFACES` entries from the merged roster's routes (#5469 D10).
+ * The declared templates, each composed once at load from its `ALIASES` row
+ * (#6753) — no manifest here is hand-typed, so a template's shape, design,
+ * modules and roster have one authority: `starter-grid.ts`. Declaration order
+ * is `ALIASES`'s, which is `RECOGNIZED_TEMPLATES`'s.
  *
- * `/software`, `/sign-in` and `/sign-up` carry no `content`: they are code
- * routes (the SoftwareProduct listing, the SignInCard island, the sign-up
- * form), like the API-backed rows the scheduling module contributes — listed
- * so the manifest is a complete install record, where the generator marks
- * them `kind: route` (#6646 D2).
- *
- * `/purchase-policy` is the product-shape purchase policy (#6646 D3): its
- * overlay seed carries returns, shipping and refunds sections — the overlay,
- * not `_base`, because the route is core and a scaffold naming no template
- * serves it too. A service-shape template overrides that seed with its own
- * cancellation and refunds file.
- *
- * `/blog` is deliberately NOT here (#5469 D3): the docs-blog module
- * contributes its own `/blog` row, so a base row would make `mergeRoster`
- * refuse every template that takes that module. The Free teaser row is
- * declared on `marketing-site-free` alone, below.
+ * Frozen (#5507): this registry is also the issuer's authorization allowlist
+ * (spec 5480 § C7) — a mutable global there could be monkey-patched at
+ * runtime. A caller needing a different registry for a test injects its own
+ * fixture rather than mutating this one.
  */
-const TEMPLATE_BASE_ROSTER = [
-    { route: "/", content: ["content/en/HomePage/home.mdx"] },
-    { route: "/software" },
-    { route: "/software/[slug]", contentDir: "content/en/SoftwareProduct" },
-    {
-        route: "/use-cases",
-        content: ["content/en/UseCasesList/use-cases.mdx"],
-    },
-    { route: "/use-cases/[slug]", contentDir: "content/en/UseCase" },
-    { route: "/pricing", content: ["content/en/Pricing/pricing.mdx"] },
-    { route: "/about", content: ["content/en/AboutPage/about.mdx"] },
-    { route: "/faq", content: ["content/en/FAQPage/faq.mdx"] },
-    { route: "/contact", content: ["content/en/ContactPage/contact.mdx"] },
-    ...SHAPE_INDEPENDENT_ROWS,
-    { route: "/sign-in" },
-    { route: "/sign-up" },
-    { route: "/privacy", content: ["content/en/PrivacyPage/privacy.mdx"] },
-    { route: "/terms", content: ["content/en/TermsPage/terms.mdx"] },
-    {
-        route: "/purchase-policy",
-        content: ["content/en/PurchasePolicyPage/purchase-policy.mdx"],
-    },
-];
+export const TEMPLATE_MANIFESTS = Object.freeze(Object.fromEntries(RECOGNIZED_TEMPLATES.map((name) => [
+    name,
+    composeManifest(name, ALIASES[name]),
+])));
 /**
- * The Free `/blog` teaser (#5469 D3) — one static BlogList page (schema `Blog`
- * with an empty `ItemList`; the correct page type, not a LandingPage) that
- * says what the Pro docs-blog module gives you. It is served by the generic
- * `[slug]` route — which probes `LandingPage` first, then `BlogList` — over
- * `content/en/BlogList/blog.mdx`, which ships in the always-copied overlay. `/blog` degrades by DIRECTORY PRECEDENCE, not
- * by a module gate: in a keyed docs-blog scaffold the module's own
- * `blog/[[...slug]]/page.tsx` directory exists and Next.js resolves the static
- * segment first, so the teaser file is inert; keyless, no `blog/` directory
- * exists and the teaser renders. Declared on the Free template only — on
- * `marketing-site` the docs-blog contribution claims the route.
+ * The composed FREE manifest per shape with no `--template` alias of its own
+ * (#6757 D5) — the coordinates a keyless `--shape S` builds. `Object.freeze`d,
+ * composed once at load by the same module-private `composeManifest` over
+ * `SHAPE_STARTER_ALIASES`, each manifest's `name` the shape. Data holding
+ * composed manifests, the status D5 gives `TEMPLATE_MANIFESTS`;
+ * `resolveTemplate` stays the only exported function that yields a
+ * template's roster, and its behavior is unchanged — it does NOT resolve a
+ * shape name (NFR-3, the issuer allowlist stays `TEMPLATE_MANIFESTS`-only).
  */
-const FREE_BLOG_TEASER_ROW = {
-    route: "/blog",
-    content: ["content/en/BlogList/blog.mdx"],
-};
+export const SHAPE_STARTERS = Object.freeze(Object.fromEntries(Object.entries(SHAPE_STARTER_ALIASES).map(([name, alias]) => [
+    name,
+    composeManifest(name, alias),
+])));
 /**
- * The rows for the `signal-collectors` bundle's six sample pages (#6646
- * disposition (a)) — the project listing, its two project pages and the
- * three thank-you pages its `installMap` lands. The module contributes no
- * row for any of these routes (`module-architecture.ts`'s installMap
- * comment), so a template that takes the module declares them, and the
- * roster names every page the scaffold installs. `/projects` is a
- * module-less `GATEABLE_SURFACES` entry, so naming it here also copies the
- * route directory the samples render through (`rosterSurfaces`).
+ * Where a starter's files live under `site-templates/` (#6757 D5) — the one
+ * place that says so. A `SHAPE_STARTERS` key (a bare-shape starter with no
+ * `--template` alias) lives at `shapes/<name>`, out of the template showcase
+ * (§ 1.6). A declared `--template` alias whose `ownTree` is `false` (spec
+ * 6892 D1) ships no directory of its own: its seed layer is its shape's tree.
+ * Every other name (a declared alias with its own tree) is unchanged.
  */
-const SIGNAL_COLLECTORS_SAMPLE_ROWS = [
-    { route: "/projects", content: ["content/en/ProjectsList/projects.mdx"] },
-    { route: "/projects/[slug]", contentDir: "content/en/Project" },
-    { route: "/thanks/[slug]", contentDir: "content/en/ThankYouPage" },
-];
+export function templateTreeDir(name) {
+    if (Object.prototype.hasOwnProperty.call(SHAPE_STARTERS, name)) {
+        return `shapes/${name}`;
+    }
+    const alias = ALIASES[name];
+    if (alias?.ownTree === false) {
+        return `shapes/${alias.shape}`;
+    }
+    return name;
+}
 /**
- * `minimalism-site`'s own rows (#5589) — the one declared template that does
- * not reuse `TEMPLATE_BASE_ROSTER`. Its page set is the issue's ROSTER, and
- * the rows it does NOT carry are as deliberate as the ones it does: no
- * `/how-it-works`, product page or `/pricing` (a reports-first site sells
- * nothing from a pricing table), and no `/sign-in` (a code route every
- * scaffold carries regardless — `CORE_ROUTE_DIRS` — which this template
- * simply does not advertise as one of its pages). It does carry the three
- * pages every starter carries (`SHAPE_INDEPENDENT_ROWS`, #6658), with its
- * own `/book-a-call` seed pointing at the scheduling module's `/meet`.
- *
- * `/purchase-policy` is the service-shape purchase policy (#6646 D3) — this
- * template's own cancellation and refunds seed, overriding `_base`'s.
+ * Whether `name` ships its own `site-templates/<name>/` directory (spec 6892
+ * D1) — `false` only for a declared `--template` alias whose `ownTree` is
+ * `false` (`minimalism-site` today). A `SHAPE_STARTERS` key owns its
+ * `shapes/<name>` tree outright, so it is never treeless by this predicate
+ * even though `templateTreeDir` also renames its directory.
  *
- * `/meet`, `/meet/[slug]`, `/meet/confirmed`, `/reports/[slug]` and the three
- * `/flows/*` rows are absent here on purpose: they are the `scheduling` and
- * `signal-collectors` modules' own `pageContributions`, merged in by
- * `mergeRoster`. Declaring one here would make that merge refuse the
- * template outright (§ D8's both-claimants refusal).
+ * The one place a caller outside this module (or `template-names.ts`) asks
+ * "does this name have its own tree" without needing `ALIASES` itself —
+ * `starter-grid.ts`'s own header restricts its importers to this file and
+ * `template-names.ts`, so a producer script asking this question goes
+ * through this predicate rather than importing `ALIASES` directly.
  */
-const MINIMALISM_ROSTER = [
-    { route: "/", content: ["content/en/HomePage/home.mdx"] },
-    { route: "/reports", content: ["content/en/LandingPage/reports.mdx"] },
-    { route: "/about", content: ["content/en/AboutPage/about.mdx"] },
-    { route: "/services", content: ["content/en/ServicesList/services.mdx"] },
-    { route: "/services/[slug]", contentDir: "content/en/Service" },
-    { route: "/contact", content: ["content/en/ContactPage/contact.mdx"] },
-    { route: "/referral", content: ["content/en/LandingPage/referral.mdx"] },
-    { route: "/faq", content: ["content/en/FAQPage/faq.mdx"] },
-    ...SHAPE_INDEPENDENT_ROWS,
-    { route: "/privacy", content: ["content/en/PrivacyPage/privacy.mdx"] },
-    { route: "/terms", content: ["content/en/TermsPage/terms.mdx"] },
-    {
-        route: "/purchase-policy",
-        content: ["content/en/PurchasePolicyPage/purchase-policy.mdx"],
-    },
-    ...SIGNAL_COLLECTORS_SAMPLE_ROWS,
-];
+export function isOwnTree(name) {
+    if (Object.prototype.hasOwnProperty.call(SHAPE_STARTERS, name))
+        return true;
+    const alias = ALIASES[name];
+    return alias?.ownTree !== false;
+}
 /**
- * `simple-service`'s own rows (#6087) — the T1 lawn-care roster of Epic #5778.
- * The second declared template that does not reuse `TEMPLATE_BASE_ROSTER`: a
- * lawn-care site sells three named services from `/services`, not from a
- * pricing table, so `/how-it-works`, the product page and `/pricing` are absent —
- * and so are their seeds: `scaffold()` installs a `_base` or overlay seed
- * only for a row that names it (#6646 D1), exactly as for `minimalism-site`.
- *
- * `/meet`, `/meet/[slug]`, `/meet/confirmed` and `/appointments` are absent
- * here on purpose: they are the `scheduling` module's own
- * `pageContributions`, merged in by `mergeRoster`. Declaring one here would
- * make that merge refuse the template outright (§ D8's both-claimants
- * refusal).
- *
- * `/purchase/success` and `/purchase/cancel` ARE declared here, and that is a
- * documented divergence from spec § D3. The spec was written at a pin where
- * #6084 was expected to add the pair to `MODULE_SLICES.commerce`'s
- * `pageContributions`. It did not: the operator's shape-2 disposition
- * (#6084 D12) ships the return pair BASE TREE — `CORE_ROUTE_DIRS` carries
- * `[locale]/purchase`, and neither `GATEABLE_SURFACES` nor
- * `MODULE_SURFACES.commerce` gained an entry — so the `commerce` slice
- * contributes no rows at all and nothing else claims these two routes. The
- * issue's AC-1 requires the merged roster to carry them; with no module
- * claimant, the template's own roster is the only place that can declare
- * them, and doing so trips no collision.
- *
- * `/thanks/[slug]` is declared here for the same reason (#6646 D2): the
- * post-purchase thank-you route ships base tree and no module claims it.
- *
- * `/purchase-policy` is the service-shape purchase policy (#6646 D3) — its
- * cancellation and refunds sections replace the three #5947 policy rows.
- *
- * `/account` carries no `content`: it is a code route (the `(authed)` group),
- * like `/sign-in` on the base roster and like the API-backed rows the
- * scheduling module contributes. `/services/[slug]` declares its seed
- * DIRECTORY (`contentDir`, `content/en/Service`) — the three service pages.
+ * Where a starter's GENERATED roster record lives (spec 6892 D1) — the
+ * companion to {@link templateTreeDir}. A treeless alias (`ownTree: false`)
+ * has no directory of its own to hold one, so its record lives under
+ * `site-templates/aliases/` instead, keyed by its name; every other name's
+ * record lives beside its tree, as it always has.
  */
-const SIMPLE_SERVICE_ROSTER = [
-    { route: "/", content: ["content/en/HomePage/home.mdx"] },
-    { route: "/services", content: ["content/en/ServicesList/services.mdx"] },
-    { route: "/services/[slug]", contentDir: "content/en/Service" },
-    { route: "/about", content: ["content/en/AboutPage/about.mdx"] },
-    { route: "/contact", content: ["content/en/ContactPage/contact.mdx"] },
-    { route: "/faq", content: ["content/en/FAQPage/faq.mdx"] },
-    ...SHAPE_INDEPENDENT_ROWS,
-    {
-        route: "/purchase-policy",
-        content: ["content/en/PurchasePolicyPage/purchase-policy.mdx"],
-    },
-    { route: "/privacy", content: ["content/en/PrivacyPage/privacy.mdx"] },
-    { route: "/terms", content: ["content/en/TermsPage/terms.mdx"] },
-    { route: "/account" },
-    { route: "/purchase/success" },
-    { route: "/purchase/cancel" },
-    { route: "/thanks/[slug]" },
-];
+export function shippedManifestPath(name) {
+    const alias = ALIASES[name];
+    if (alias?.ownTree === false) {
+        return `aliases/${name}.TEMPLATE-MANIFEST.json`;
+    }
+    return `${templateTreeDir(name)}/TEMPLATE-MANIFEST.json`;
+}
 /**
- * The three settled templates and their fixed `requires` lists — settled by
- * Sam, 2026-09-14 (parent § D12). The plain name is the Pro one: it is the
- * flagship and the demo.
- *
- * `workspace` appears in none of them. It is a Pro module, but an authed app
- * surface contributing no PUBLIC page to a marketing site, and `requires`
- * names what the roster uses (parent § D15). A Pro key unlocks it regardless
- * of any template. `ModuleName` could express it either way — `workspace` is
- * one of the seven `RECOGNIZED_MODULES` names; it is simply not one any
- * template's fixed `requires` list names.
+ * Look up a declared template — the one exported function that yields a
+ * template's roster (#6753 AC-1); `TEMPLATE_MANIFESTS`, the frozen record it
+ * reads, holds only manifests composed from `ALIASES`.
  *
- * `commerce` is likewise in none of them: it is a per-site add-on available at
- * any level, so a template for it would contradict the offering model and
- * multiply the set combinatorially (parent § D13). It still contributes rows
- * to whichever template takes it, through `mergeRoster` below.
+ * With no `aliases`, returns the frozen `TEMPLATE_MANIFESTS` entry itself.
+ * With an injected alias table — the `resolveTemplateLineage` precedent
+ * (#5507) — composes `aliases[name]` against the shipped shape rosters, so a
+ * test exercises the composer's refusals without touching the shipped table.
  *
- * Frozen (#5507): this registry is also the issuer's authorization allowlist
- * (spec 5480 § C7) — a mutable global there could be monkey-patched at
- * runtime. A caller needing a different registry for a test injects its own
- * fixture rather than mutating this one.
+ * @throws TemplateError on an undeclared name, or a malformed injected alias.
  */
-export const TEMPLATE_MANIFESTS = Object.freeze({
-    /**
-     * The Free template, and the mechanism's own proof (parent § D11): it
-     * requires only `marketing`, so the keyless merge path is exercised by a
-     * template we ship anyway rather than by a throwaway fixture.
-     */
-    "marketing-site-free": {
-        name: "marketing-site-free",
-        requires: ["marketing"],
-        // The demo site carries the "Get started with this template" banner
-        // (operator ruling 2026-09-23); every other layout knob keeps its default.
-        layout: { announcementBanner: true },
-        categories: ["accounting", "legal", "technology"],
-        shape: "organization-product",
-        design: "standard",
-        extends: BASE_LAYER_DIR,
-        roster: [...TEMPLATE_BASE_ROSTER, FREE_BLOG_TEASER_ROW],
-    },
-    /**
-     * The Pro flagship. Its module list is OFFERINGS § 4 offering 3's tiers line
-     * — "docs, scheduling and flows modules" — where "flows" is
-     * `signal-collectors` (`MODULE_SURFACES` maps it to `["flows"]`).
-     */
-    "marketing-site": {
-        name: "marketing-site",
-        requires: ["marketing", "docs-blog", "scheduling", "signal-collectors"],
-        // The flagship is the general-purpose template: it carries the whole
-        // registry, so every group tile on the hub has at least one template.
-        categories: [
-            "accounting",
-            "legal",
-            "hvac",
-            "roofing",
-            "plumbing",
-            "electrical",
-            "landscaping",
-            "auto-repair",
-            "real-estate",
-            "technology",
-            "medical-specialty",
-        ],
-        shape: "organization-product",
-        design: "standard",
-        extends: BASE_LAYER_DIR,
-        roster: [...TEMPLATE_BASE_ROSTER, ...SIGNAL_COLLECTORS_SAMPLE_ROWS],
-    },
-    /**
-     * Pro Plus — the Pro list plus `multi-tenant`, which is correctly in the
-     * list because it DOES contribute pages (the org and workspace surfaces).
-     * Its `pageContributions` is nonetheless unset today, deferred to its own
-     * instance, so this template's merged roster carries the same contributed
-     * rows as `marketing-site`'s and no more. That is a module which has
-     * declared no rows yet — visible in the diff — not a merge that dropped
-     * declared rows.
-     */
-    "saas-product": {
-        name: "saas-product",
-        requires: [
-            "marketing",
-            "docs-blog",
-            "scheduling",
-            "signal-collectors",
-            "multi-tenant",
-        ],
-        categories: ["technology", "medical-specialty"],
-        shape: "organization-product",
-        design: "standard",
-        extends: BASE_LAYER_DIR,
-        roster: [...TEMPLATE_BASE_ROSTER, ...SIGNAL_COLLECTORS_SAMPLE_ROWS],
-    },
-    /**
-     * The second Pro template (#5589) — the reports-first, scroll-snap deck
-     * site. NOT `marketing-site` plus a module: its `requires` omits
-     * `docs-blog`, so the two Pro templates are siblings under `_base`
-     * (#5618 D2), never a lineage. Level still derives from `requires`:
-     * `scheduling` and `signal-collectors` are paid, so `templateDelivery`
-     * returns `"paid"` exactly as it does for `marketing-site`.
-     *
-     * It declares its OWN roster rather than reusing `TEMPLATE_BASE_ROSTER`
-     * (the only declared template that does): the deck home replaces the
-     * document-scroll home, and `/how-it-works`, the product page, `/pricing` and
-     * `/sign-in` are not pages this site has. The roster is what the
-     * template IS, so an unrostered page has neither a route directory
-     * (`rosterSurfaces`) nor its `_base`/overlay seed (#6646 D1).
-     *
-     * It declares NO `layout` block (#6638): the deck home, mark-only nav and
-     * centered footer are the `minimalism` design's, supplied by
-     * `DESIGN_LAYOUTS` from `design:` — the look any shape can wear. The
-     * roster rows the `organization-service` shape does not derive
-     * (`/reports`, `/referral`) are recorded with their reasons in this
-     * template's TEMPLATE-MANIFEST.md § 3a.
-     *
-     * `/reports` and `/referral` carry no `GATEABLE_SURFACES` entry and need
-     * none: both are single-segment `LandingPage` slugs served by the generic
-     * `[slug]` route (#5469 D2), the same mechanism Free's `/how-it-works`
-     * uses. `/reports/[slug]` (the reader) is the signal-collectors module's
-     * own contributed row.
-     *
-     * `/services/[slug]` declares its seed DIRECTORY as `contentDir`
-     * (`content/en/Service`, as `routes-map.ts` records it). The three
-     * samples ride the template tree unmapped, landing at that directory.
-     */
-    "minimalism-site": {
-        name: "minimalism-site",
-        requires: ["marketing", "scheduling", "signal-collectors"],
-        categories: ["real-estate", "technology", "legal"],
-        shape: "organization-service",
-        design: "minimalism",
-        extends: BASE_LAYER_DIR,
-        roster: MINIMALISM_ROSTER,
-    },
-    /**
-     * The T1 lawn-care template (#6087, Epic #5778) — the first site shape
-     * that composes `scheduling` and `commerce`: three priced services, a
-     * booker, a checkout return pair and the three #5947 policy pages.
-     *
-     * `requires` lists `marketing` for the registry convention every other
-     * manifest keeps: it is free (`module-tier.ts`'s `FREE_MODULES`), so it
-     * cannot change `templateDelivery`'s verdict, and listing it keeps the
-     * template's own declaration — not `DEFAULT_MODULES` — the authority for
-     * what a bare `--template simple-service` run installs. The order is
-     * `RECOGNIZED_MODULES` order, which is also `normalizeModules`' output
-     * order, so the declared list and the merge order read the same.
-     *
-     * `scheduling` and `commerce` are both paid, so `templateDelivery`
-     * returns `"paid"` from either one alone.
-     *
-     * It declares NO `layout` block: the default chrome (full nav, column
-     * footer, no announcement banner) is the one a lawn-care site wants, and
-     * the issue's STOP boundary excludes layout knobs the spec does not name.
-     */
-    "simple-service": {
-        name: "simple-service",
-        requires: ["marketing", "scheduling", "commerce"],
-        categories: ["landscaping"],
-        shape: "local-business-service",
-        design: "standard",
-        extends: BASE_LAYER_DIR,
-        roster: SIMPLE_SERVICE_ROSTER,
-    },
-});
-/** Look up a declared template. @throws TemplateError on an undeclared name. */
-export function resolveTemplate(name) {
-    const manifest = TEMPLATE_MANIFESTS[name];
-    if (!manifest) {
-        throw new TemplateError(`unknown template "${name}". Declared: ${Object.keys(TEMPLATE_MANIFESTS).join(", ")}`);
+export function resolveTemplate(name, aliases) {
+    const declared = aliases ?? TEMPLATE_MANIFESTS;
+    if (!Object.prototype.hasOwnProperty.call(declared, name)) {
+        throw new TemplateError(`unknown template "${name}". Declared: ${Object.keys(declared).join(", ")}`);
     }
-    return manifest;
+    return aliases
+        ? composeManifest(name, aliases[name])
+        : TEMPLATE_MANIFESTS[name];
 }
 /**
  * Resolve a template's `extends` chain — `[name, …ancestors, "_base"]` — in

package/dist/template-names.d.ts

@@ -20,22 +20,24 @@
  * ("Deliberately imports nothing from `parse-args.ts`: that module imports
  * THIS one … so a back-import would close a cycle"), and `surfaces.ts` is the
  * precedent this file follows: the flag's vocabulary lives in a module the
- * parser can import because it imports nothing at all.
+ * parser can import because it reaches nothing that imports the parser.
  *
- * THE REGISTRY IS STILL `template-manifest.ts` (parent record D2). This file
- * declares NAMES; that one declares what a template IS — `requires`, the
- * roster, the `installMap`, the free-vs-paid derivation — and it stays the
- * single place a template is defined. The two cannot drift: the names here
- * are asserted equal to `Object.keys(TEMPLATE_MANIFESTS)` by
- * `__tests__/template-scaffold.test.ts`, so adding a template without listing
- * it here (or the reverse) fails the suite rather than shipping a flag that
- * accepts a name the registry does not know.
+ * THE NAMES ARE DERIVED, NOT TYPED (#6753 D1). They are the key set of
+ * `ALIASES` in `starter-grid.ts` — the alias table `template-manifest.ts`
+ * composes every manifest from — so the flag's vocabulary and the registry
+ * cannot drift. `starter-grid.ts` is the one file this module imports, and it
+ * imports nothing at runtime (every import there is `import type`), so
+ * `parse-args.ts` → here → `starter-grid.ts` still reaches no module that
+ * imports `parse-args.ts` back. `ALIASES` does not live in
+ * `template-manifest.ts` for exactly that reason: importing it from there
+ * would re-open the cycle above.
  *
  * Rejected: lazifying `module-tier.ts`'s `PAID_MODULES` to break the cycle at
  * its source. It is the correct structural fix and it is not this unit's to
  * make — `module-tier.ts` is a READ row in spec 5481 § 4, and `PAID_MODULES`
  * is consumed as a plain array across the package.
  */
-/** The declared site templates, in `TEMPLATE_MANIFESTS` declaration order. */
-export declare const RECOGNIZED_TEMPLATES: readonly ["marketing-site-free", "marketing-site", "saas-product", "minimalism-site", "simple-service"];
-export type TemplateName = (typeof RECOGNIZED_TEMPLATES)[number];
+import { ALIASES } from "./starter-grid.js";
+export type TemplateName = keyof typeof ALIASES;
+/** The declared site templates, in `ALIASES` (and so `TEMPLATE_MANIFESTS`) declaration order. */
+export declare const RECOGNIZED_TEMPLATES: readonly TemplateName[];