create-ailk 0.7.0 → 0.9.0

package/dist/surfaces.js

@@ -31,6 +31,7 @@
  * `MODULE_SURFACES`, and `__tests__/surface-gating.test.ts` asserts those keys
  * equal `RECOGNIZED_MODULES` so the two cannot drift.
  */
+import { createHash } from "node:crypto";
 /** Template-relative prefix every `apps/web` route directory sits under. */
 const ROUTE_ROOT = "apps/web/app/[locale]";
 /**
@@ -81,13 +82,6 @@ export const CORE_ROUTE_DIRS = [
     // scaffold carrying it and no content is byte-for-byte a scaffold with one
     // more 404, nothing else.
     `${ROUTE_ROOT}/[slug]`,
-    // #6658 D3 — the product's own detail page (`/software/product`, a
-    // SoftwareProduct → SoftwareApplication), which replaced the /features
-    // stand-in. Core for the same reason [slug] is: its content
-    // (`content/en/SoftwareProduct/product.mdx`) is in the always-copied overlay
-    // and the generated nav always links it, so every scaffold — template or
-    // not — must carry the route.
-    `${ROUTE_ROOT}/software`,
     // #6084 D12 (the operator's shape-2 disposition) — the checkout return
     // pair. The launchers pointing at them (`apps/mcp/src/tools/purchase.ts`,
     // `apps/web/.../dev/purchase/purchase.actions.ts`) are ALREADY
@@ -121,19 +115,22 @@ export const NON_ROUTE_DIRS = new Set([
  * byte-deterministic).
  */
 export const GATEABLE_SURFACES = [
+    {
+        // #6878 D9 — the comparison hub/spoke pair (`ComparisonsList` at
+        // /alternatives, `ComparisonPage` at /vs/<slug>). No `navLabelKey`: no
+        // roster names it by default, so it excludes at scaffold time exactly
+        // like any other gateable surface a roster leaves off. `add-page`
+        // installs it (D11) the first time a site adds a comparison.
+        id: "alternatives",
+        routes: [`${ROUTE_ROOT}/alternatives`, `${ROUTE_ROOT}/vs`],
+        content: ["content/<locale>/ComparisonsList", "content/<locale>/ComparisonPage"],
+    },
     {
         id: "blog",
         routes: [`${ROUTE_ROOT}/blog`],
         content: ["apps/web/content/<locale>/blog"],
         navLabelKey: "blog",
     },
-    {
-        // Module-less (#6658 D5), like `pricing`: every starter's roster names
-        // it. No `navLabelKey` — the footer links it, gated on this surface.
-        id: "book-a-call",
-        routes: [`${ROUTE_ROOT}/book-a-call`],
-        content: ["content/<locale>/BookCall"],
-    },
     {
         id: "careers",
         routes: [`${ROUTE_ROOT}/careers`],
@@ -180,12 +177,27 @@ export const GATEABLE_SURFACES = [
         routes: [`${ROUTE_ROOT}/events`],
         content: ["content/<locale>/EventsList", "content/<locale>/Event"],
     },
+    {
+        // #6721 — the product's feature pages: a FeaturesList hub over one
+        // Feature page per feature. The Free roster enables it by its rows.
+        id: "features",
+        routes: [`${ROUTE_ROOT}/features`],
+        content: ["content/<locale>/FeaturesList", "content/<locale>/Feature"],
+    },
     {
         // API-backed (the flow engine); no MDX of its own.
         id: "flows",
         routes: [`${ROUTE_ROOT}/flows`],
         content: [],
     },
+    {
+        // #6878 D3 — the persona hub, renamed from `use-cases` (route-naming
+        // convention #3450: /for/{persona} spokes under a /for hub). Every shape
+        // roster carries it now (D7), service shapes included.
+        id: "for",
+        routes: [`${ROUTE_ROOT}/for`],
+        content: ["content/<locale>/UseCasesList", "content/<locale>/UseCase"],
+    },
     {
         // Module-less (#6658 D5) — see `book-a-call`.
         id: "glossary",
@@ -240,6 +252,11 @@ export const GATEABLE_SURFACES = [
         routes: [`${ROUTE_ROOT}/partners`],
         content: ["content/<locale>/PartnersList", "content/<locale>/Partner"],
     },
+    {
+        id: "portfolio",
+        routes: [`${ROUTE_ROOT}/portfolio`],
+        content: ["content/<locale>/PortfolioList", "content/<locale>/PortfolioItem"],
+    },
     {
         // Module-LESS by construction (#5479 D16): no MODULE_SURFACES value names
         // it, so a site template may enable it by roster alone. Same for
@@ -276,6 +293,13 @@ export const GATEABLE_SURFACES = [
         routes: [`${ROUTE_ROOT}/services`],
         content: ["content/<locale>/ServicesList", "content/<locale>/Service"],
     },
+    {
+        // #6721 — the product's own page (#6658 D3), a gateable surface again now
+        // that the Free roster links /features instead of /software/product.
+        id: "software",
+        routes: [`${ROUTE_ROOT}/software`],
+        content: ["content/<locale>/SoftwareProduct"],
+    },
     {
         id: "tech-articles",
         routes: [`${ROUTE_ROOT}/tech-articles`],
@@ -291,11 +315,6 @@ export const GATEABLE_SURFACES = [
         routes: [`${ROUTE_ROOT}/testimonials`],
         content: ["content/<locale>/TestimonialsList"],
     },
-    {
-        id: "use-cases",
-        routes: [`${ROUTE_ROOT}/use-cases`],
-        content: ["content/<locale>/UseCasesList", "content/<locale>/UseCase"],
-    },
     {
         id: "whitepapers",
         routes: [`${ROUTE_ROOT}/whitepapers`],
@@ -311,6 +330,9 @@ export const RECOGNIZED_SURFACES = GATEABLE_SURFACES.map((s) => s.id);
  */
 export const SURFACE_ALIASES = {
     schedule: "meet",
+    // #6878 D3 — one-release alias for the /use-cases -> /for rename, same
+    // removal trigger as `schedule` above.
+    "use-cases": "for",
 };
 /**
  * Surface ids that became core routes (#6658 D3: `software` — the product's
@@ -319,7 +341,10 @@ export const SURFACE_ALIASES = {
  * so a site scaffolded with `--surfaces software` keeps working: its route
  * is copied regardless.
  */
-export const CORE_PROMOTED_SURFACES = new Set(["software"]);
+// #6721 — `software` is a gateable surface again (the Free roster now carries
+// /features + /features/[slug] instead); the set is kept, empty, so the
+// accept-and-drop read sites stay in place for the next promotion.
+export const CORE_PROMOTED_SURFACES = new Set([]);
 /** Canonical id for a `--surfaces` value, resolving a retired alias. */
 function canonicalizeSurface(s) {
     return SURFACE_ALIASES[s] ?? s;
@@ -492,10 +517,6 @@ export function excludedContentPaths(enabled) {
 export const ROUTE_SINCE = {
     about: "0.0.0",
     "blog/[[...slug]]": "0.0.0",
-    // #6658 — four genuinely new route directories (D4, D5), attaching at
-    // today's fixed-group version, the same "attach at today's version" rule
-    // #6084, #5977, #5678, #5479, #5371 and #5048 applied.
-    "book-a-call": "0.26.0",
     careers: "0.0.0",
     "careers/[slug]": "0.0.0",
     "case-studies": "0.0.0",
@@ -509,10 +530,17 @@ export const ROUTE_SINCE = {
     downloads: "0.0.0",
     events: "0.0.0",
     "events/[slug]": "0.0.0",
+    // #6721 — the feature pages, a new route pair at today's line.
+    features: "0.27.0",
+    "features/[slug]": "0.27.0",
     faq: "0.0.0",
     "flows/[slug]": "0.0.0",
     "flows/[slug]/results/[payload]": "0.14.0",
     "flows/[slug]/start": "0.18.0",
+    // #6658 — genuinely new route directories (D4, D5), attaching at today's
+    // fixed-group version, the same "attach at today's version" rule #6084,
+    // #5977, #5678, #5479, #5371 and #5048 applied. `book-a-call` was a third
+    // such entry, retired by #6897 D10.
     glossary: "0.26.0",
     "how-to": "0.0.0",
     "how-to/[slug]": "0.0.0",
@@ -531,6 +559,9 @@ export const ROUTE_SINCE = {
     // #5479 — three genuinely new route directories, so they attach at today's
     // fixed-group version rather than the "predates the manifest" 0.0.0 above,
     // the same rule #5048 ("projects/apply") and #5014 ("(authed)") applied.
+    // #6687 — the before/after portfolio, a new route pair at today's line.
+    portfolio: "0.27.0",
+    "portfolio/[slug]": "0.27.0",
     pricing: "0.22.0",
     privacy: "0.22.0",
     products: "0.0.0",
@@ -558,8 +589,14 @@ export const ROUTE_SINCE = {
     terms: "0.22.0",
     testimonials: "0.0.0",
     "thanks/[slug]": "0.14.0",
-    "use-cases": "0.0.0",
-    "use-cases/[slug]": "0.26.0",
+    // #6878 — the persona family, renamed from `use-cases`/`use-cases/[slug]`.
+    // Attaches at today's fixed-group version, the same "attach at today's
+    // version" rule #6084, #5977, #5678, #5479, #5371 and #5048 applied.
+    for: "0.28.0",
+    "for/[slug]": "0.28.0",
+    // #6878 D9 — the comparison hub/spoke pair.
+    alternatives: "0.28.0",
+    "vs/[slug]": "0.28.0",
     whitepapers: "0.0.0",
     "whitepapers/[slug]": "0.0.0",
     // #5014 — the (authed) route GROUP: layout.tsx + sign-in-gate.tsx sit
@@ -624,6 +661,10 @@ export const ROUTE_SINCE = {
     // directory, so it attaches at today's fixed-group version, the same rule
     // #5479, #5371 and #5048 applied.
     "[slug]": "0.23.0",
+    // #6897 D2 — the Free /meet/<slug> placeholder detail route. A genuinely
+    // new route directory, so it attaches at today's fixed-group version, the
+    // same rule applied above.
+    "[slug]/[detail]": "0.28.0",
 };
 /**
  * Surface id of the registry that owns `routeDir` (ROUTE_ROOT-relative): the
@@ -659,12 +700,18 @@ export function surfaceForRouteDir(routeDir) {
  */
 export const ROUTE_DEPENDENCIES = {
     // #5963 — the (auth) group's layout renders the brand mark through
-    // `siteLogo()`, and the LOCALE layout above it branches on
-    // `isAuthPath()` to drop the marketing chrome for these five paths: without
-    // `auth-routes.ts` a synced group renders inside the Nav + Footer it exists
-    // to replace. The sign-in page no longer imports `site-brand` — the mark is
-    // the shell's since #5963 — so its own list is just the env reader.
-    "(auth)": ["apps/web/lib/site-brand.tsx", "apps/web/lib/auth-routes.ts"],
+    // `siteLogo()` — which lives in `site-logo.tsx` since #6820 and reads the
+    // raw mark + name from `site-brand.tsx`, so BOTH files travel with the
+    // group — and the LOCALE layout above it branches on `isAuthPath()` to drop
+    // the marketing chrome for these five paths: without `auth-routes.ts` a
+    // synced group renders inside the Nav + Footer it exists to replace. The
+    // sign-in page no longer imports `site-brand` — the mark is the shell's
+    // since #5963 — so its own list is just the env reader.
+    "(auth)": [
+        "apps/web/lib/site-brand.tsx",
+        "apps/web/lib/site-logo.tsx",
+        "apps/web/lib/auth-routes.ts",
+    ],
     "(auth)/sign-in": ["apps/web/lib/auth-env.ts"],
     "(auth)/sign-up": ["apps/web/lib/auth-env.ts"],
     "(auth)/forgot-password": ["apps/web/lib/auth-env.ts"],
@@ -739,6 +786,46 @@ export const ROUTE_MESSAGE_NAMESPACES = {
 };
 /** Template-relative path of the generated site-nav registry. */
 export const NAV_CONFIG_PATH = "apps/web/lib/nav-config.ts";
+/**
+ * `renderNavConfig`'s first-line stamp (#6908 D1): `// ailk:generated
+ * sha256=<64 lowercase hex>`, recognised whether it ends in `\n` or `\r\n`.
+ * `<hex>` is the SHA-256 of every byte after the stamp line's terminator,
+ * CRLF folded to LF first — the same fold-and-hash rule `claude-md.ts`
+ * `hashBody` uses for the scaffold's `CLAUDE.md` regions (#6904), given its
+ * own definition here (N1) rather than an import, since the two files hash
+ * unrelated bodies.
+ */
+const NAV_STAMP_RE = /^\/\/ ailk:generated sha256=([0-9a-f]{64})\r?\n/;
+/** SHA-256, lowercase hex, of a nav body with every CRLF folded to LF (D1, N1). */
+function hashNavBody(body) {
+    return createHash("sha256")
+        .update(body.replace(/\r\n/g, "\n"), "utf8")
+        .digest("hex");
+}
+/**
+ * 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 function readNavConfigStamp(text) {
+    const match = NAV_STAMP_RE.exec(text);
+    if (match === null)
+        return "absent";
+    const body = text.slice(match[0].length);
+    return match[1] === hashNavBody(body) ? "valid" : "invalid";
+}
+/**
+ * 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 function stripNavConfigStamp(text) {
+    return text.replace(NAV_STAMP_RE, "");
+}
 /**
  * Render `apps/web/lib/nav-config.ts` for an enabled surface set.
  *
@@ -749,14 +836,19 @@ export 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 (Use cases · Features · FAQ), then Use cases, Blog, Pricing
- * and About. Features links the product's own page (`/software/product`), a
- * core route like `/faq` and `/about`; `/blog` is always linked (the teaser or
- * the docs-blog module serves it). Use cases and Pricing are 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
@@ -770,78 +862,155 @@ export 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 function renderNavConfig(enabled) {
+export function renderNavConfig(enabled, options) {
     const on = new Set(enabled);
     // `blog` is linked unconditionally below (operator ruling 2026-09-23), so
-    // it is excluded here; `use-cases` is the Free roster's own page (a
-    // module-less surface the roster enables, like `pricing`), linked in its
-    // fixed positions below rather than appended.
-    const linked = GATEABLE_SURFACES.filter((s) => s.navLabelKey !== undefined &&
-        on.has(s.id) &&
-        s.id !== "blog" &&
-        s.id !== "use-cases");
-    const useCases = on.has("use-cases");
+    // it is excluded here; `for` is the Customers flyout/footer column below,
+    // linked in its own fixed positions rather than appended.
+    const linked = GATEABLE_SURFACES.filter((s) => s.navLabelKey !== undefined && on.has(s.id) && s.id !== "blog");
+    const features = on.has("features");
+    const services = on.has("services");
+    const forEnabled = on.has("for");
+    const portfolio = on.has("portfolio");
+    const serviceSlugs = [...(options?.serviceSlugs ?? [])].sort().slice(0, 3);
+    // #6878 D6 (operator ruling 2026-09-27): one flyout rule for every shape.
+    // The `groups` render the desktop panel; `features` carries the same links
+    // for the mobile disclosure and the active-path match.
+    const featureLinks = features
+        ? [
+            '        { labelKey: "feature1", path: "/features/feature-1" },',
+            '        { labelKey: "feature2", path: "/features/feature-2" },',
+            '        { labelKey: "feature3", path: "/features/feature-3" },',
+        ]
+        : [];
+    const serviceLinks = !features && services
+        ? serviceSlugs.map((slug, i) => `        { labelKey: "service${i + 1}", path: "/services/${slug}" },`)
+        : [];
+    const customerLinks = forEnabled
+        ? [
+            '        { labelKey: "customer1", path: "/for/persona-1" },',
+            '        { labelKey: "customer2", path: "/for/persona-2" },',
+            '        { labelKey: "customer3", path: "/for/persona-3" },',
+        ]
+        : [];
+    const indent = (line) => `    ${line}`;
+    const group = (headingKey, links) => links.length === 0
+        ? []
+        : [
+            "        {",
+            `          headingKey: "${headingKey}",`,
+            "          items: [",
+            ...links.map(indent),
+            "          ],",
+            "        },",
+        ];
+    // Offering column: Features on a product shape, Services on a service
+    // shape. `features` wins when both surfaces are somehow on at once — the
+    // Free roster never enables both.
+    const offeringLinks = features ? featureLinks : serviceLinks;
+    const offeringLabelKey = features ? "product" : "services";
+    const offeringHeadingKey = features
+        ? "flyoutFeaturesHeading"
+        : "flyoutServicesHeading";
+    const flyoutGroups = [
+        ...group(offeringHeadingKey, offeringLinks),
+        ...group("flyoutCustomersHeading", customerLinks),
+    ];
+    // #6942 — the Services flyout's action bar links the /services hub. The
+    // hub rides the `services` surface's gate: its route directory serves both
+    // /services and /services/[slug], so every roster that enables the surface
+    // carries the hub. Emitted only inside a flyout that has a column (never
+    // an action-only flyout). A flyout action requires an icon
+    // (`NavFlyoutAction`), imported below only when this link is emitted.
+    const servicesHub = !features && services && flyoutGroups.length > 0;
     const entries = [
-        "  {",
-        '    labelKey: "product",',
-        "    flyout: {",
-        // SOFT_LOCK_OK: #6508 — width "panel" (D4/D5): a fixed 640px, two-column
-        // grid, replacing the "list"/"trigger" one-column menu. `presentation` is
-        // omitted — it defaults to "grid" (D5). The `docs` action is dropped (it
-        // duplicated the first feature's /how-it-works destination, § 1.4).
-        '      width: "panel",',
-        "      features: [",
-        ...(useCases
-            ? ['        { labelKey: "useCases", descKey: "useCasesDesc", icon: Layers, path: "/use-cases" },']
+        // No empty flyout (D6): emitted only when at least one column has links.
+        ...(flyoutGroups.length === 0
+            ? []
+            : [
+                "  {",
+                `    labelKey: "${offeringLabelKey}",`,
+                "    flyout: {",
+                // SOFT_LOCK_OK: #6508 — width "panel" (D4/D5): a fixed 640px panel.
+                '      width: "panel",',
+                "      features: [",
+                ...offeringLinks,
+                ...customerLinks,
+                "      ],",
+                "      groups: [",
+                ...flyoutGroups,
+                "      ],",
+                servicesHub
+                    ? '      actions: [{ labelKey: "services", icon: ArrowRight, path: "/services" }],'
+                    : "      actions: [],",
+                "    },",
+                "  },",
+            ]),
+        // #6895 (operator decision 2026-09-27): a service shape's header reads
+        // Services ▾ · Portfolio · Blog · About — Portfolio a plain top-level
+        // link, never a flyout link (D6), and the first item when no flyout is
+        // emitted. Product shapes keep their header.
+        ...(!features && services && portfolio
+            ? ['  { labelKey: "portfolio", path: "/portfolio" },']
             : []),
-        '        { labelKey: "features", descKey: "featuresDesc", icon: Sparkles, path: "/software/product" },',
-        '        { labelKey: "faq", descKey: "faqDesc", icon: HelpCircle, path: "/faq" },',
-        "      ],",
-        "      actions: [],",
-        "    },",
-        "  },",
-        // Operator ruling 2026-09-23: Product · Use cases · Blog · Pricing · About.
+        // Operator ruling 2026-09-25: [flyout ·] Blog · Pricing · About.
         // `/blog` is always linked — the `blog` surface serves the real route, and
         // with it off the `[slug]` route serves the overlay's module page.
-        ...(useCases ? ['  { labelKey: "useCases", path: "/use-cases" },'] : []),
         '  { labelKey: "blog", path: "/blog" },',
         ...(on.has("pricing") ? ['  { labelKey: "pricing", path: "/pricing" },'] : []),
         '  { labelKey: "about", path: "/about" },',
         ...linked.map((s) => `  { labelKey: "${s.navLabelKey}", path: "/${s.id}" },`),
     ];
-    // The footer's column groups (operator ruling 2026-09-23, replacing #6468's
-    // Product/Company pair): Site pages, Features, Resources. Pricing rides the
+    // The footer's column groups (operator rulings 2026-09-23 + 2026-09-25,
+    // #6878 D6). Site pages, Features, Customers, Resources. Pricing rides the
     // same `pricing` gate as the header item; `/blog` is always linked (above).
-    // The product links point at the product's own page, `/software/product`
-    // (#6658 D3): `software` is core, so they stay unconditional. Book a call,
-    // Glossary and Newsletter (#6658 D8) each ride their own surface's gate.
+    // The Features column links the three feature pages and the /features hub;
+    // the Customers column the three personas and the /for hub — each rides its
+    // surface's gate. Glossary and Newsletter (#6658 D8) each ride their own
+    // surface's gate. Book a call is always linked (#6897 D9), the same /blog
+    // precedent above: it retargets to /meet/book-a-call, served as a Free
+    // placeholder or the live scheduling page depending on what the site
+    // carries. No other footer column changes (D6) — there is deliberately no
+    // footer Services column.
     const footerEntries = [
         "  {",
         '    headingKey: "footerSitePagesHeading",',
         "    items: [",
-        '      { labelKey: "features", path: "/software/product" },',
+        ...(features ? ['      { labelKey: "features", path: "/features" },'] : []),
         ...(on.has("pricing")
             ? ['      { labelKey: "pricing", path: "/pricing" },']
             : []),
-        ...(useCases ? ['      { labelKey: "useCases", path: "/use-cases" },'] : []),
+        // #6895 — every shape's Site pages column links Portfolio, gated.
+        ...(portfolio
+            ? ['      { labelKey: "portfolio", path: "/portfolio" },']
+            : []),
         '      { labelKey: "about", path: "/about" },',
         '      { labelKey: "contact", path: "/contact" },',
-        ...(on.has("book-a-call")
-            ? ['      { labelKey: "bookACall", path: "/book-a-call" },']
-            : []),
-        "    ],",
-        "  },",
-        "  {",
-        '    headingKey: "footerFeaturesHeading",',
-        "    items: [",
-        '      { labelKey: "feature1", path: "/software/product" },',
-        '      { labelKey: "feature2", path: "/software/product" },',
-        '      { labelKey: "feature3", path: "/software/product" },',
-        '      { labelKey: "feature4", path: "/software/product" },',
-        '      { labelKey: "feature5", path: "/software/product" },',
-        '      { labelKey: "allFeatures", path: "/software/product" },',
+        '      { labelKey: "bookACall", path: "/meet/book-a-call" },',
         "    ],",
         "  },",
+        ...(features
+            ? [
+                "  {",
+                '    headingKey: "footerFeaturesHeading",',
+                "    items: [",
+                ...featureLinks.map((l) => l.slice(2)),
+                '      { labelKey: "allFeatures", path: "/features" },',
+                "    ],",
+                "  },",
+            ]
+            : []),
+        ...(forEnabled
+            ? [
+                "  {",
+                '    headingKey: "footerCustomersHeading",',
+                "    items: [",
+                ...customerLinks.map((l) => l.slice(2)),
+                '      { labelKey: "allCustomers", path: "/for" },',
+                "    ],",
+                "  },",
+            ]
+            : []),
         "  {",
         '    headingKey: "footerResourcesHeading",',
         "    items: [",
@@ -867,19 +1036,23 @@ export function renderNavConfig(enabled) {
         "from ",
         '"@working-theory/ui";',
     ].join("");
-    return `// nav-config.ts — site-nav registry.
+    const body = `// nav-config.ts — site-nav registry.
 //
 // GENERATED by create-ailk from the declared route surfaces. Every entry here
 // points at a route this site actually carries — the nav is regenerated with
 // the surface set so it can never link a page that was not scaffolded.
 //
+// The first line hashes the rest of this file: while it matches, \`create-ailk
+// add-module\` regenerates this nav when a module adds pages; once you edit
+// below it, the nav is yours and add-module reports the change it wanted
+// instead.
+//
 // Adding a link: scaffold the page (the \`add-page\` skill), then add an
 // entry below with a \`labelKey\` that exists in the \`nav\` namespace of
 // \`apps/web/messages/<locale>.json\`. Paths are locale-agnostic — Nav prefixes
 // them with the active locale at render.
 ${navItemImport}
-import { HelpCircle, Layers, Sparkles } from "lucide-react";
-
+${servicesHub ? 'import { ArrowRight } from "lucide-react";\n' : ""}
 export const navItems: NavItem[] = [
 ${entries.join("\n")}
 ];
@@ -895,4 +1068,7 @@ export const footerColumns: FooterColumnConfig[] = [
 ${footerEntries.join("\n")}
 ];
 `;
+    // D1 — a first-line stamp holding the SHA-256 of the rest of the file
+    // (`body`), so an unedited nav proves itself whatever generator wrote it.
+    return `// ailk:generated sha256=${hashNavBody(body)}\n${body}`;
 }