create-ailk 0.8.0 → 0.9.0

package/dist/starter-grid.js

@@ -1,10 +1,13 @@
 /**
- * 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`.
+ * The two pages every starter carries whatever its shape (#6658 D5,
+ * `docs/decisions/starter-roster-page-set.md` D4/D7): a glossary and a
+ * newsletter signup. Each is a module-less `GATEABLE_SURFACES` entry the
+ * roster enables, with its seed in `_base`.
+ *
+ * The third — `/book-a-call` — was retired by #6897 D10: every scaffold's
+ * former `/book-a-call` link now points at `/meet/book-a-call`, served by
+ * `FREE_MEET_PLACEHOLDER_ROWS` below (a Free placeholder) or by the
+ * scheduling module's own live `/meet/[slug]` page.
  */
 const SHAPE_INDEPENDENT_ROWS = [
     { route: "/glossary", content: ["content/en/GlossaryList/glossary.mdx"] },
@@ -12,7 +15,37 @@ const SHAPE_INDEPENDENT_ROWS = [
         route: "/newsletter",
         content: ["content/en/NewsletterSignup/newsletter.mdx"],
     },
-    { route: "/book-a-call", content: ["content/en/BookCall/book-call.mdx"] },
+];
+/**
+ * The Free `/meet` placeholder pages (#6897 D5) — a meeting-types hub
+ * (`LandingPage`, served by the generic `[slug]` route) and its four
+ * `BookCall` detail seeds (served by the `[slug]/[detail]` route, D2). Both
+ * ship in the always-copied overlay, beside `FREE_BLOG_TEASER_ROW`, so a
+ * template-less scaffold's Contact tiles (which link `/meet/*` too) reach
+ * real pages. The second row uses an explicit `content` list, not
+ * `contentDir`, because only a `content`-list row is removed by
+ * `planRosterAppend`'s add-module supersede (F4's add-module half,
+ * `site-roster.ts`).
+ *
+ * Every alias that takes the `scheduling` module drops `"/meet"` and
+ * `"/meet/[slug]"` (D5) — otherwise `mergeRoster` refuses the duplicate
+ * route the module's own rows also contribute. The ROWS go; the SEEDS stay
+ * (#6942, operator 2026-09-28, partly reversing D5): until
+ * `SCHEDULING_CAL_LINK` is configured the module's pages hand off to the Free
+ * placeholder routes, which serve these seeds. `withMeetPlaceholderSeeds`
+ * (`site-roster.ts`) folds them onto the module's rows.
+ */
+const FREE_MEET_PLACEHOLDER_ROWS = [
+    { route: "/meet", content: ["content/en/LandingPage/meet.mdx"] },
+    {
+        route: "/meet/[slug]",
+        content: [
+            "content/en/BookCall/book-a-call.mdx",
+            "content/en/BookCall/onsite-estimate.mdx",
+            "content/en/BookCall/start-project.mdx",
+            "content/en/BookCall/onsite-service.mdx",
+        ],
+    },
 ];
 /**
  * The rows every `organization-product` template brings itself — one declared
@@ -26,17 +59,17 @@ const SHAPE_INDEPENDENT_ROWS = [
  *
  * Two layers, one roster:
  *
- *   - `/`, `/software/[slug]`, `/use-cases`, `/about`, `/faq`, `/contact` and
+ *   - `/`, `/software/[slug]`, `/for`, `/about`, `/faq`, `/contact` and
  *     `/purchase-policy` take their content from the overlay
  *     (`template-overlay/content/en/**`, copied whole into `templates/` by
  *     `build-templates.mjs`). `/features` is the FeaturesList hub over one
  *     Feature page per feature at `/features/[slug]` (#6721, reversing the
  *     single `/software/product` page of #6658 D3); both ride the `features`
  *     surface the roster enables.
- *     `/use-cases` lists the three UseCase pages at `/use-cases/[slug]`
+ *     `/for` lists the three UseCase pages at `/for/[slug]`
  *     (#6658 D4).
  *   - `/pricing`, `/privacy`, `/terms`, `/glossary`, `/newsletter`,
- *     `/book-a-call` and the three UseCase pages take their content from the
+ *     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
@@ -70,10 +103,11 @@ const TEMPLATE_BASE_ROSTER = [
     { route: "/features", content: ["content/en/FeaturesList/features.mdx"] },
     { route: "/features/[slug]", contentDir: "content/en/Feature" },
     {
-        route: "/use-cases",
-        content: ["content/en/UseCasesList/use-cases.mdx"],
+        // #6878 D7 — the persona hub, renamed from /use-cases.
+        route: "/for",
+        content: ["content/en/UseCasesList/for.mdx"],
     },
-    { route: "/use-cases/[slug]", contentDir: "content/en/UseCase" },
+    { route: "/for/[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"] },
@@ -128,7 +162,7 @@ const SIGNAL_COLLECTORS_SAMPLE_ROWS = [
  * 2026-09-25, reversing #6687's "Pro and up"): every shape roster below
  * carries them, and an alias sheds them only by an explicit `drop`. The seeds
  * live in the `_base` layer under `content/en/PortfolioItem/`; the detail
- * row's `contentDir` installs them (#6646 D1), exactly as `/use-cases/[slug]`
+ * row's `contentDir` installs them (#6646 D1), exactly as `/for/[slug]`
  * serves `content/en/UseCase`.
  */
 // NO_HAND_IMPLEMENT_OK: /build-starter operator-directed live pass (#6687).
@@ -148,12 +182,24 @@ const PORTFOLIO_ROWS = [
  */
 const REPORTS_ROW = {
     route: "/reports",
-    content: ["content/en/LandingPage/reports.mdx"],
+    content: ["content/en/ReportsList/reports.mdx"],
 };
 const REFERRAL_ROW = {
     route: "/referral",
     content: ["content/en/LandingPage/referral.mdx"],
 };
+/**
+ * The signal-collectors module's report/referral sample rows (spec 6892 D3):
+ * `/reports`, a `ReportsList` hub over the module's four `ReportPage` seeds,
+ * and `/referral`, a sample flow landing page. `marketing-site` and
+ * `saas-product` add these before `/portfolio`, alongside
+ * `SIGNAL_COLLECTORS_SAMPLE_ROWS`; `minimalism-site` keeps its own two
+ * `insert` groups instead (its pre-existing row order, D1).
+ */
+const SIGNAL_COLLECTORS_REPORT_ROWS = [
+    REPORTS_ROW,
+    REFERRAL_ROW,
+];
 /**
  * `organization-service`'s own rows (#6757 D1), derived from
  * `derive-roster.py --shape organization-service --primary-goal generate-leads
@@ -168,9 +214,19 @@ const ORGANIZATION_SERVICE_ROWS = [
     { route: "/about", content: ["content/en/AboutPage/about.mdx"] },
     { route: "/services", content: ["content/en/ServicesList/services.mdx"] },
     { route: "/services/[slug]", contentDir: "content/en/Service" },
+    // #6878 D7 — every shape carries the /for family now, service shapes
+    // included: the seeds are shape-neutral (D7), so no per-shape override is
+    // needed.
+    {
+        route: "/for",
+        content: ["content/en/UseCasesList/for.mdx"],
+    },
+    { route: "/for/[slug]", contentDir: "content/en/UseCase" },
     { route: "/contact", content: ["content/en/ContactPage/contact.mdx"] },
     { route: "/faq", content: ["content/en/FAQPage/faq.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"] },
     {
@@ -187,10 +243,18 @@ const LOCAL_BUSINESS_SERVICE_ROWS = [
     { route: "/", content: ["content/en/HomePage/home.mdx"] },
     { route: "/services", content: ["content/en/ServicesList/services.mdx"] },
     { route: "/services/[slug]", contentDir: "content/en/Service" },
+    // #6878 D7 — every shape carries the /for family now (D7 shape-neutral seeds).
+    {
+        route: "/for",
+        content: ["content/en/UseCasesList/for.mdx"],
+    },
+    { route: "/for/[slug]", contentDir: "content/en/UseCase" },
     { 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: "/sign-in" },
+    { route: "/sign-up" },
     {
         route: "/purchase-policy",
         content: ["content/en/PurchasePolicyPage/purchase-policy.mdx"],
@@ -214,10 +278,18 @@ const PERSON_SERVICE_ROWS = [
     { route: "/", content: ["content/en/HomePage/home.mdx"] },
     { route: "/services", content: ["content/en/ServicesList/services.mdx"] },
     { route: "/services/[slug]", contentDir: "content/en/Service" },
+    // #6878 D7 — every shape carries the /for family now (D7 shape-neutral seeds).
+    {
+        route: "/for",
+        content: ["content/en/UseCasesList/for.mdx"],
+    },
+    { route: "/for/[slug]", contentDir: "content/en/UseCase" },
     { 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: "/sign-in" },
+    { route: "/sign-up" },
     {
         route: "/purchase-policy",
         content: ["content/en/PurchasePolicyPage/purchase-policy.mdx"],
@@ -232,27 +304,33 @@ const PERSON_SERVICE_ROWS = [
  * `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.
+ * 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 const SHAPE_ROSTERS = Object.freeze({
     "organization-product": [
         ...TEMPLATE_BASE_ROSTER,
         FREE_BLOG_TEASER_ROW,
+        ...FREE_MEET_PLACEHOLDER_ROWS,
         ...PORTFOLIO_ROWS,
     ],
     "organization-service": [
         ...ORGANIZATION_SERVICE_ROWS,
         FREE_BLOG_TEASER_ROW,
+        ...FREE_MEET_PLACEHOLDER_ROWS,
         ...PORTFOLIO_ROWS,
     ],
     "local-business-service": [
         ...LOCAL_BUSINESS_SERVICE_ROWS,
         FREE_BLOG_TEASER_ROW,
+        ...FREE_MEET_PLACEHOLDER_ROWS,
         ...PORTFOLIO_ROWS,
     ],
     "person-service": [
         ...PERSON_SERVICE_ROWS,
         FREE_BLOG_TEASER_ROW,
+        ...FREE_MEET_PLACEHOLDER_ROWS,
         ...PORTFOLIO_ROWS,
     ],
 });
@@ -320,8 +398,8 @@ export const ALIASES = Object.freeze({
             "medical-specialty",
         ],
         differences: {
-            drop: ["/blog"],
-            add: SIGNAL_COLLECTORS_SAMPLE_ROWS,
+            drop: ["/blog", "/meet", "/meet/[slug]"],
+            add: [...SIGNAL_COLLECTORS_SAMPLE_ROWS, ...SIGNAL_COLLECTORS_REPORT_ROWS],
             before: "/portfolio",
         },
     },
@@ -346,8 +424,8 @@ export const ALIASES = Object.freeze({
         ],
         categories: ["technology", "medical-specialty"],
         differences: {
-            drop: ["/blog"],
-            add: SIGNAL_COLLECTORS_SAMPLE_ROWS,
+            drop: ["/blog", "/meet", "/meet/[slug]"],
+            add: [...SIGNAL_COLLECTORS_SAMPLE_ROWS, ...SIGNAL_COLLECTORS_REPORT_ROWS],
             before: "/portfolio",
         },
     },
@@ -367,17 +445,19 @@ export const ALIASES = Object.freeze({
      * (`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.
+     * 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` 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.
+     * `/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
@@ -386,8 +466,10 @@ export const ALIASES = Object.freeze({
      * 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) and the portfolio pair (the reports are the proof, not a
-     * portfolio), adds the signal-collectors samples, and INSERTS its two own
+     * 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.
      */
@@ -396,8 +478,22 @@ export const ALIASES = Object.freeze({
         design: "minimalism",
         modules: ["marketing", "scheduling", "signal-collectors"],
         categories: ["real-estate", "technology", "legal"],
+        // Spec 6892 D1 — this alias ships no `site-templates/minimalism-site/`
+        // tree of its own: it resolves purely from the grid. Its seed layer is
+        // its shape's tree (`templateTreeDir`), its deck home + SVGs are a
+        // sample the `minimalism` design installs (D4), and its `/reports` +
+        // `/referral` rows are signal-collectors module samples (D3).
+        ownTree: false,
         differences: {
-            drop: ["/blog", "/portfolio", "/portfolio/[slug]"],
+            drop: [
+                "/sign-in",
+                "/sign-up",
+                "/blog",
+                "/meet",
+                "/meet/[slug]",
+                "/portfolio",
+                "/portfolio/[slug]",
+            ],
             add: SIGNAL_COLLECTORS_SAMPLE_ROWS,
             insert: [
                 { before: "/about", rows: [REPORTS_ROW] },

package/dist/surfaces.d.ts

@@ -181,6 +181,33 @@ export declare const ROUTE_DEPENDENCIES: Readonly<Record<string, readonly string
 export declare const ROUTE_MESSAGE_NAMESPACES: Readonly<Record<string, readonly string[]>>;
 /** Template-relative path of the generated site-nav registry. */
 export declare const NAV_CONFIG_PATH = "apps/web/lib/nav-config.ts";
+/**
+ * Verify a rendered nav's self-hashing stamp (#6908 D1/F1–F2): `"valid"` when
+ * the first line's hash matches every byte after it, `"invalid"` when a
+ * stamp line is present but the hash fails (an edited, still-stamped nav),
+ * `"absent"` when there is no stamp line at all. A stamp that verifies proves
+ * the file unedited whatever generator wrote it — the check needs only the
+ * file, never the generator's code.
+ */
+export declare function readNavConfigStamp(text: string): "valid" | "invalid" | "absent";
+/**
+ * Every byte after a nav's stamp line, or `text` unchanged when it carries
+ * none. The one place the D1 stamp-line shape is matched outside
+ * `readNavConfigStamp` itself, so a test simulating an edit below the stamp
+ * (or a bare pre-D1 body) never re-derives `NAV_STAMP_RE`'s pattern by hand.
+ */
+export declare function stripNavConfigStamp(text: string): string;
+/** Options for `renderNavConfig` (#6878 D6). */
+export interface RenderNavConfigOptions {
+    /**
+     * Service page slugs — the basenames, minus `.mdx`, of a site's
+     * `content/en/Service/*.mdx` — for the Services flyout column on a
+     * service shape. Sorted, then cut to the first three. Absent/empty →
+     * the offering column emits no Services links even when the `services`
+     * surface is on (there is nothing to link yet).
+     */
+    serviceSlugs?: readonly string[];
+}
 /**
  * Render `apps/web/lib/nav-config.ts` for an enabled surface set.
  *
@@ -191,14 +218,19 @@ export declare const NAV_CONFIG_PATH = "apps/web/lib/nav-config.ts";
  * surface set for the same reason the route tree does.
  *
  * The base items are the Free marketing-site chrome (#5469 D5, the approved
- * chrome diff recorded on that card, re-pointed by #6658 D8):
- * a Product flyout in two columns (Features · Use Cases, #6721), then Blog,
- * Pricing and About. The feature and use-case links ride the `features` and
- * `use-cases` surfaces; `/blog` is always linked (the teaser or the docs-blog
- * module serves it). Pricing is gateable
- * surfaces: each item is emitted only when its surface is enabled (a template
- * roster enables it, #5469 D10), so the nav still never links a page the
- * scaffold does not carry.
+ * chrome diff recorded on that card, re-pointed by #6658 D8, then by #6878 D6):
+ * ONE flyout rule for every shape — an offering column (Features on product
+ * shapes, Services on service shapes) beside a Customers column linking the
+ * /for persona pages — then Blog, Pricing and About. `/blog` is always linked
+ * (the teaser or the docs-blog module serves it). Pricing and every other
+ * gateable surface: each item is emitted only when its surface is enabled (a
+ * template roster enables it, #5469 D10), so the nav still never links a page
+ * the scaffold does not carry. Portfolio is never a flyout link (D6): on a
+ * service shape it is a plain top-level link directly after the Services
+ * flyout, and every shape's footer Site pages column links it (#6895), both
+ * under the `portfolio` surface's gate. No empty flyout is ever emitted: with
+ * neither column non-empty, no flyout item is emitted at all (closes #6766's
+ * AC-1).
  *
  * Only gateable surfaces carrying a `navLabelKey` are linked after the base
  * items, because a nav entry needs a translated label. Emitting an entry whose
@@ -212,4 +244,4 @@ export declare const NAV_CONFIG_PATH = "apps/web/lib/nav-config.ts";
  * Deterministic: gateable entries follow GATEABLE_SURFACES order (alphabetical
  * by id), after the fixed base items.
  */
-export declare function renderNavConfig(enabled: string[]): string;
+export declare function renderNavConfig(enabled: string[], options?: RenderNavConfigOptions): string;