create-ailk 0.7.0 → 0.9.0

package/dist/starter-grid.d.ts

@@ -0,0 +1,232 @@
+/**
+ * The starter grid's data (#6753): the shape rosters and the alias table
+ * every `--template` name resolves through. A starter is one shape rendered
+ * in one design with a module list (starter-template contract § The three
+ * axes); an alias names those coordinates plus how its own rows differ from
+ * the shape's standard roster.
+ *
+ * DATA ONLY, AND IMPORT-FREE AT RUNTIME. Every import below is `import type`,
+ * erased at emit. `template-names.ts` derives `RECOGNIZED_TEMPLATES` from
+ * `ALIASES` and `parse-args.ts` imports that at runtime, so a runtime import
+ * here could reach `lib/module-tier.ts` and re-open the `RECOGNIZED_MODULES`
+ * temporal-dead-zone cycle `template-names.ts`'s header records (spec 6753
+ * D1). The composition itself — shape roster, minus `drop`, plus `add` —
+ * lives in `template-manifest.ts`, whose `resolveTemplate` is the one reader
+ * that yields a template's roster. Nothing but those two files imports this one.
+ */
+import type { CategorySlug } from "@working-theory/schema/categories";
+import type { ModuleName } from "./parse-args.js";
+import type { TemplateLayout } from "./site-chrome.js";
+import type { StarterDesign, StarterShape, TemplateRosterRow } from "./template-manifest.js";
+/** The shapes a starter can be built from — every StarterShape but the reserved one. */
+export type BuildableShape = Exclude<StarterShape, "local-business-product">;
+/** How an alias's own rows differ from its shape's standard roster. */
+export interface AliasDifferences {
+    /** Shape-roster routes this alias does not carry. */
+    readonly drop?: readonly string[];
+    /** Rows this alias carries that its shape roster does not. */
+    readonly add?: readonly TemplateRosterRow[];
+    /** The retained shape route `add` is inserted before; absent → appended. */
+    readonly before?: string;
+    /**
+     * Further positioned groups (#6757 D7): each group's rows go before its
+     * own `before` route, applied group by group in array order, AFTER `add`
+     * is placed. The one alias that needs more than one anchor
+     * (`minimalism-site`, which interleaves rows at two separate points in the
+     * shape's row order) uses this; every other alias leaves it unset.
+     */
+    readonly insert?: readonly {
+        readonly before: string;
+        readonly rows: readonly TemplateRosterRow[];
+    }[];
+}
+/**
+ * One `--template` name: the grid coordinates it stands for.
+ *
+ * No `tier`, `level`, `price` or optional-module member, for the reason
+ * `TemplateManifest` carries none (parent § D4, D12): the level is derived
+ * from `modules`, never declared, and the type is what makes declaring one a
+ * compile error.
+ */
+export interface TemplateAlias {
+    readonly shape: BuildableShape;
+    readonly design: StarterDesign;
+    /** Becomes the manifest's `requires`. */
+    readonly modules: readonly ModuleName[];
+    readonly categories: readonly CategorySlug[];
+    readonly layout?: TemplateLayout;
+    readonly differences?: AliasDifferences;
+    /**
+     * Whether this alias ships its own `site-templates/<name>/` tree (spec 6892
+     * D1). Absent means `true` — every alias but `minimalism-site` keeps its
+     * own directory. `false` declares that the alias resolves purely from the
+     * grid: its seed layer is its shape's tree (`templateTreeDir`), and its
+     * generated roster record lives under `site-templates/aliases/` rather
+     * than a directory of its own (`shippedManifestPath`).
+     */
+    readonly ownTree?: boolean;
+}
+/**
+ * Each buildable shape's standard roster (#6753 D3) — the rows an alias starts
+ * from before its `differences` apply.
+ *
+ * `organization-product` is today's base roster, the `/blog` teaser and the
+ * portfolio pair. `organization-service`, `local-business-service` (#6757)
+ * and `person-service` (#6758, roadmap § 6 Phase 2) are each their own rows,
+ * the `/blog` teaser and the portfolio pair. Every shape's own rows carry
+ * `/sign-in` and `/sign-up` (#6797): the locale layout's header links both on
+ * every shape, so the roster of record lists them as code routes.
+ */
+export declare const SHAPE_ROSTERS: Readonly<Record<BuildableShape, readonly TemplateRosterRow[]>>;
+/**
+ * The `--template` names and the grid coordinates each stands for (#6753) —
+ * the one table `TEMPLATE_MANIFESTS` and `RECOGNIZED_TEMPLATES` derive from,
+ * in the declaration order both keep. The plain name is the Pro one: it is
+ * the flagship and the demo (Sam, 2026-09-14, parent § D12).
+ *
+ * `workspace` appears in no module list. It is a Pro module, but an authed app
+ * surface contributing no PUBLIC page to a marketing site, and `modules` names
+ * what the roster uses (parent § D15). A Pro key unlocks it regardless of any
+ * template.
+ *
+ * `commerce` is a per-site add-on available at any level, so no alias exists
+ * FOR it (parent § D13); it still contributes rows to whichever alias takes
+ * it, through `mergeRoster`.
+ *
+ * Frozen (#5507): the registry composed from this table is also the issuer's
+ * authorization allowlist (spec 5480 § C7). A test needing a different table
+ * passes its own to `resolveTemplate(name, aliases)` rather than mutating
+ * this one.
+ */
+export declare const ALIASES: Readonly<{
+    /**
+     * 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. The bare
+     * `organization-product` shape — no differences at all.
+     */
+    readonly "marketing-site-free": {
+        readonly shape: "organization-product";
+        readonly design: "standard";
+        readonly modules: readonly ["marketing"];
+        readonly categories: readonly ["accounting", "legal", "technology"];
+        readonly layout: {
+            readonly announcementBanner: true;
+        };
+    };
+    /**
+     * 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"]`). It drops
+     * the shape's `/blog` teaser because docs-blog contributes the real `/blog`,
+     * and adds the signal-collectors sample rows ahead of the portfolio pair.
+     */
+    readonly "marketing-site": {
+        readonly shape: "organization-product";
+        readonly design: "standard";
+        readonly modules: readonly ["marketing", "docs-blog", "scheduling", "signal-collectors"];
+        readonly categories: readonly ["accounting", "legal", "consulting", "hvac", "roofing", "plumbing", "electrical", "landscaping", "auto-repair", "real-estate", "technology", "medical-specialty"];
+        readonly differences: {
+            readonly drop: readonly ["/blog", "/meet", "/meet/[slug]"];
+            readonly add: readonly import("./module-architecture.js").PageRosterRow[];
+            readonly before: "/portfolio";
+        };
+    };
+    /**
+     * 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.
+     */
+    readonly "saas-product": {
+        readonly shape: "organization-product";
+        readonly design: "standard";
+        readonly modules: readonly ["marketing", "docs-blog", "scheduling", "signal-collectors", "multi-tenant"];
+        readonly categories: readonly ["technology", "medical-specialty"];
+        readonly differences: {
+            readonly drop: readonly ["/blog", "/meet", "/meet/[slug]"];
+            readonly add: readonly import("./module-architecture.js").PageRosterRow[];
+            readonly before: "/portfolio";
+        };
+    };
+    /**
+     * The second Pro template (#5589) — the reports-first, scroll-snap deck
+     * site. NOT `marketing-site` plus a module: its `modules` omit `docs-blog`,
+     * so the two Pro templates are siblings under `_base` (#5618 D2), never a
+     * lineage. Level still derives from `modules`: `scheduling` and
+     * `signal-collectors` are paid, so `templateDelivery` returns `"paid"`
+     * exactly as it does for `marketing-site`.
+     *
+     * It composes the `organization-service` shape roster (#6757) rather than
+     * the organization-product one: 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 own `layout` (its
+     * `DESIGN.md`, resolved by `resolveDesign` off `design:` — #6813 D4) — the
+     * look any shape can wear. This alias ships no tree of its own (`ownTree:
+     * false`, spec 6892 D1); its GENERATED roster record (no narrative `.md`,
+     * D5) lives at `site-templates/aliases/minimalism-site.TEMPLATE-MANIFEST.json`.
+     *
+     * `/reports` (a `ReportsList` hub over `ReportPage`) and `/referral` (a
+     * flow landing page) are signal-collectors module samples (spec 6892 D3);
+     * neither carries a `GATEABLE_SURFACES` entry: `/referral` is a
+     * single-segment `LandingPage` slug served by the generic `[slug]` route
+     * (#5469 D2), the same mechanism Free's `/how-it-works` uses, and `/reports`
+     * is its own routes-map row. `/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.
+     *
+     * Since #6757, `organization-service` carries a real standard roster
+     * (D1), so this alias's `differences` is additions and drops only: it
+     * drops the `/blog` teaser (a Pro alias does not upsell its own level,
+     * D8), the portfolio pair (the reports are the proof, not a
+     * portfolio) and the two auth code routes the shape rosters (#6797 —
+     * this site has no `/sign-in`, above), adds the signal-collectors
+     * samples, and INSERTS its two own
+     * rows — `/reports` before `/about`, `/referral` before `/faq` (D7) — to
+     * reproduce its pre-#6757 row order (§ 1.2) exactly.
+     */
+    readonly "minimalism-site": {
+        readonly shape: "organization-service";
+        readonly design: "minimalism";
+        readonly modules: readonly ["marketing", "scheduling", "signal-collectors"];
+        readonly categories: readonly ["real-estate", "technology", "legal"];
+        readonly ownTree: false;
+        readonly differences: {
+            readonly drop: readonly ["/sign-in", "/sign-up", "/blog", "/meet", "/meet/[slug]", "/portfolio", "/portfolio/[slug]"];
+            readonly add: readonly import("./module-architecture.js").PageRosterRow[];
+            readonly insert: readonly [{
+                readonly before: "/about";
+                readonly rows: readonly [import("./module-architecture.js").PageRosterRow];
+            }, {
+                readonly before: "/faq";
+                readonly rows: readonly [import("./module-architecture.js").PageRosterRow];
+            }];
+        };
+    };
+}>;
+/**
+ * The coordinates a keyless `--shape S` builds (#6757 D5) — the composed
+ * FREE manifest per shape, for a shape with no `--template` alias of its
+ * own. Frozen and `Partial`; `organization-product` needs none — its
+ * keyless tree is `marketing-site-free`'s (#6754 AC-2).
+ *
+ * No `differences` (a bare shape is its standard roster, D1) and no
+ * `layout`. Every category is a leaf of `packages/schema/src/categories.ts`,
+ * as `TemplateManifest.categories` requires. `person-service`'s single
+ * `consulting` category is the operator's disposition (2026-09-26,
+ * ai-launch-kit-internal#6758): the leaf did not exist when #6758's spec was
+ * written, and adding it replaced that spec's `["accounting", "legal",
+ * "technology"]` author-pick stand-in.
+ */
+export declare const SHAPE_STARTER_ALIASES: Readonly<Partial<Record<BuildableShape, TemplateAlias>>>;