create-ailk 0.6.0 → 0.6.1

package/templates/DESIGN.md

@@ -0,0 +1,155 @@
+---
+name: AI Launch Kit base scaffold
+description: The foundation every AI Launch Kit site starts from — pure white, black ink, black hairline rules, system type, generous pacing.
+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: _base (the AI Launch Kit base scaffold)
+  Version: create-ailk {{CREATE_AILK_VERSION}}
+
+  This file describes the visual system this scaffold ships with. The impeccable
+  design skill reads it at the start of every design session, so an agent
+  building a new page stays on-system.
+
+  A site template (installed with `--template <name>`) replaces this file with
+  its own DESIGN.md — same path, with a header naming the template it came
+  from. Edit whichever one your site has; the header tells you which.
+
+  The tokens above describe what the scaffold 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.
+-->
+
+# AI Launch Kit base scaffold
+
+## Overview
+
+The foundation reads like a well-made wireframe: nothing on the page but the words, black on white, with rules where other sites use shadows and colour. It is the look of a site whose owner has not chosen a brand yet and does not pretend otherwise — every placeholder reads as a placeholder, and the structure of the argument is what the visitor sees. A brand is applied on top of it; it is not one.
+
+Every page is composed from the AI Launch Kit component library (`@working-theory/ui`). Nothing is hand-built: a page is a list of registered sections, each with a bounded set of variants. Each section is one full-width band with a lot of air around it.
+
+## 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
+
+Content sits in a 1280px container. Sections stack at the platform's 4rem rhythm today; a few sections choose a compact (2.5rem) or spacious (6rem) step internally. Card grids gap 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
+
+Wordmark or logo left, page links, then an outlined and a filled button at the far right. A black hairline separates it from the page. An optional announcement banner sits above it.
+
+## 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/templates/README.md

@@ -29,7 +29,7 @@ pnpm preflight   # architecture + types + lint + build
 pnpm build       # production build
 ```
 
-> Requires Node.js 20+ and `pnpm`. No vendor API keys are required for first boot — Stripe, Anthropic, and email-provider integrations are opt-in.
+> Requires Node.js 20+ and `pnpm` — that is the whole prerequisite list. No database is needed to run or build this site (see [When you need a database](#when-you-need-a-database)), and no vendor API keys are required for first boot — Stripe, Anthropic, and email-provider integrations are opt-in. `pnpm install` generates the Prisma client for you; there is no generator step to remember.
 
 ## Content
 
@@ -63,16 +63,50 @@ Apply `myTheme` via the provider you use to wrap children. The full extension su
 
 Copy `.env.example` to `.env` and fill in only what you need. Most variables are optional. A complete reference:
 
-| Variable                           | Purpose                                                                                                                   |
-| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
-| `AILK_LICENSE_KEY`                 | Optional. JWT issued by ailaunchkit.ai; verified locally to unlock Pro features. Get one at <https://ailaunchkit.ai/pro>. |
-| `NEXT_PUBLIC_STREAMING_AI_ENABLED` | Optional. Set to `true` to enable the opt-in streaming AI assist UI. Off by default.                                      |
-| `ANTHROPIC_API_KEY`                | Required only when `NEXT_PUBLIC_STREAMING_AI_ENABLED=true`. Used by the AI assist surface only.                           |
-| `AILK_LOCAL_LEAD_CAPTURE`          | Optional. When `true`, leads from the contact form are written to a local file instead of an API.                         |
-| `AILK_LEADS_API_URL`               | Optional. Override the upstream that receives lead-capture submissions.                                                   |
+| Variable                           | Purpose                                                                                                                       |
+| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| `AILK_LICENSE_KEY`                 | Optional. JWT issued by ailaunchkit.ai; verified locally to unlock Pro features. Get one at <https://ailaunchkit.ai/pricing>. |
+| `NEXT_PUBLIC_STREAMING_AI_ENABLED` | Optional. Set to `true` to enable the opt-in streaming AI assist UI. Off by default.                                          |
+| `ANTHROPIC_API_KEY`                | Required only when `NEXT_PUBLIC_STREAMING_AI_ENABLED=true`. Used by the AI assist surface only.                               |
+| `AILK_LOCAL_LEAD_CAPTURE`          | Optional. When `true`, leads from the contact form are written to a local file instead of an API.                             |
+| `AILK_LEADS_API_URL`               | Optional. Override the upstream that receives lead-capture submissions.                                                       |
 
 See [`.env.example`](./.env.example) for the full template with comments. Per-app overrides (e.g. `apps/api/.env`) are honored alongside the root `.env`.
 
+## When you need a database
+
+**A free marketing site needs no database at all.** `pnpm install`, `pnpm dev` and `pnpm build` all run green on an empty machine with no Postgres, no `DATABASE_URL` and no `.env` — the pages render from `content/*.mdx`, and the Prisma client is generated for you by `database`'s `postinstall` so the workspace type-checks and builds either way.
+
+You need Postgres once you turn on one of these four:
+
+| Surface                                | What it stores                                                                                                    |
+| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
+| **Auth** (sign-in, sessions, accounts) | users, sessions, accounts                                                                                         |
+| **Flows** — `/save` and `/checkout`    | a visitor's in-progress flow state, so they can resume or pay later                                               |
+| **Lead capture in DB mode**            | submitted leads. The default file mode (`AILK_LOCAL_LEAD_CAPTURE=true`) writes to disk instead and needs nothing. |
+| **`CONTENT_ADAPTER=database`**         | pages authored in the Artifact store rather than in `content/*.mdx`                                               |
+
+### One command to get one
+
+```bash
+docker run --name ailk-postgres -e POSTGRES_PASSWORD=postgres -p 5432:5432 -d postgres:17
+```
+
+Point the app at it in `.env` (both variables, same URL for local work — the second is the direct connection `prisma migrate` uses):
+
+```bash
+DATABASE_URL=postgresql://postgres:postgres@localhost:5432/postgres
+DATABASE_URL_NON_POOLED=postgresql://postgres:postgres@localhost:5432/postgres
+```
+
+Then create the tables:
+
+```bash
+pnpm db:migrate:deploy
+```
+
+That is the whole setup. `pnpm db:studio` opens a browser UI over the data, and `pnpm db:seed` loads the sample rows. Turning the database off again is just unsetting the two variables — the marketing pages never read it.
+
 ## AI assist (optional)
 
 The site ships with an opt-in streaming AI assist. It is **off by default**. To turn it on, set `NEXT_PUBLIC_STREAMING_AI_ENABLED=true` in `.env` and provide an `ANTHROPIC_API_KEY`. The assist runs server-side so the API key never reaches the browser. With both unset, the chat UI is hidden and no AI traffic flows.

package/templates/apps/web/PRODUCT.md

@@ -0,0 +1,86 @@
+# Product
+
+<!-- impeccable:product-schema 1 -->
+
+<!--
+  This file is the product context the impeccable design skill reads before
+  every design decision on this app (apps/web). It holds facts about your
+  product, not the look (that is DESIGN.md) and not the pitch (that is your
+  strategy docs).
+
+  Platform, Stack and the accessibility floor below are facts about this
+  AI Launch Kit scaffold. Every other section is empty until it has a real
+  source: each one names the strategy doc it will come from. Until then, treat
+  it as unknown — never invent a customer, a number or a capability to fill it.
+
+  Each section carries a `source:` marker. `hand` means nothing generates the
+  section, so edit it directly (or answer `/impeccable init`'s questions).
+-->
+
+## Platform
+
+<!-- source: hand -->
+
+web
+
+## Stack
+
+<!-- source: hand -->
+
+Next.js 16 (App Router) and React 19, in TypeScript, styled with Tailwind CSS 4. Pages are MDX content files rendered through the AI Launch Kit component library (`@working-theory/ui`, `@working-theory/theme`, `@working-theory/page-renderer`); translations through next-intl. pnpm workspace. Exact versions: `apps/web/package.json`.
+
+## Users
+
+<!-- source: hand -->
+
+[Not yet set — comes from your strategy run: Messaging Canvas §3 Champion profile]
+
+## Product Purpose
+
+<!-- source: hand -->
+
+[Not yet set — comes from your strategy run: ENTITY §1.4 Purpose]
+
+## Positioning
+
+<!-- source: hand -->
+
+[Not yet set — comes from your strategy run: Messaging Canvas §1 Inherited from positioning]
+
+## Operating Context
+
+<!-- source: hand -->
+
+[Not yet set — comes from your strategy run: Messaging Canvas §3 Champion profile, Reading context]
+
+## Capabilities and Constraints
+
+<!-- source: hand -->
+
+[Not yet set — comes from your strategy run: OFFERINGS §4 Offering catalog]
+
+## Brand Commitments
+
+<!-- source: hand -->
+
+[Not yet set — comes from your strategy run: VOICE §2 Voice anchor, and your brand_assets/ folder]
+
+## Evidence on Hand
+
+<!-- source: hand -->
+
+[Not yet set — comes from your strategy run: Messaging Canvas §5 Pillars, the proof each pillar carries]
+
+## Product Principles
+
+<!-- source: hand -->
+
+[Not yet set — comes from your strategy run: ENTITY § Product Principles]
+
+## Accessibility & Inclusion
+
+<!-- source: hand -->
+
+The AI Launch Kit build audits every section component in its library against WCAG 2 Level A and AA (axe-core, plus its best-practice rules), on each section's stories. Smaller components are audited only where a story opts in, and your own pages are not audited automatically. Every text-on-background pair in the platform's default colors meets 4.5:1 contrast for normal text and 3:1 for large text, in light and dark mode. Colors you set yourself in `content/_site.mdx` are not checked automatically — keep them to the same ratios.
+
+Commitments above this floor: [Not yet set — comes from your strategy run: ENTITY, accessibility commitments]

package/templates/apps/web/lib/__tests__/site-theme.test.ts

@@ -4,11 +4,28 @@
  * This is the end-to-end claim the wiring makes — a site declares a theme and
  * the built page renders in those colours — asserted on the actual repo file
  * rather than a fixture, so deleting the `theme:` block would fail here.
+ *
+ * Every expectation is DERIVED from whichever `_site.mdx` the test reads, never
+ * hard-coded (#6460). This file is snapshotted into `create-ailk`'s
+ * `templates/`, so it runs against TWO different `_site.mdx` files: this
+ * monorepo's, and the scaffold's own. Hard-coded values made it a snapshot of
+ * one tree's palette masquerading as a round-trip test — green here, red in a
+ * scaffold whose theme differs, which is exactly what happened when the base
+ * scaffold moved to the black-on-white foundation. It also meant a CUSTOMER who
+ * took the file's own invitation to "declare only what you change" got a red
+ * suite for editing their own colours.
+ *
+ * Deriving keeps every claim the hard-coded form made — the mapping is applied,
+ * the values reach the CSS, and nothing else moves — while making all three
+ * true of any declared palette. Deleting the `theme:` block still fails, on the
+ * `toBeDefined()` below.
  */
-import { mkdtempSync, writeFileSync } from "node:fs";
+import { mkdtempSync, readFileSync, writeFileSync } from "node:fs";
 import { tmpdir } from "node:os";
 import { join } from "node:path";
 
+import { parse as parseYaml } from "yaml";
+
 import { PartialColorPaletteSchema } from "@working-theory/site-config/schema";
 import { siteColorTokenMap, themeToCssVarsBothModes } from "@working-theory/theme";
 
@@ -26,6 +43,46 @@ function darkBlock(css: string): string {
   return css.slice(css.indexOf(':root[data-theme="dark"]'));
 }
 
+/** The two modes, as the palette and the emitted CSS both name them. */
+const MODES = ["light", "dark"] as const;
+
+/**
+ * The `theme.colors` block exactly as the `_site.mdx` under test declares it —
+ * raw SLOT names (`text`, `primary`), not token keys. Read with the same
+ * frontmatter parse `site-theme.ts` uses, so the test cannot pass against a
+ * file the implementation reads differently.
+ */
+function declaredColors(): Partial<Record<(typeof MODES)[number], Record<string, string>>> {
+  const raw = readFileSync(join(REPO_CONTENT_ROOT, "_site.mdx"), "utf8");
+  const frontmatter = /^---\r?\n([\s\S]*?)\r?\n---/.exec(raw);
+  const parsed = parseYaml(frontmatter?.[1] ?? "") as
+    | { theme?: { colors?: Record<string, Record<string, string>> } }
+    | null;
+  return parsed?.theme?.colors ?? {};
+}
+
+/**
+ * The CSS custom property a token key is emitted as — `fgOnBrand` →
+ * `--color-fg-on-brand`. The colon in every call site anchors the match, so
+ * `--color-surface` never collides with `--color-surface-secondary`.
+ */
+function cssVar(tokenKey: string): string {
+  return `--color-${tokenKey.replace(/[A-Z]/g, (c) => `-${c.toLowerCase()}`)}`;
+}
+
+/** `{ [tokenKey]: value }` for one mode's declared slots, mapping applied. */
+function declaredTokens(mode: (typeof MODES)[number]): Record<string, string> {
+  const out: Record<string, string> = {};
+  for (const [slot, value] of Object.entries(declaredColors()[mode] ?? {})) {
+    const tokenKey = siteColorTokenMap[slot as keyof typeof siteColorTokenMap];
+    // A slot with no token counterpart cannot reach the CSS at all —
+    // `siteThemeToBrandTokens` throws on it, which the schema's own tests
+    // cover. Nothing to assert about it here.
+    if (typeof tokenKey === "string") out[tokenKey] = value;
+  }
+  return out;
+}
+
 describe("loadSiteBrandTokens — the real content/_site.mdx", () => {
   const originalRoot = process.env.AILK_CONTENT_ROOT;
 
@@ -38,35 +95,93 @@ describe("loadSiteBrandTokens — the real content/_site.mdx", () => {
     else process.env.AILK_CONTENT_ROOT = originalRoot;
   });
 
-  it("translates the declared theme into the token overlay", () => {
-    expect(loadSiteBrandTokens()).toEqual({
-      colors: {
-        light: { bg: "#fdfcfa", fg: "#1c1917" },
-        dark: { bg: "#0c0a09" },
-      },
-    });
+  it("translates every colour the file declares into its mapped token", () => {
+    const overlay = loadSiteBrandTokens();
+    // The `theme:` block exists and produced an overlay — the claim the
+    // hard-coded form made by naming values, kept without naming them.
+    expect(overlay).toBeDefined();
+
+    // `BrandTokenOverrides` is deliberately `Readonly<Record<string, unknown>>`
+    // — `@working-theory/theme` cannot name the overlay's shape without
+    // pinning it to one token set — so the test states the shape it asserts
+    // about. The hard-coded form sidestepped this by comparing whole objects.
+    const colors = (overlay?.["colors"] ?? {}) as Partial<
+      Record<(typeof MODES)[number], Record<string, string>>
+    >;
+
+    let asserted = 0;
+    for (const mode of MODES) {
+      const expectedTokens = declaredTokens(mode);
+      // Exactly the declared slots, nothing invented and nothing dropped.
+      expect(colors[mode] ?? {}).toEqual(expectedTokens);
+      asserted += Object.keys(expectedTokens).length;
+    }
+    // Non-vacuity: a file that declared nothing would satisfy the loop above.
+    expect(asserted).toBeGreaterThan(0);
   });
 
   it("reaches the emitted CSS custom properties", () => {
     const brand = loadSiteBrandTokens();
     const css = themeToCssVarsBothModes(brand ? { brand } : {});
-
-    expect(lightBlock(css)).toContain("--color-bg: #fdfcfa;");
-    expect(lightBlock(css)).toContain("--color-fg: #1c1917;");
-    expect(darkBlock(css)).toContain("--color-bg: #0c0a09;");
+    const blockFor = { light: lightBlock(css), dark: darkBlock(css) };
+
+    let asserted = 0;
+    for (const mode of MODES) {
+      for (const [tokenKey, value] of Object.entries(declaredTokens(mode))) {
+        expect(blockFor[mode]).toContain(`${cssVar(tokenKey)}: ${value};`);
+        asserted += 1;
+      }
+    }
+    expect(asserted).toBeGreaterThan(0);
   });
 
   it("changes exactly the declared variables and nothing else", () => {
     const brand = loadSiteBrandTokens();
     const themed = themeToCssVarsBothModes(brand ? { brand } : {});
-    const expected = themeToCssVarsBothModes()
-      // light block — the two declared light colours
-      .replace("--color-bg: #ffffff;", "--color-bg: #fdfcfa;")
-      .replace("--color-fg: #030712;", "--color-fg: #1c1917;")
-      // dark block — the one declared dark colour
-      .replace("--color-bg: #0a0a0a;", "--color-bg: #0c0a09;");
-
-    expect(themed).toBe(expected);
+
+    // Rebuild the expectation from the DEFAULT CSS by overwriting, per mode
+    // block, only the variables this site declares. Anything the overlay
+    // touched beyond them makes the final equality fail — which is the whole
+    // point of this case.
+    const base = themeToCssVarsBothModes();
+    const rewritten = { light: lightBlock(base), dark: darkBlock(base) };
+    for (const mode of MODES) {
+      for (const [tokenKey, value] of Object.entries(declaredTokens(mode))) {
+        const pattern = new RegExp(`(${cssVar(tokenKey)}: )[^;]+;`);
+        // The variable must exist in the default block for the overwrite to
+        // mean anything — a replace with no target would weaken the equality
+        // below into a tautology. Presence is the right check rather than
+        // "the text changed": a site may legitimately declare a value that
+        // already MATCHES the default (the black-on-white base declares
+        // `bg: #ffffff`, which light mode already is), and that no-op is
+        // correct, not vacuous.
+        expect(rewritten[mode]).toMatch(pattern);
+        rewritten[mode] = rewritten[mode].replace(pattern, `$1${value};`);
+      }
+
+      // `--color-surface-raised` is DERIVED, not independent: the emitter
+      // resolves it from `surfaceSecondary` in light mode and from `surface`
+      // in dark (`packages/theme/src/theme-to-css.ts`, and the rule is
+      // documented at `site-theme.ts`'s header). So a site that declares
+      // either of those moves it too, and the equality below has to account
+      // for it — re-derived here from whatever the block now carries rather
+      // than restated as a value, so the two cannot drift.
+      //
+      // Kept inside the total equality instead of excluded from it: this
+      // variable is SUPPOSED to move, and excluding it would stop the test
+      // noticing if it ever stopped moving.
+      const derivedFrom = mode === "light" ? "surfaceSecondary" : "surface";
+      const sourceValue = new RegExp(`${cssVar(derivedFrom)}: ([^;]+);`).exec(
+        rewritten[mode],
+      )?.[1];
+      expect(sourceValue).toBeDefined();
+      rewritten[mode] = rewritten[mode].replace(
+        /(--color-surface-raised: )[^;]+;/,
+        `$1${sourceValue};`,
+      );
+    }
+
+    expect(themed).toBe(rewritten.light + rewritten.dark);
   });
 
   it("treats a bare `theme:` key as no theme, rather than throwing", () => {

package/templates/apps/web/lib/site-brand.tsx

@@ -108,14 +108,10 @@ export const SITE_BASE_URL =
   process.env.NEXT_PUBLIC_BASE_URL ?? siteFrontmatter?.baseUrl ?? FALLBACK_BASE_URL;
 
 /**
- * Shared brand mark — the light/dark logo pair, mode-switched via the theme
- * `dark:` utility. RSC-safe (no hooks, no client state).
+ * Shared brand mark — the square logomark (the central brand library's
+ * `logomark/loop/icon.svg`). The Nav pairs it with `/wordmark.svg`.
+ * RSC-safe (no hooks, no client state).
  */
 export function siteLogo(): ReactElement {
-  return (
-    <>
-      <img src="/logo-light.svg" alt={SITE_NAME} height={28} className="block dark:hidden" />
-      <img src="/logo-dark.svg" alt={SITE_NAME} height={28} className="hidden dark:block" />
-    </>
-  );
+  return <img src="/logomark.svg" alt={SITE_NAME} width={28} height={28} className="block" />;
 }

package/templates/apps/web/middleware.ts

@@ -79,7 +79,7 @@ export function middleware(request: NextRequest): NextResponse {
 // The trailing `.*\\..*` alternative excludes any path whose last segment
 // contains a dot, i.e. every file with an extension. Without it the negative
 // lookahead named only favicon.ico, so next-intl's locale rewrite swallowed
-// every OTHER public/ asset — logo-light.svg, logo-dark.svg, site.webmanifest,
+// every OTHER public/ asset — logomark.svg, wordmark.svg, site.webmanifest,
 // og-default.png — and each 404'd (#4090 item 4). robots.txt and sitemap.xml are
 // route handlers rather than public/ files, but they carry extensions too and
 // are equally not locale-scoped, so the same rule covers them.

package/templates/apps/web/src/lib/commerce-sections.ts

@@ -43,13 +43,45 @@
  */
 let registration: Promise<boolean> | undefined;
 
+/**
+ * The paid package's specifier, held in a CONST rather than written inline at
+ * the `import()` call (#6440 AC2).
+ *
+ * `webpackIgnore` defers only WEBPACK's resolution; `tsc` resolves a dynamic
+ * `import()` whose argument is a string LITERAL exactly as eagerly as a static
+ * one, so the literal form failed a keyless scaffold's type-check with TS2307
+ * "Cannot find module '@working-theory/ui-commerce'" — the build error #6440
+ * was filed for. This monorepo never saw it: `packages-paid/ui-commerce` is on
+ * disk here and `apps/web/package.json` declares it `workspace:*`, so the
+ * specifier resolves and the defect is reachable only from a scaffold.
+ *
+ * A non-literal specifier is the whole fix. `tsc` does not attempt module
+ * resolution on an `import()` it cannot constant-fold, so the paid package's
+ * ABSENCE stops being a type error — while webpack still honours the magic
+ * comment beside it and Node still performs the real resolution at runtime,
+ * leaving the `catch` below as the one and only thing that observes whether
+ * the package is installed. The behaviour is unchanged in both directions:
+ * a licensed deployment registers the sections; a keyless one returns false.
+ *
+ * The file deliberately stays in the BASE TREE rather than moving into the
+ * commerce slice: `/purchase/success` and `/purchase/cancel` import it
+ * statically, so slicing it out would take the return pages with it and
+ * regress #6084 D12 (disposed again on #6440, 2026-09-22).
+ */
+const COMMERCE_UI_PACKAGE = "@working-theory/ui-commerce";
+
+/** The one export this module needs from the paid package. */
+interface CommerceSectionsModule {
+  registerCommerceSections: () => void;
+}
+
 export function ensureCommerceSectionsRegistered(): Promise<boolean> {
   if (!registration) {
     registration = (async () => {
       try {
-        const mod = await import(
-          /* webpackIgnore: true */ "@working-theory/ui-commerce"
-        );
+        const mod = (await import(
+          /* webpackIgnore: true */ COMMERCE_UI_PACKAGE
+        )) as CommerceSectionsModule;
         mod.registerCommerceSections();
         return true;
       } catch {

package/templates/content/_site.mdx

@@ -17,10 +17,25 @@ analytics:
 theme:
   colors:
     light:
-      bg: "#fdfcfa"
-      text: "#1c1917"
+      bg: "#ffffff"
+      bgMuted: "#ffffff"
+      surface: "#ffffff"
+      border: "#000000"
+      text: "#000000"
+      textMuted: "#333333"
+      primary: "#000000"
+      primaryFg: "#ffffff"
+      accent: "#000000"
     dark:
-      bg: "#0c0a09"
+      bg: "#000000"
+      bgMuted: "#000000"
+      surface: "#000000"
+      border: "#ffffff"
+      text: "#ffffff"
+      textMuted: "#cccccc"
+      primary: "#ffffff"
+      primaryFg: "#000000"
+      accent: "#ffffff"
 ---
 
 <!--

package/templates/database/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @working-theory/database
 
+## 0.26.0
+
+### Patch Changes
+
+- Updated dependencies []:
+  - @working-theory/validation@0.26.0
+
 ## 0.25.0
 
 ### Minor Changes

package/templates/database/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@working-theory/database",
-  "version": "0.25.0",
+  "version": "0.26.0",
   "license": "Apache-2.0",
   "publishConfig": {
     "access": "public"
@@ -60,7 +60,8 @@
     "db:seed:test": "tsx seed-test.ts",
     "db:studio": "prisma studio",
     "test": "jest --config jest.config.cjs",
-    "test:watch": "jest --config jest.config.cjs --watch"
+    "test:watch": "jest --config jest.config.cjs --watch",
+    "postinstall": "prisma generate"
   },
   "dependencies": {
     "@prisma/adapter-pg": "^7.8.0",