create-ailk 0.23.0 → 0.24.0

package/templates/apps/mcp/src/tools/index.ts

@@ -13,27 +13,29 @@ export {
 } from "./purchase.js";
 
 export {
-  listPagesInputSchema,
-  listPagesOutputSchema,
+  contentListParamsSchema,
+  contentListQuerySchema,
+  contentListResultSchema,
   ailkListPages,
   type ListPagesInput,
-  type ListPagesOutput,
+  type ContentListResult,
 } from "./list_pages.js";
 
 export {
-  readContentInputSchema,
-  readContentOutputSchema,
+  contentPageParamsSchema,
+  contentPageQuerySchema,
+  contentPageResultSchema,
   ailkReadContent,
   type ReadContentInput,
-  type ReadContentOutput,
+  type ContentPageResult,
 } from "./read_content.js";
 
 export {
-  searchContentInputSchema,
-  searchContentOutputSchema,
+  contentSearchQuerySchema,
+  contentSearchResultSchema,
   ailkSearchContent,
   type SearchContentInput,
-  type SearchContentOutput,
+  type ContentSearchResult,
 } from "./search_content.js";
 
 export {
@@ -92,28 +94,27 @@ export {
   type AuditOutput,
 } from "./audit.js";
 
+// #7171, #7172, #7173 — the three lead writes take their routes' body
+// exports and share one output schema (the route's 201 body or the tool's
+// error), re-exported once from capture_lead.
 export {
-  submitLeadInputSchema,
-  submitLeadOutputSchema,
+  leadSubmitBodySchema,
+  leadWriteOutputSchema,
   ailkCaptureLead,
-  type SubmitLeadInput,
-  type SubmitLeadOutput,
+  type LeadSubmitBody,
+  type LeadWriteOutput,
 } from "./capture_lead.js";
 
 export {
-  subscribeNewsletterInputSchema,
-  subscribeNewsletterOutputSchema,
+  leadSubscribeBodySchema,
   ailkSubscribeNewsletter,
-  type SubscribeNewsletterInput,
-  type SubscribeNewsletterOutput,
+  type LeadSubscribeBody,
 } from "./subscribe_newsletter.js";
 
 export {
-  requestCallbackInputSchema,
-  requestCallbackOutputSchema,
+  leadCallbackBodySchema,
   ailkRequestCallback,
-  type RequestCallbackInput,
-  type RequestCallbackOutput,
+  type LeadCallbackBody,
 } from "./request_callback.js";
 
 export {

package/templates/apps/mcp/src/tools/list_pages.ts

@@ -1,29 +1,35 @@
 /**
- * list_pages — returns published content pages, optionally filtered by type.
+ * list_pages — returns one page of the published content pages of a type.
  *
  * Pure read: resolves its adapter through `getMcpContentAdapter()` — the one
- * resolver seam (#5805, ADR 0011), MDX by default.
+ * resolver seam (#5805, ADR 0011), MDX by default — and answers through
+ * `listPagesItemList` (`@working-theory/content-adapters`).
  * No auth, no side effects, no network. The adapter reads from the filesystem.
  *
+ * HTTP twin (#7168): `GET /v1/content/:type` in `apps/api` parses the same
+ * `contentListParamsSchema` + `contentListQuerySchema` and answers through
+ * the same builder — the tool adopted the API, arguments and results: `type`
+ * is required, and `page` (default 1) / `pageSize` (default 20, at most 100)
+ * pick the window.
+ *
  * Phase 3 S3: optional `locale` parameter. Validated against `readLocales()`
  * allowlist; invalid or unknown values silently fall back to the project's
  * default locale (AC-i18n-07). Lists are locale-scoped — pages must exist in
  * the requested locale's directory to be enumerated.
  *
- * Input:  { type?: SchemaOrgType, locale?: string }
- * Output: { pages: Array<{ slug, type, title, description? }> }
+ * Input:  { type: SchemaOrgType, page?: number, pageSize?: number, locale?: string }
+ * Output: { "@context", "@type": "ItemList", type, items: ContentPage[],
+ *           pagination: { page, pageSize, totalItems, totalPages } }
  * Session/scope: none — read-only public content.
  */
 
+import { listPagesItemList } from "@working-theory/content-adapters";
 import {
-  SCHEMA_ORG_TYPES,
-  type SchemaOrgType,
-} from "@working-theory/content-adapters";
-import {
-  listPagesInputSchema,
-  listPagesOutputSchema,
+  contentListParamsSchema,
+  contentListQuerySchema,
+  contentListResultSchema,
+  type ContentListResult,
   type ListPagesInput,
-  type ListPagesOutput,
 } from "@working-theory/validation";
 
 import {
@@ -32,8 +38,12 @@ import {
 } from "../lib/content-adapter.js";
 import { resolveLocale } from "../lib/resolve-locale.js";
 
-export { listPagesInputSchema, listPagesOutputSchema };
-export type { ListPagesInput, ListPagesOutput };
+export {
+  contentListParamsSchema,
+  contentListQuerySchema,
+  contentListResultSchema,
+};
+export type { ListPagesInput, ContentListResult };
 
 /**
  * list_pages handler.
@@ -45,30 +55,14 @@ export type { ListPagesInput, ListPagesOutput };
 export async function ailkListPages(
   input: ListPagesInput,
   contentRoot?: string,
-): Promise<ListPagesOutput> {
-  listPagesInputSchema.parse(input);
+): Promise<ContentListResult> {
+  const { type } = contentListParamsSchema.parse(input);
+  const { page, pageSize } = contentListQuerySchema.parse(input);
 
   // Default: the one content-root resolver (#8070 D3).
   const root = contentRoot ?? mcpContentRoot();
   const locale = resolveLocale(input.locale);
   const adapter = getMcpContentAdapter({ contentRoot: root, locale });
 
-  const types: readonly SchemaOrgType[] = input.type
-    ? [input.type]
-    : SCHEMA_ORG_TYPES;
-
-  const perType = await Promise.all(
-    types.map((type) => adapter.listPages(type, locale)),
-  );
-
-  const pages: ListPagesOutput["pages"] = perType.flatMap((results) =>
-    results.map((page) => ({
-      slug: page.slug,
-      type: page.type,
-      title: page.title,
-      ...(page.description !== undefined && { description: page.description }),
-    })),
-  );
-
-  return listPagesOutputSchema.parse({ pages });
+  return listPagesItemList(adapter, { type, page, pageSize, locale });
 }

package/templates/apps/mcp/src/tools/read_content.ts

@@ -1,40 +1,58 @@
 /**
- * read_content — returns a single page's frontmatter + raw MDX body.
+ * read_content — returns a single page's document: its schema.org JSON-LD at
+ * the root, its frontmatter under `page`, and the raw MDX body on request.
  *
- * Pure read: resolves its adapter through `getMcpMdxContentAdapter()` — the
- * MDX-narrowed twin of the one resolver seam (#5805, ADR 0011; needed here
- * for `getPageSource()`'s raw body, which the base `ContentAdapter` contract
- * doesn't carry), MDX by default.
- * Composes getPageBySlug (frontmatter) + getPageSource (body) into a single
- * output shape. Returns null when the slug is not found — never throws for
- * a missing page.
+ * Pure read: resolves its adapter through `getMcpContentAdapter()` — the one
+ * resolver seam (#5805, ADR 0011), MDX by default — and answers through
+ * `readContentDocument` (`@working-theory/content-adapters`), over the
+ * deployment's `_site.mdx` (`lib/site-config.ts`). A missing page is the MCP
+ * not-found body (`lib/errors.ts`), carrying the route's 404 message — never
+ * a throw.
+ *
+ * HTTP twin (#7169): `GET /v1/content/:type/:slug` in `apps/api` parses the
+ * same `contentPageParamsSchema` + `contentPageQuerySchema` and answers
+ * through the same builder — the tool adopted the API, arguments and results:
+ * `body` is served only with `include: "body"`, from ONE `getPageSource`
+ * read (#5927). The builder's own capability check replaces the retired
+ * MDX-narrowed resolver twin this tool used to call: every adapter the
+ * resolver returns carries `getPageSource`, the fail-closed empty one
+ * included (#5876 D5).
  *
  * Phase 3 S3: optional `locale` parameter. Validated against `readLocales()`
  * allowlist; invalid or unknown values silently fall back to the project's
  * default locale (AC-i18n-07). The adapter applies its own fallback chain.
  *
- * Input:  { type: SchemaOrgType, slug: string, locale?: string } — `type`
- *         admits the full SchemaOrgType set (#6030 D1), mirrored in
- *         @working-theory/validation's MCP_SCHEMA_ORG_TYPES.
- * Output: { slug, type, frontmatter, body } | null
+ * Input:  { type: SchemaOrgType, slug: string, locale?: string,
+ *           include?: "body" } — `type` admits the full SchemaOrgType set
+ *         (#6030 D1), mirrored in @working-theory/validation's
+ *         MCP_SCHEMA_ORG_TYPES.
+ * Output: { ...jsonLd, page, body? } | { error: "not_found", message }
  * Session/scope: none — read-only public content.
  */
 
+import { readContentDocument } from "@working-theory/content-adapters";
 import {
-  readContentInputSchema,
-  readContentOutputSchema,
+  contentPageParamsSchema,
+  contentPageQuerySchema,
+  contentPageResultSchema,
+  type ContentPageResult,
   type ReadContentInput,
-  type ReadContentOutput,
 } from "@working-theory/validation";
 
 import {
-  getMcpMdxContentAdapter,
+  getMcpContentAdapter,
   mcpContentRoot,
 } from "../lib/content-adapter.js";
+import { notFoundError, type ErrorBody } from "../lib/errors.js";
 import { resolveLocale } from "../lib/resolve-locale.js";
+import { readSiteConfig } from "../lib/site-config.js";
 
-export { readContentInputSchema, readContentOutputSchema };
-export type { ReadContentInput, ReadContentOutput };
+export {
+  contentPageParamsSchema,
+  contentPageQuerySchema,
+  contentPageResultSchema,
+};
+export type { ReadContentInput, ContentPageResult };
 
 /**
  * read_content handler.
@@ -45,31 +63,19 @@ export type { ReadContentInput, ReadContentOutput };
 export async function ailkReadContent(
   input: ReadContentInput,
   contentRoot?: string,
-): Promise<ReadContentOutput> {
-  readContentInputSchema.parse(input);
+): Promise<ContentPageResult | ErrorBody> {
+  const { type, slug } = contentPageParamsSchema.parse(input);
+  const { include } = contentPageQuerySchema.parse(input);
 
   // Default: the one content-root resolver (#8070 D3).
   const root = contentRoot ?? mcpContentRoot();
   const locale = resolveLocale(input.locale);
+  const adapter = getMcpContentAdapter({ contentRoot: root, locale });
 
-  const adapter = getMcpMdxContentAdapter({ contentRoot: root, locale });
-
-  const source = await adapter.getPageSource(input.type, input.slug, locale);
-  if (source === null) return null;
-
-  return readContentOutputSchema.parse({
-    // Prefer the stored frontmatter's slug/type; fall back to the
-    // request-validated input (#5876 spec D9). On the MDX path the
-    // frontmatter always carries both — required, non-optional fields of
-    // FrontmatterSchema — so this is inert there and the mdx payload stays
-    // byte-identical. The fallback matters for cross-adapter identity: the
-    // Epic #5324 AC-WCE-04 comparison needs `read_content`'s payload to be
-    // identical across adapters, which a request-validated value guarantees
-    // and a stored-bookkeeping value only guarantees if the write path
-    // agrees.
-    slug: source.frontmatter.slug ?? input.slug,
-    type: source.frontmatter.type ?? input.type,
-    frontmatter: source.frontmatter as Record<string, unknown>,
-    body: source.body,
-  });
+  const document = await readContentDocument(
+    adapter,
+    { type, slug, locale, include },
+    readSiteConfig(root),
+  );
+  return document ?? notFoundError("Page not found");
 }

package/templates/apps/mcp/src/tools/request_callback.ts

@@ -1,32 +1,35 @@
 /**
- * request_callback — schedule a callback request.
+ * request_callback — request a callback: the body `POST /v1/leads/callback`
+ * takes.
  *
- * Validates input via Zod, forwards to POST /api/leads/callback via
- * @working-theory/api-client, and shapes the response into the MCP output schema.
- * No business logic — orchestration lives in apps/api B6.
+ * The tool adopted the API, arguments and results (#7173 — the operator's
+ * decision of 2026-10-19). Its input IS the route's `leadCallbackBodySchema`
+ * (`{ name, phone, preferredTime?, payload? }`; the catalog registers the
+ * same shape, so the SDK has already parsed the arguments against it — the
+ * `safeParse` here keeps the stdio path and the `invalid_input` branch
+ * honest), the parsed body is posted as the agent sent it — no `siteId`, no
+ * stamped `payload: {}` — and the route's 201 body `{ id, persisted, email }`
+ * comes back unchanged. No business logic — orchestration lives in apps/api.
  *
- * Input:  { name, phone, preferredTime? }
- * Output: { ok: true, id, persisted } | { ok: false, error: { kind, ... } }
  * Session/scope: none — anonymous write, no auth required.
  */
 
 import { apiClient } from "@working-theory/api-client";
 import {
-  requestCallbackInputSchema,
-  requestCallbackOutputSchema,
-  type RequestCallbackInput,
-  type RequestCallbackOutput,
+  leadCallbackBodySchema,
+  type LeadCallbackBody,
+  type LeadWriteOutput,
 } from "@working-theory/validation";
 
 import { visitorForwardHeadersForThisCall } from "../request-context.js";
 
-export { requestCallbackInputSchema, requestCallbackOutputSchema };
-export type { RequestCallbackInput, RequestCallbackOutput };
+export { leadCallbackBodySchema };
+export type { LeadCallbackBody };
 
 export async function ailkRequestCallback(
-  input: RequestCallbackInput,
-): Promise<RequestCallbackOutput> {
-  const parsed = requestCallbackInputSchema.safeParse(input);
+  input: LeadCallbackBody,
+): Promise<LeadWriteOutput> {
+  const parsed = leadCallbackBodySchema.safeParse(input);
   if (!parsed.success) {
     return {
       ok: false,
@@ -34,26 +37,16 @@ export async function ailkRequestCallback(
     };
   }
 
-  const { name, phone, preferredTime } = parsed.data;
-  const siteId = process.env.AILK_SITE_ID ?? "default";
-  const body = {
-    siteId,
-    name,
-    phone,
-    ...(preferredTime !== undefined && { preferredTime }),
-    payload: {},
-  };
-
   // #8073 — forward the address the transport trusted (never an identity
   // argument on this tool's own schema) so the hub counts the write in that
   // visitor's own rate-limit bucket rather than this MCP host's.
   const headers = visitorForwardHeadersForThisCall();
   const res = headers
-    ? await apiClient.leads.callback(body, { headers })
-    : await apiClient.leads.callback(body);
+    ? await apiClient.leads.callback(parsed.data, { headers })
+    : await apiClient.leads.callback(parsed.data);
   if (!res.ok) {
     return { ok: false, error: { kind: "api_error", status: res.status } };
   }
 
-  return { ok: true, id: res.body.id, persisted: res.body.persisted };
+  return res.body;
 }

package/templates/apps/mcp/src/tools/search_content.ts

@@ -2,9 +2,14 @@
  * search_content — full-text search across published content pages.
  *
  * Pure read: resolves its adapter through `getMcpContentAdapter()` — the one
- * resolver seam (#5805, ADR 0011), MDX by default.
- * Delegates to adapter.searchPages which scores by title/description/body match.
- * Limit defaults to 10; max 50. Query capped at 200 chars (enforced by Zod).
+ * resolver seam (#5805, ADR 0011), MDX by default — and answers through
+ * `searchContentItemList` (`@working-theory/content-adapters`), which scores by
+ * title/description/body match through `adapter.searchPages`.
+ *
+ * HTTP twin (#7167): `GET /v1/content/search` in `apps/api` parses the same
+ * `contentSearchQuerySchema` and answers through the same builder — the tool
+ * adopted the API, arguments and results. Limit defaults to 10; max 50. The
+ * search string `q` is capped at 200 chars (enforced by Zod).
  *
  * Phase 3 S3: optional `locale` parameter. Search is locale-scoped — only the
  * requested locale's content directory is searched. Invalid or unknown values
@@ -14,17 +19,19 @@
  * registry. Unlike `locale`, an unrecognised value is a validation error, not
  * a silent fallback: the registry is closed, so a bad slug is a caller mistake.
  *
- * Input:  { query: string, type?: SchemaOrgType, category?: CategorySlug,
+ * Input:  { q: string, type?: SchemaOrgType, category?: CategorySlug,
  *           limit?: number, locale?: string }
- * Output: { results: Array<{ slug, type, title, snippet, score }> }
+ * Output: { "@context", "@type": "ItemList", query, items: Array<{ slug, type,
+ *           title, snippet, score }>, totalItems }
  * Session/scope: none — read-only public content.
  */
 
+import { searchContentItemList } from "@working-theory/content-adapters";
 import {
-  searchContentInputSchema,
-  searchContentOutputSchema,
+  contentSearchQuerySchema,
+  contentSearchResultSchema,
+  type ContentSearchResult,
   type SearchContentInput,
-  type SearchContentOutput,
 } from "@working-theory/validation";
 
 import {
@@ -33,10 +40,8 @@ import {
 } from "../lib/content-adapter.js";
 import { resolveLocale } from "../lib/resolve-locale.js";
 
-export { searchContentInputSchema, searchContentOutputSchema };
-export type { SearchContentInput, SearchContentOutput };
-
-const DEFAULT_LIMIT = 10;
+export { contentSearchQuerySchema, contentSearchResultSchema };
+export type { SearchContentInput, ContentSearchResult };
 
 /**
  * search_content handler.
@@ -47,21 +52,12 @@ const DEFAULT_LIMIT = 10;
 export async function ailkSearchContent(
   input: SearchContentInput,
   contentRoot?: string,
-): Promise<SearchContentOutput> {
-  searchContentInputSchema.parse(input);
+): Promise<ContentSearchResult> {
+  const { q, type, category, limit } = contentSearchQuerySchema.parse(input);
 
   const root = contentRoot ?? mcpContentRoot();
   const locale = resolveLocale(input.locale);
   const adapter = getMcpContentAdapter({ contentRoot: root, locale });
 
-  const options = {
-    limit: input.limit ?? DEFAULT_LIMIT,
-    ...(input.type !== undefined && { type: input.type }),
-    ...(input.category !== undefined && { category: input.category }),
-    locale,
-  };
-
-  const rawResults = await adapter.searchPages(input.query, options);
-
-  return searchContentOutputSchema.parse({ results: rawResults });
+  return searchContentItemList(adapter, { q, type, category, limit, locale });
 }

package/templates/apps/mcp/src/tools/subscribe_newsletter.ts

@@ -1,32 +1,37 @@
 /**
- * subscribe_newsletter — add an email to the newsletter list.
+ * subscribe_newsletter — add an email to the newsletter list: the body
+ * `POST /v1/leads/subscribe` takes.
  *
- * Validates input via Zod, forwards to POST /api/leads/subscribe via
- * @working-theory/api-client, and shapes the response into the MCP output schema.
- * No business logic — orchestration lives in apps/api B6.
+ * The tool adopted the API, arguments and results (#7172 — the operator's
+ * decision of 2026-10-19). Its input IS the route's `leadSubscribeBodySchema`
+ * (`{ email, source }`; the catalog registers the same shape, so the SDK has
+ * already parsed the arguments against it — the `safeParse` here keeps the
+ * stdio path and the `invalid_input` branch honest), the parsed body is
+ * posted as the agent sent it — no `siteId`, no stamped `source`, and no
+ * `firstName`, which never reached the wire — and the route's 201 body
+ * `{ id, persisted, email }` comes back unchanged. No spoke marker: a
+ * Subscriber row has no payload to carry it. No business logic —
+ * orchestration lives in apps/api.
  *
- * Input:  { email, firstName? }
- * Output: { ok: true, id, persisted } | { ok: false, error: { kind, ... } }
  * Session/scope: none — anonymous write, no auth required.
  */
 
 import { apiClient } from "@working-theory/api-client";
 import {
-  subscribeNewsletterInputSchema,
-  subscribeNewsletterOutputSchema,
-  type SubscribeNewsletterInput,
-  type SubscribeNewsletterOutput,
+  leadSubscribeBodySchema,
+  type LeadSubscribeBody,
+  type LeadWriteOutput,
 } from "@working-theory/validation";
 
 import { visitorForwardHeadersForThisCall } from "../request-context.js";
 
-export { subscribeNewsletterInputSchema, subscribeNewsletterOutputSchema };
-export type { SubscribeNewsletterInput, SubscribeNewsletterOutput };
+export { leadSubscribeBodySchema };
+export type { LeadSubscribeBody };
 
 export async function ailkSubscribeNewsletter(
-  input: SubscribeNewsletterInput,
-): Promise<SubscribeNewsletterOutput> {
-  const parsed = subscribeNewsletterInputSchema.safeParse(input);
+  input: LeadSubscribeBody,
+): Promise<LeadWriteOutput> {
+  const parsed = leadSubscribeBodySchema.safeParse(input);
   if (!parsed.success) {
     return {
       ok: false,
@@ -34,24 +39,16 @@ export async function ailkSubscribeNewsletter(
     };
   }
 
-  const { email } = parsed.data;
-  // firstName is not part of the canonical subscribeSchema (no payload field);
-  // it is accepted by the MCP input but dropped here for now. The #7397 spoke
-  // marker (LEAD_SITE_MARKER_KEY) is absent for the same reason: a Subscriber
-  // row has no payload column, so subscribe has nowhere to carry it.
-  const siteId = process.env.AILK_SITE_ID ?? "default";
-  const body = { siteId, email, source: "mcp" };
-
   // #8073 — forward the address the transport trusted (never an identity
   // argument on this tool's own schema) so the hub counts the write in that
   // visitor's own rate-limit bucket rather than this MCP host's.
   const headers = visitorForwardHeadersForThisCall();
   const res = headers
-    ? await apiClient.leads.subscribe(body, { headers })
-    : await apiClient.leads.subscribe(body);
+    ? await apiClient.leads.subscribe(parsed.data, { headers })
+    : await apiClient.leads.subscribe(parsed.data);
   if (!res.ok) {
     return { ok: false, error: { kind: "api_error", status: res.status } };
   }
 
-  return { ok: true, id: res.body.id, persisted: res.body.persisted };
+  return res.body;
 }

package/templates/apps/web/CLAUDE.md

@@ -345,8 +345,9 @@ Every multi-step magnet is a page pair (#8840), rendered by one module,
 - **`/<magnet>/start`** — the walk, `noindex, follow`, full-screen with the
   back arrow alone (`NavBackLink`) above step 1. `lib/magnet-routes.ts`'s
   `isMagnetWalkPath` is what the locale layout drops the Nav and Footer on:
-  any path ending in `start`, plus `/careers/apply` and
-  `/careers/<posting>/apply`. The cookie consent banner stays.
+  any path ending in `start`, plus `/careers/apply`,
+  `/careers/<posting>/apply` and `/trial/request`. The cookie consent banner
+  stays.
 - **The ending.** A flow with an `ending` ends on it, never on `thankYou`:
   `FlowStepperClient` picks the outcome from the walk's answers
   (`selectFlowEndingOutcome`) — a screen in the finished card with `{name}`
@@ -362,6 +363,12 @@ Every multi-step magnet is a page pair (#8840), rendered by one module,
 - **The pairs.** `/flows/<slug>` is the canonical pair. `/careers/apply` and
   `/careers/<posting>/apply` walk the Job application magnet (the second
   titles step 1 with the posting and sends its slug as the hidden `job`).
+  `/trial` and `/trial/request` are the trial magnet's pair (#9287): the
+  landing passes `renderMagnetLanding` a `startPath`, so its one button
+  (the magnet's `landing.cta`, "Request a free trial") goes to
+  `/trial/request` rather than `/trial/start`, and the walk passes a
+  `title`, so an absent flow renders the contact email under its own `<h1>`,
+  as `/careers/apply` does. Both are `signal-collectors` slice files.
   Any other pair is written by `create-ailk add-route magnet --path <path>
   --flow <slug>`: two short pages carrying the `Standard magnet page
   (#8840)` marker, which `lib/__tests__/structured-data.test.tsx` exempts
@@ -539,7 +546,9 @@ A visitor's browser never calls the hub. Lead capture, newsletter signup, callba
 - Don't reach into `apps/api` or `apps/mcp` from `apps/web`. They're peer apps — talk via HTTP/MCP.
 - Don't commit images to `screenshots/` — only the `.gitkeep` is tracked.
 
-Last updated: 2026-10-19 — § Magnet pages: `/careers/apply` renders the contact email under its own `<h1>` when its flow is absent or the hub cannot answer; `readMagnet`'s `not-configured` kind 404s an unknown `/reports/<slug>` (and its `/start`) on a site with no hub to ask, while a configured hub that is down keeps #8848 D6's contact email (#9219) — verified against `app/[locale]/flows/[slug]/magnet-page.tsx`, `app/[locale]/careers/apply/page.tsx`, `app/[locale]/reports/deliverable-page.tsx` and `app/[locale]/reports/[slug]/{page,start/page}.tsx`.
+Last updated: 2026-10-20 — § Magnet pages: the trial magnet's pair, `/trial` (its button to `/trial/request` through `renderMagnetLanding`'s `startPath`) and the chrome-free `/trial/request` walk with its own `<h1>` fallback (#9287 C2, DD10) — verified against `app/[locale]/flows/[slug]/magnet-page.tsx`, `app/[locale]/trial/{page,request/page}.tsx` and `lib/magnet-routes.ts`.
+
+Prior: 2026-10-19 — § Magnet pages: `/careers/apply` renders the contact email under its own `<h1>` when its flow is absent or the hub cannot answer; `readMagnet`'s `not-configured` kind 404s an unknown `/reports/<slug>` (and its `/start`) on a site with no hub to ask, while a configured hub that is down keeps #8848 D6's contact email (#9219) — verified against `app/[locale]/flows/[slug]/magnet-page.tsx`, `app/[locale]/careers/apply/page.tsx`, `app/[locale]/reports/deliverable-page.tsx` and `app/[locale]/reports/[slug]/{page,start/page}.tsx`.
 
 Prior: 2026-10-18 — § Spoke checkout: the Offerings buy route is the one selling path, and the legacy env-key buy route, webhook route, `lib/checkout.ts` and checkout e2e workflow are retired (#9142) — verified against `app/api/offerings/checkout/[lookupKey]/route.ts`, `app/[locale]/checkout/*/page.tsx`, `lib/checkout-config.ts` and create-ailk's `spoke-checkout.ts` and `sync-routes.ts`.
 

package/templates/apps/web/app/[locale]/contact/__tests__/ConversationalIntakeWrapper.test.tsx

@@ -7,7 +7,7 @@
  *   boundary is mocked (`@working-theory/api-client`'s `leads.submit`) —
  *   the REAL `ConversationalIntake` block (#4543) and its engine (#4532),
  *   the REAL `captureLeadAction` (the SAME action the shared
- *   `LeadCaptureForm` on `/contact` uses), and the REAL `submitLeadInputSchema` validation all run, proving
+ *   `LeadCaptureForm` on `/contact` uses), and the REAL `contactFormSchema` validation all run, proving
  *   the whole chain end to end. No file under apps/api is imported, mocked,
  *   or touched by this test or by the wiring it exercises.
  * AC2 — Skip renders the existing form, carrying over answers already

package/templates/apps/web/app/[locale]/contact/contact.actions.ts

@@ -3,8 +3,10 @@
 /**
  * captureLeadAction — Server Action paired with ailkCaptureLead MCP tool.
  *
- * Validates contact-form input with submitLeadInputSchema (shared schema per
- * ADR 0013), calls POST /v1/leads/submit via @working-theory/api-client, and returns
+ * Validates contact-form input with its own `contactFormSchema` (the form's
+ * field set is the page's, not a wire contract — the `capture_lead` MCP tool
+ * takes the route body since #7171), calls POST /v1/leads/submit via
+ * @working-theory/api-client, and returns
  * the shared `LeadCaptureForm` block's `LeadCaptureFormState`.
  *
  * Canonical filename: contact.actions.ts (*.actions.ts per ADR 0013 / U0 spec
@@ -102,11 +104,11 @@ import {
   CONTACT_LEAD_SOURCES,
   flowCheckoutOfferingSchema,
   leadSubmitNextSchema,
-  submitLeadInputSchema,
 } from "@working-theory/validation";
 import { cookies, headers } from "next/headers";
 import { redirect } from "next/navigation";
 import { getLocale, getTranslations } from "next-intl/server";
+import { z } from "zod";
 
 import { accountInviteHref } from "../../../lib/account-invite";
 import { consentVisitorHeader, readConsentVisitor } from "../../../lib/consent-visitor";
@@ -139,6 +141,14 @@ const DEFAULT_SOURCE = "contact-form";
 const CONSENT_REQUIRED = "Please accept the terms to send your message.";
 const MAX_EXTRA_FIELD_LENGTH = 2000;
 
+/** The form's four fields and bounds; each field error is zod's own message. */
+const contactFormSchema = z.object({
+  name: z.string().min(1).max(200),
+  email: z.string().email(),
+  message: z.string().max(2000).optional(),
+  phone: z.string().max(50).optional(),
+});
+
 /**
  * The declared extra fields, or `null` when they exceed the bounds. Non-string
  * entries (files) and Next's own `$ACTION_…` keys are skipped.
@@ -253,7 +263,7 @@ export async function captureLeadAction(
     fieldErrors.consent = CONSENT_REQUIRED;
   }
 
-  const parsed = submitLeadInputSchema.safeParse(raw);
+  const parsed = contactFormSchema.safeParse(raw);
   if (!parsed.success) {
     for (const issue of parsed.error.issues) {
       const field = String(issue.path[0] ?? "form");

package/templates/apps/web/app/[locale]/contact/intake-script.ts

@@ -4,7 +4,7 @@
  * leg).
  *
  * Three open questions, deliberately keyed `name` / `message` / `email` —
- * the SAME field names `submitLeadInputSchema` (packages/validation)
+ * the SAME field names `contactFormSchema` (`./contact.actions.ts`)
  * expects. `ConversationalIntakeWrapper` reads `IntakeEngineState.answers`
  * by these exact ids to build the `FormData` it hands to the existing
  * `captureLeadAction` (`./contact.actions.ts`), so the script's question