create-ailk 0.5.0 → 0.6.1

package/dist/surfaces.js

@@ -66,12 +66,32 @@ export const CORE_ROUTE_DIRS = [
     // copies all of apps/web verbatim, no `--surfaces` gating on this route),
     // so joining CORE_ROUTE_DIRS only makes the REGISTRY match what already
     // ships — it does not change what a fresh scaffold carries.
-    `${ROUTE_ROOT}/sign-in`,
+    //
+    // #5963 moved `sign-in` INTO the `(auth)` route group and added four
+    // siblings, so the group is what is listed now. It stays CORE rather than
+    // taking its own surface id the way `(authed)` did: `(authed)` is gated
+    // authed-app surface reported under its own identity, whereas these five
+    // are the public auth entry points that have always shipped ungated —
+    // registering the group keeps `sign-in`'s existing `core` identity exactly.
+    `${ROUTE_ROOT}/(auth)`,
     // #5469 D2 — always copied: it is what serves the Free template's
     // /how-it-works, /features and /blog pages, and it is inert for every slug
     // that has no LandingPage MDX (notFound), so a scaffold carrying it and no
     // content is byte-for-byte a scaffold with three more 404s, nothing else.
     `${ROUTE_ROOT}/[slug]`,
+    // #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
+    // unconditional base-tree code under D-64, so gating the return pages
+    // behind a scaffold-time surface would leave a licence-added commerce
+    // site with a working checkout and a 404 return page — the exact defect
+    // this issue exists to close. `CORE_ROUTE_DIRS` is the right home for the
+    // same reason `[slug]` immediately above is: inert (a request-time
+    // `notFound()`, `src/lib/commerce-claim.ts`) for every scaffold that never
+    // buys the `commerce` claim, so carrying it costs nothing beyond two more
+    // 404s. Neither `GATEABLE_SURFACES` nor `MODULE_SURFACES.commerce` gains
+    // an entry — the claim decides whether the pages serve, not the scaffold.
+    `${ROUTE_ROOT}/purchase`,
 ];
 /**
  * Directory names skipped by `listTemplateRouteDirs`'s walker even though they
@@ -482,6 +502,11 @@ export const ROUTE_SINCE = {
     // question set is the SITE's content. A scaffolded site adds its own route
     // beside this file and passes its own config.
     "projects/apply": "0.18.0",
+    // #6084 — two genuinely new route directories, attaching at today's
+    // fixed-group version, the same "attach at today's version" rule #5977,
+    // #5678, #5479, #5371 and #5048 applied.
+    "purchase/success": "0.24.0",
+    "purchase/cancel": "0.24.0",
     resources: "0.0.0",
     "resources/[slug]": "0.0.0",
     services: "0.0.0",
@@ -524,10 +549,36 @@ export const ROUTE_SINCE = {
     "(authed)/admin": "0.22.1",
     "(authed)/admin/site": "0.22.1",
     "(authed)/admin/team": "0.22.1",
+    // #5977 — the Pro content host's editor routes (spec 5872 FR1/FR2), added
+    // to apps/web by #5957. Genuinely new route directories, so they attach at
+    // today's fixed-group version, the same "attach at today's version" rule
+    // #5678, #5479, #5371 and #5048 applied.
+    //
+    // They are registered here but do NOT ship in a scaffold: the pair is
+    // excluded from the template snapshot by `EXCLUDE_TEMPLATE_DIRS` in
+    // `scripts/build-templates.mjs` (see that entry for the two spec-5872-D11
+    // constraints behind the choice). The entries are kept because ROUTE_SINCE
+    // is the route registry for `apps/web`, not a mirror of what the snapshot
+    // happens to carry — sync-routes' AC-5 coverage test knows the exclusion
+    // and treats the absence as justified.
+    "(authed)/edit": "0.24.0",
+    "(authed)/edit/[type]/[slug]": "0.24.0",
     "(authed)/waitlist": "0.18.0",
     "(authed)/waitlist/[experimentId]": "0.18.0",
     "(authed)/waitlist/[experimentId]/signups/[leadId]": "0.18.0",
-    "sign-in": "0.18.0",
+    // #5963 — the `(auth)` route group. `sign-in` keeps its ORIGINAL version
+    // under its new key: ROUTE_SINCE tracks when a route was introduced, not
+    // when it was moved, exactly as the #5637 workspace -> admin rename above
+    // left `(authed)/admin` at 0.22.1. The group's own layout and the four new
+    // pages are genuinely new route directories, so they attach at today's
+    // fixed-group version — the same rule #5977, #5678, #5479, #5371 and #5048
+    // applied.
+    "(auth)": "0.24.0",
+    "(auth)/sign-in": "0.18.0",
+    "(auth)/sign-up": "0.24.0",
+    "(auth)/forgot-password": "0.24.0",
+    "(auth)/reset-password": "0.24.0",
+    "(auth)/verify-email": "0.24.0",
     // #5469 D2 — the generic `[slug]` content route. A genuinely new route
     // directory, so it attaches at today's fixed-group version, the same rule
     // #5479, #5371 and #5048 applied.
@@ -566,7 +617,17 @@ export function surfaceForRouteDir(routeDir) {
  * that the waitlist dashboard also uses, rather than duplicating them.
  */
 export const ROUTE_DEPENDENCIES = {
-    "sign-in": ["apps/web/lib/auth-env.ts", "apps/web/lib/site-brand.tsx"],
+    // #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"],
+    "(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"],
+    "(auth)/reset-password": ["apps/web/lib/auth-env.ts"],
     "(authed)": ["apps/web/auth.ts", "apps/web/lib/auth-env.ts"],
     "(authed)/account": [
         "apps/web/lib/account-config.ts",
@@ -574,11 +635,37 @@ export const ROUTE_DEPENDENCIES = {
         `${ROUTE_ROOT}/(authed)/waitlist/components/ForbiddenState.tsx`,
         `${ROUTE_ROOT}/(authed)/waitlist/format.ts`,
     ],
-    "(authed)/admin": ["apps/web/lib/server-api.ts"],
+    "(authed)/admin": [
+        "apps/web/lib/server-api.ts",
+        `${ROUTE_ROOT}/(authed)/waitlist/components/ForbiddenState.tsx`,
+    ],
     "(authed)/leads": ["apps/web/lib/server-api.ts"],
-    "(authed)/admin/site": ["apps/web/lib/server-api.ts"],
-    "(authed)/admin/team": ["apps/web/lib/server-api.ts"],
+    // #5977 — the editor routes' own imports, read from their sources: both
+    // pages call `forwardedCookieInit`/`unwrapApiResult` from `lib/server-api`
+    // and render the shared `ForbiddenState` on the tenant guard's 403, the
+    // same pair `(authed)/admin` already declares. Declared for registry
+    // completeness; inert in practice while the routes are excluded from the
+    // snapshot (see ROUTE_SINCE above).
+    "(authed)/edit": [
+        "apps/web/lib/server-api.ts",
+        `${ROUTE_ROOT}/(authed)/waitlist/components/ForbiddenState.tsx`,
+    ],
+    "(authed)/edit/[type]/[slug]": [
+        "apps/web/lib/server-api.ts",
+        `${ROUTE_ROOT}/(authed)/waitlist/components/ForbiddenState.tsx`,
+    ],
+    "(authed)/admin/site": [
+        "apps/web/lib/server-api.ts",
+        `${ROUTE_ROOT}/(authed)/waitlist/components/ForbiddenState.tsx`,
+    ],
+    "(authed)/admin/team": [
+        "apps/web/lib/server-api.ts",
+        `${ROUTE_ROOT}/(authed)/waitlist/components/ForbiddenState.tsx`,
+    ],
     "(authed)/waitlist": ["apps/web/lib/server-api.ts"],
+    // #6183 S9b D5 — both /meet pages call the shared enabled-slug read.
+    meet: ["apps/web/lib/meeting-slugs.ts"],
+    "meet/[slug]": ["apps/web/lib/meeting-slugs.ts"],
 };
 /**
  * i18n message namespaces (dot-path into `apps/web/messages/<locale>.json`) a
@@ -590,10 +677,21 @@ export const ROUTE_DEPENDENCIES = {
  * to the site owner, same as any other reported gap.
  */
 export const ROUTE_MESSAGE_NAMESPACES = {
-    "sign-in": ["signIn"],
+    // #5963 — `signIn` is untouched and still the sign-in page's namespace; the
+    // group's layout and the four new pages read the new `auth` namespace.
+    "(auth)": ["auth"],
+    "(auth)/sign-in": ["signIn"],
+    "(auth)/sign-up": ["auth"],
+    "(auth)/forgot-password": ["auth"],
+    "(auth)/reset-password": ["auth"],
+    "(auth)/verify-email": ["auth"],
     "(authed)/account": ["account"],
     "(authed)/admin": ["admin"],
     "(authed)/leads": ["leadsInbox"],
+    // #5977 — every string on both editor routes comes from the `edit`
+    // namespace (spec 5872 D10).
+    "(authed)/edit": ["edit"],
+    "(authed)/edit/[type]/[slug]": ["edit"],
     "(authed)/admin/site": ["admin"],
     "(authed)/admin/team": ["admin"],
     "(authed)/waitlist": ["waitlistDashboard.gate"],

package/dist/template-manifest.d.ts

@@ -1,3 +1,20 @@
+/**
+ * Site-template registry, and the roster merge that composes a template with
+ * the modules it takes (spec 5478, unit A of the site-templates mechanism;
+ * design record docs/specs/5462-site-templates-module-bundles-spec.md).
+ *
+ * A site template is DATA AND CONTENT, NOT CODE: a page roster, seed content
+ * and config — never a `page.tsx` (parent § D16). This file declares what a
+ * template IS. It declares no delivery channel, reads no licence, and touches
+ * no disk: the `--template` flag, the bundle fetch and the landing order are
+ * #5481's, and `GET /v1/templates/:name/:version` is #5480's.
+ *
+ * A CODE registry, not per-template JSON (parent § D2): in TypeScript,
+ * `requires` is checked against `RECOGNIZED_MODULES` at compile time, and this
+ * package already twice records that a fixed template FILE is the drift a
+ * registry removes.
+ */
+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";
@@ -24,6 +41,22 @@ export interface TemplateManifest {
      * unrecognized name fails type-check rather than a runtime validation.
      */
     requires: readonly ModuleName[];
+    /**
+     * The business categories this template is FOR — one or more LEAF slugs from
+     * the site-category registry (`@working-theory/schema/categories`, #5830),
+     * shared with content's frontmatter `categories`. Required, and typed against
+     * `CategorySlug`, for the same reason `requires` is typed against
+     * `ModuleName`: an unrecognized name fails type-check rather than a runtime
+     * validation, and every template must be findable under at least one
+     * category on the hub's "Browse by business" band.
+     *
+     * LEAVES ONLY. A group slug (`professional-services`, `home-and-trades`, …)
+     * is never a valid value: the group is DERIVED through `groupOf`, so a
+     * template that fits "professional services" names `accounting` and `legal`.
+     * Where a leaf is genuinely missing, the operator adds a leaf to the
+     * registry — never a group here.
+     */
+    categories: readonly CategorySlug[];
     /**
      * The template this one EXTENDS — its lineage, never its level (#5618 D2).
      * A single parent, not a list: "later layers win file by file" needs a

package/dist/template-manifest.js

@@ -1,19 +1,3 @@
-/**
- * Site-template registry, and the roster merge that composes a template with
- * the modules it takes (spec 5478, unit A of the site-templates mechanism;
- * design record docs/specs/5462-site-templates-module-bundles-spec.md).
- *
- * A site template is DATA AND CONTENT, NOT CODE: a page roster, seed content
- * and config — never a `page.tsx` (parent § D16). This file declares what a
- * template IS. It declares no delivery channel, reads no licence, and touches
- * no disk: the `--template` flag, the bundle fetch and the landing order are
- * #5481's, and `GET /v1/templates/:name/:version` is #5480's.
- *
- * A CODE registry, not per-template JSON (parent § D2): in TypeScript,
- * `requires` is checked against `RECOGNIZED_MODULES` at compile time, and this
- * package already twice records that a fixed template FILE is the drift a
- * registry removes.
- */
 import { classifyModules } from "./lib/module-tier.js";
 import { MODULE_SLICES, normalizeModules, } from "./module-architecture.js";
 /**
@@ -125,6 +109,60 @@ const MINIMALISM_ROSTER = [
     { route: "/privacy", content: ["content/en/PrivacyPage/privacy.mdx"] },
     { route: "/terms", content: ["content/en/TermsPage/terms.mdx"] },
 ];
+/**
+ * `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`, `/features` and `/pricing` are absent —
+ * `/pricing`'s `_base` seed still lands on disk, it simply has no rostered
+ * route, exactly as it does 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.
+ *
+ * `/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]` likewise declares none —
+ * its seed is a whole DIRECTORY (`content/en/Service`), and a roster row's
+ * `content` names files the manifest generator reads frontmatter from.
+ */
+const SIMPLE_SERVICE_ROSTER = [
+    { route: "/", content: ["content/en/HomePage/home.mdx"] },
+    { route: "/services", content: ["content/en/ServicesList/services.mdx"] },
+    { route: "/services/[slug]" },
+    { route: "/about", content: ["content/en/AboutPage/about.mdx"] },
+    { route: "/contact", content: ["content/en/ContactPage/contact.mdx"] },
+    { route: "/faq", content: ["content/en/FAQPage/faq.mdx"] },
+    { route: "/returns", content: ["content/en/ReturnsPolicyPage/returns.mdx"] },
+    {
+        route: "/cancellation",
+        content: ["content/en/CancellationPolicyPage/cancellation.mdx"],
+    },
+    {
+        route: "/shipping",
+        content: ["content/en/ShippingPolicyPage/shipping.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" },
+];
 /**
  * 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
@@ -156,6 +194,7 @@ export const TEMPLATE_MANIFESTS = Object.freeze({
     "marketing-site-free": {
         name: "marketing-site-free",
         requires: ["marketing"],
+        categories: ["accounting", "legal", "technology"],
         extends: BASE_LAYER_DIR,
         roster: [...TEMPLATE_BASE_ROSTER, FREE_BLOG_TEASER_ROW],
     },
@@ -167,6 +206,21 @@ export const TEMPLATE_MANIFESTS = Object.freeze({
     "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",
+        ],
         extends: BASE_LAYER_DIR,
         roster: TEMPLATE_BASE_ROSTER,
     },
@@ -188,6 +242,7 @@ export const TEMPLATE_MANIFESTS = Object.freeze({
             "signal-collectors",
             "multi-tenant",
         ],
+        categories: ["technology", "medical-specialty"],
         extends: BASE_LAYER_DIR,
         roster: TEMPLATE_BASE_ROSTER,
     },
@@ -222,6 +277,7 @@ export const TEMPLATE_MANIFESTS = Object.freeze({
     "minimalism-site": {
         name: "minimalism-site",
         requires: ["marketing", "scheduling", "signal-collectors"],
+        categories: ["real-estate", "technology", "legal"],
         extends: BASE_LAYER_DIR,
         roster: MINIMALISM_ROSTER,
         layout: {
@@ -231,6 +287,33 @@ export const TEMPLATE_MANIFESTS = Object.freeze({
             home: "deck",
         },
     },
+    /**
+     * 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 marketing-site chrome 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"],
+        extends: BASE_LAYER_DIR,
+        roster: SIMPLE_SERVICE_ROSTER,
+    },
 });
 /** Look up a declared template. @throws TemplateError on an undeclared name. */
 export function resolveTemplate(name) {

package/dist/template-names.d.ts

@@ -37,5 +37,5 @@
  * 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"];
+export declare const RECOGNIZED_TEMPLATES: readonly ["marketing-site-free", "marketing-site", "saas-product", "minimalism-site", "simple-service"];
 export type TemplateName = (typeof RECOGNIZED_TEMPLATES)[number];

package/dist/template-names.js

@@ -42,4 +42,5 @@ export const RECOGNIZED_TEMPLATES = [
     "marketing-site",
     "saas-product",
     "minimalism-site",
+    "simple-service",
 ];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-ailk",
-  "version": "0.5.0",
+  "version": "0.6.1",
   "description": "Scaffolder for AI Launch Kit — `pnpm create ailk@latest <dir>` produces a starter repo consuming @working-theory/* from npm (per ADR 0007).",
   "type": "module",
   "main": "./dist/index.js",
@@ -25,7 +25,8 @@
     "tar": "^7.5.21"
   },
   "devDependencies": {
-    "@working-theory/templates": "0.24.0"
+    "@working-theory/schema": "0.26.0",
+    "@working-theory/templates": "0.26.0"
   },
   "repository": {
     "type": "git",

package/site-templates/marketing-site/DESIGN.md

@@ -0,0 +1,148 @@
+---
+name: Marketing site (Pro) — marketing-site
+description: The Pro flagship: the Standard marketing pages plus blog, docs, booking and signal-collector pages, on the base foundation.
+colors:
+  bg: "#ffffff"
+  fg: "#000000"
+  surface: "#ffffff"
+  surface-secondary: "#ffffff"
+  border: "#000000"
+  text-muted: "#333333"
+  brand: "#000000"
+  fg-on-brand: "#ffffff"
+  accent: "#000000"
+  bg-dark: "#000000"
+  fg-dark: "#ffffff"
+  border-dark: "#ffffff"
+  brand-dark: "#ffffff"
+typography:
+  display:
+    fontFamily: "system-ui, -apple-system, Segoe UI, Roboto, Helvetica Neue, sans-serif"
+    fontSize: "6rem"
+    fontWeight: 400
+    lineHeight: 1
+    letterSpacing: "-0.05em"
+  heading-section:
+    fontFamily: "system-ui, -apple-system, Segoe UI, Roboto, Helvetica Neue, sans-serif"
+    fontSize: "2.25rem"
+    fontWeight: 400
+    lineHeight: 1.25
+    letterSpacing: "-0.05em"
+  heading-item:
+    fontSize: "1.25rem"
+    fontWeight: 600
+    lineHeight: 1.375
+  body:
+    fontFamily: "system-ui, -apple-system, Segoe UI, Roboto, Helvetica Neue, sans-serif"
+    fontSize: "1.125rem"
+    fontWeight: 400
+    lineHeight: 1.5
+  eyebrow:
+    fontSize: "0.875rem"
+    fontWeight: 600
+    lineHeight: 1.4
+    letterSpacing: "0.05em"
+rounded:
+  button: "0.25rem"
+  card: "0.75rem"
+spacing:
+  section: "4rem"
+  card: "1.5rem"
+  grid: "1.5rem"
+  container: "1280px"
+---
+
+<!--
+  Source template: marketing-site
+  Version: create-ailk {{CREATE_AILK_VERSION}}
+  Extends: _base — installing this template replaces the base scaffold's
+  DESIGN.md with this file. Its tokens are the base foundation's, unchanged:
+  this template carries no theme of its own.
+
+  The tokens above describe what the site RENDERS today. Colours come from
+  content/_site.mdx (`theme.colors`); type, radius and spacing are platform
+  defaults a site cannot override yet — see "Where this is heading" below.
+-->
+
+# Marketing site (Pro)
+
+## Overview
+
+The Pro flagship template. It carries the same nine-beat home and marketing pages as Standard (Free), and adds the pages its four Pro modules bring: the blog, the docs, the booking pages under `/meet`, and the signal-collector surfaces. It runs on the base foundation unchanged.
+
+## Colors
+
+### Primary
+
+**Black** (`brand` `#000000`) fills the primary button; its label is white. The secondary button is white with a black hairline and black label.
+
+### Neutral
+
+Pure white ground (`bg` `#ffffff`), pure black ink for headings (`fg` `#000000`), and near-black `#333333` for body copy — well above AA on white. **Borders are black** (`#000000`): card outlines, the rule under the navigation, the rules between sections and the rule above the footer are all 1px black lines. Cards are white, not tinted (`surface-secondary` is white too). There is no accent colour — `accent` is black.
+
+Dark mode inverts: black ground, white ink, white rules, white primary button with black label.
+
+### Named Rules
+
+- **Rules, not fills.** A container is drawn with a black hairline on the white ground. Grey fills are reserved for image placeholders.
+
+## Typography
+
+System sans throughout; no web font.
+
+### Hierarchy
+
+| Role            | Size     | Weight | Notes                                                                       |
+| --------------- | -------- | ------ | --------------------------------------------------------------------------- |
+| Hero headline   | 6rem     | 400    | Tracking -0.05em, line-height 1                                             |
+| Section heading | 2.25rem  | 400    | Tracking -0.05em — light and tight, not bold                                |
+| Item heading    | 1.25rem  | 600    | Card, feature and step titles                                               |
+| Body            | 1.125rem | 400    | `#333333`, line-height 1.5                                                  |
+| Section label   | 0.875rem | 600    | Uppercase, +0.05em tracking today — the small label above a section heading |
+
+Measured from the rendered scaffold (1440px wide), not transcribed from tokens.
+
+The small label above a section heading is **kept** as part of this foundation's voice (operator-disposed 2026-09-22) and is headed toward the treatment below.
+
+## Layout
+
+Full navigation with the announcement banner; a multi-column footer; the default home. Every page and its sections are listed in `TEMPLATE-MANIFEST.md` in this directory. Shared foundation: a 1280px container, sections at 4rem, card grids at 1.5rem, breakpoints 320 / 768 / 1024 / 1440.
+
+## Shapes
+
+Two radii today: buttons at 0.25rem, cards and outlined boxes at 0.75rem. Headed toward square corners — see below.
+
+## Components
+
+### Buttons
+
+Primary: black fill, white label, 0.25rem corners. Secondary: transparent with a black 1px outline and black label. Both are the library `Button`.
+
+### Cards / Containers
+
+White panels with a black 1px outline, 0.75rem corners, `card` (1.5rem) padding. The one exception today: the "how it works" steps render as dark filled cards (see below).
+
+### Navigation
+
+Full navigation: wordmark left, page links, an outlined and a filled button at the far right, the announcement banner above. A black hairline separates it from the page.
+
+## Where this is heading
+
+The foundation's pinned direction is the pacing of a classic wireframe marketing kit — `standardissue.webflow.io` is the reference for rhythm, type scale, spacing density and section pacing only; no image, copy or code is taken from it. Six parts of that direction cannot be expressed through a site's theme today, so they wait on a platform change rather than being hand-coded. Until they land, this file describes the rendered site above, not these targets.
+
+| Target                                            | Reference value                                                                                                                  | Blocked by                                                                                               |
+| ------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
+| Square corners on buttons, cards and inputs       | radius 0                                                                                                                         | A site's `theme:` block accepts colours only — no radius                                                 |
+| Bold, tighter headings                            | hero ~3.6rem and section headings ~2.9rem, both at weight 700 with tracking about -0.02em (today 6rem and 2.25rem at weight 400) | No per-site type-role override                                                                           |
+| Generous section pacing                           | about 10rem between sections, not 4rem                                                                                           | No per-site section-spacing override; `spacious` (6rem) is not author-selectable                         |
+| Section label in sentence case, bold, no tracking | "Core Features", not "CORE FEATURES"                                                                                             | The eyebrow role bakes in uppercase and tracking                                                         |
+| Whitespace between sections, not rules            | no rule between bands                                                                                                            | Section dividers share the one `border` colour with card outlines, so black outlines make black dividers |
+| Outlined steps in "how it works"                  | three plain outlined columns                                                                                                     | The steps section renders dark filled cards; no outlined variant                                         |
+
+## Do's and Don'ts
+
+- **Do** keep every page built from registered sections. If a section you need does not exist, request it rather than writing one-off markup.
+- **Do** change colours in `content/_site.mdx` `theme.colors`; they reach every section.
+- **Don't** add a colour accent. The foundation's one idea is black on white; a brand pass adds colour deliberately, through the theme.
+- **Don't** replace a black rule with a shadow or a grey fill.
+- **Don't** hard-code the "heading toward" values above into a page. They arrive through the platform, or not at all.

package/site-templates/marketing-site/TEMPLATE-MANIFEST.json

@@ -1,8 +1,20 @@
 {
   "template": "marketing-site",
   "requires": ["marketing", "docs-blog", "scheduling", "signal-collectors"],
-  "createAilkVersion": "0.5.0",
-  "generatedHash": "0d7192a6f912c43e2ae3d51dae5878a72cf01f50dd206e341b0c59cf46dbd40c",
+  "categories": [
+    "accounting",
+    "legal",
+    "hvac",
+    "roofing",
+    "plumbing",
+    "electrical",
+    "landscaping",
+    "auto-repair",
+    "real-estate",
+    "technology",
+    "medical-specialty"
+  ],
+  "generatedHash": "7ac1901833c4607d7b1a5f7f8531d18618ecdc4a3e810480635d3d6b5eb3be83",
   "layout": {
     "nav": "full",
     "footer": "columns",
@@ -295,6 +307,14 @@
       "chrome": "on",
       "sections": []
     },
+    {
+      "route": "/appointments",
+      "pageType": null,
+      "schema": null,
+      "shell": "MarketingShell",
+      "chrome": "on",
+      "sections": []
+    },
     {
       "route": "/flows/[slug]",
       "pageType": null,

package/site-templates/marketing-site/TEMPLATE-MANIFEST.md

@@ -250,6 +250,13 @@ Target composition (deferred to **#5670**, same as `/meet` above):
 _Code route — no content, no sections._
 <!-- generated:end -->
 
+`/appointments`:
+
+<!-- generated:begin page=/appointments -->
+
+_Code route — no content, no sections._
+<!-- generated:end -->
+
 ### `/flows/<slug>` — InstrumentEntryPage · schema `WebPage` · signal-collectors
 
 The signal collector's landing (sample: a 5-question fit check). Sections: `hero` · `feature` · `step-flow` (preview) · `cta` · `faq`.
@@ -322,6 +329,7 @@ Everything in the Free manifest § 2a applies. Pro adds:
 ```
 marketing-site:
   requires: [marketing, docs-blog, scheduling, signal-collectors]
+  categories: [accounting, legal, hvac, roofing, plumbing, electrical, landscaping, auto-repair, real-estate, technology, medical-specialty]
   roster:
     - { route: "/",                               content: ["content/en/HomePage/home.mdx"] }
     - { route: "/how-it-works",                   content: ["content/en/LandingPage/how-it-works.mdx"] }
@@ -338,6 +346,7 @@ marketing-site:
     - { route: "/meet" }
     - { route: "/meet/[slug]" }
     - { route: "/meet/confirmed" }
+    - { route: "/appointments" }
     - { route: "/flows/[slug]" }
     - { route: "/flows/[slug]/start" }
     - { route: "/flows/[slug]/results/[payload]" }
@@ -382,8 +391,6 @@ Every component the roster rows' seed content composes today (generated):
 
 | Gap                                                                 | Issue      |
 | ------------------------------------------------------------------- | ---------- |
-| `/meet` rename                                                      | #5563      |
-| `ReportPage` + `/reports/<slug>`                                    | #5562      |
 | Module bundles carry no LICENSE                                     | #5552      |
 | Strip ignores `commercial_tier` (paid dirs still under `packages/`) | #5475      |
 | The Pro demo host `marketing-site.ailaunchkit.ai` — provisioning    | #5464 body |

package/site-templates/marketing-site/ailk-template.json

@@ -7,5 +7,5 @@
     "provenance.json": ".ailk-template.json",
     "content/en/blog/05-this-vc-morning-routine-will-make-you-super-annoying.mdx": "apps/web/content/en/blog/launching-ailk.mdx"
   },
-  "postInstall": "Template marketing-site installed: its module samples - the Pro blog (5 posts) and docs (3 pages) from docs-blog, the projects (2 + listing), thank-you pages (contact, newsletter, apply), fit-check flow definition, waitlist experiment and sample report PDF under apps/web/public/reports/ from signal-collectors - arrived with those module bundles, and /pricing, /privacy and /terms with the base layer (its /reports/<slug> route is pending #5562; /meet, /meet/<slug> and /meet/confirmed shipped by #5563). This template adds one copy override (blog post 05) - every sample is placeholder copy to replace before you launch."
+  "postInstall": "Template marketing-site installed: its module samples - the Pro blog (5 posts) and docs (3 pages) from docs-blog, the booking pages at /meet, /meet/<slug> and /meet/confirmed from scheduling, the projects (2 + listing), thank-you pages (contact, newsletter, apply), fit-check flow definition, waitlist experiment, the report reader at /reports/<slug> and its sample report PDF under apps/web/public/reports/ from signal-collectors - arrived with those module bundles, and /pricing, /privacy and /terms with the base layer. This template adds one copy override (blog post 05) - every sample is placeholder copy to replace before you launch."
 }