create-ailk 0.7.0 → 0.9.0

package/dist/template-manifest.d.ts

@@ -18,6 +18,7 @@ import type { CategorySlug } from "@working-theory/schema/categories";
 import { type PageRosterRow } from "./module-architecture.js";
 import type { ModuleName } from "./parse-args.js";
 import type { TemplateLayout } from "./site-chrome.js";
+import { type BuildableShape, type TemplateAlias } from "./starter-grid.js";
 /**
  * The closed **shape** enum (starter-template contract § The three axes,
  * operator-disposed 2026-09-24) — `<primary node>-<offering node>` in
@@ -30,21 +31,14 @@ export declare const STARTER_SHAPES: readonly ["organization-product", "organiza
 export type StarterShape = (typeof STARTER_SHAPES)[number];
 /**
  * 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 declare const STARTER_DESIGNS: readonly ["standard", "minimalism"];
 export type StarterDesign = (typeof STARTER_DESIGNS)[number];
-/**
- * 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 declare const DESIGN_LAYOUTS: Readonly<Record<StarterDesign, TemplateLayout>>;
 /**
  * One site template: its fixed module list and the page rows it brings itself.
  *
@@ -155,21 +149,10 @@ export declare class TemplateError extends Error {
     constructor(message: string);
 }
 /**
- * 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.
- *
- * `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.
+ * 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.
  *
  * Frozen (#5507): this registry is also the issuer's authorization allowlist
  * (spec 5480 § C7) — a mutable global there could be monkey-patched at
@@ -177,8 +160,61 @@ export declare class TemplateError extends Error {
  * fixture rather than mutating this one.
  */
 export declare const TEMPLATE_MANIFESTS: Readonly<Record<string, TemplateManifest>>;
-/** Look up a declared template. @throws TemplateError on an undeclared name. */
-export declare function resolveTemplate(name: string): TemplateManifest;
+/**
+ * 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).
+ */
+export declare const SHAPE_STARTERS: Readonly<Partial<Record<BuildableShape, TemplateManifest>>>;
+/**
+ * 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.
+ */
+export declare function templateTreeDir(name: string): string;
+/**
+ * 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.
+ *
+ * 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.
+ */
+export declare function isOwnTree(name: string): boolean;
+/**
+ * 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.
+ */
+export declare function shippedManifestPath(name: string): string;
+/**
+ * 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`.
+ *
+ * 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.
+ *
+ * @throws TemplateError on an undeclared name, or a malformed injected alias.
+ */
+export declare function resolveTemplate(name: string, aliases?: Readonly<Record<string, TemplateAlias>>): TemplateManifest;
 /**
  * Resolve a template's `extends` chain — `[name, …ancestors, "_base"]` — in
  * the client registry, before any fetch (#5618 D2). `_base` is the only