@wildo-ai/saas-website 1.1.1

package/dist/esm/schemas/blog/blog-post-frontmatter.shared.schemas.js

@@ -0,0 +1,85 @@
+import { z } from 'zod';
+import { AvailableLanguage } from '@wildo-ai/saas-models/public-runtime';
+/**
+ * @wildo_source:part:start saas.website.blog.frontmatter facet:layer:shared facet:family:website
+ *
+ * `BlogPostFrontmatter` — the YAML frontmatter contract every blog
+ * post MDX file under `examples/<app>/website/src/content/blog/<locale>/`
+ * MUST satisfy.
+ *
+ * **Q16=B context**: blogs are authored as full per-locale MDX files
+ * (one MDX per (slug, locale) pair), NOT as label-pack-keyed content.
+ * The frontmatter therefore carries strings directly (`title`,
+ * `summary`) rather than label keys — there is no shared
+ * label-pack-driven authoring surface for blog content. This is
+ * intentional: blog copy is long-form and locale-divergent; forcing
+ * it through a structural label-pack would either inflate the pack
+ * or fragment the prose.
+ *
+ * **Field rationale**:
+ *
+ * - `title` — REQUIRED. Renders into `<title>`, `og:title`, and the
+ *   in-page H1. Authored as a direct string, deliberately.
+ * - `summary` — REQUIRED. Renders into `<meta name="description">`,
+ *   `og:description`, and listing-card descriptions. Direct string.
+ * - `slug` — REQUIRED. URL slug (lowercase kebab-case). Brand prevents
+ *   accidental swap with `WebsitePageRef` (same shape, different role).
+ * - `locale` — REQUIRED. The post's locale. Drives the URL prefix
+ *   (`/<locale>/blog/<slug>`) and `<html lang>`. Cross-locale
+ *   correspondence is established by sharing the `slug` across
+ *   per-locale MDX files (e.g. `en/why-context.md` and
+ *   `fr/why-context.md` are the same post in two locales).
+ * - `publishedAt` — REQUIRED. ISO-8601 date-time string. Renders into
+ *   `og:article:published_time` and the listing-card date label.
+ *   Stored as string (not `z.coerce.date`) because YAML frontmatter
+ *   parsers preserve the original string and the SEO emitters need
+ *   the original ISO formatting (no Date.toISOString() round-trip
+ *   loss).
+ * - `authorRef` — REQUIRED. Identifier of the author resolved by the
+ *   consumer's author registry (typically a `src/content/authors/<ref>.ts`
+ *   file). Brand keeps it distinct from page/section refs.
+ * - `tags` — REQUIRED, possibly empty. Lowercase kebab-case tag
+ *   identifiers. Drives `og:article:tag` and the listing-page facets.
+ * - `coverImageUrl` — OPTIONAL. CDN URL for the blog post hero image
+ *   and `og:image`.
+ *
+ * **Why a separate file from the page-manifest**: a blog post is NOT
+ * a `WebsitePageManifest` (no React `pageComponent` to mount — the
+ * MDX file IS the content). The Astro adapter emits one MDX route
+ * per post via `content collections`, with `BlogPostFrontmatter`
+ * driving the route generation and the SEO emission.
+ */
+const _BlogPostSlugSchema = z
+    .string()
+    .min(1, { error: 'BlogPostSlug must not be empty' })
+    .max(96, { error: 'BlogPostSlug must be at most 96 characters' })
+    .regex(/^[a-z][a-z0-9-]*$/, { error: 'BlogPostSlug must be lowercase kebab-case starting with a letter' })
+    .brand();
+export const BlogPostSlugSchema = _BlogPostSlugSchema;
+const _BlogAuthorRefSchema = z
+    .string()
+    .min(1, { error: 'BlogAuthorRef must not be empty' })
+    .max(64, { error: 'BlogAuthorRef must be at most 64 characters' })
+    .regex(/^[a-z][a-z0-9-]*$/, { error: 'BlogAuthorRef must be lowercase kebab-case starting with a letter' })
+    .brand();
+export const BlogAuthorRefSchema = _BlogAuthorRefSchema;
+const _BlogPostTagSchema = z
+    .string()
+    .min(1, { error: 'BlogPostTag must not be empty' })
+    .max(48, { error: 'BlogPostTag must be at most 48 characters' })
+    .regex(/^[a-z][a-z0-9-]*$/, { error: 'BlogPostTag must be lowercase kebab-case starting with a letter' })
+    .brand();
+export const BlogPostTagSchema = _BlogPostTagSchema;
+const _BlogPostFrontmatterSchema = z.object({
+    title: z.string().min(1, { error: 'title must not be empty' }).max(200, { error: 'title must be at most 200 characters' }),
+    summary: z.string().min(1, { error: 'summary must not be empty' }).max(400, { error: 'summary must be at most 400 characters' }),
+    slug: _BlogPostSlugSchema,
+    locale: z.enum(AvailableLanguage),
+    publishedAt: z.iso.datetime({ error: 'publishedAt must be an ISO-8601 datetime string' }),
+    authorRef: _BlogAuthorRefSchema,
+    tags: z.array(_BlogPostTagSchema),
+    coverImageUrl: z.url({ error: 'coverImageUrl must be a valid URL' }).optional(),
+});
+export const BlogPostFrontmatterSchema = _BlogPostFrontmatterSchema;
+/** @wildo_source:part:end saas.website.blog.frontmatter */
+//# sourceMappingURL=blog-post-frontmatter.shared.schemas.js.map

package/dist/esm/schemas/blog/blog-post-frontmatter.shared.schemas.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"blog-post-frontmatter.shared.schemas.js","sourceRoot":"","sources":["../../../../../src/schemas/blog/blog-post-frontmatter.shared.schemas.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB,OAAO,EAAE,iBAAiB,EAAE,MAAM,sCAAsC,CAAC;AAEzE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgDG;AACH,MAAM,mBAAmB,GAAG,CAAC;KAC1B,MAAM,EAAE;KACR,GAAG,CAAC,CAAC,EAAE,EAAE,KAAK,EAAE,gCAAgC,EAAE,CAAC;KACnD,GAAG,CAAC,EAAE,EAAE,EAAE,KAAK,EAAE,4CAA4C,EAAE,CAAC;KAChE,KAAK,CACJ,mBAAmB,EACnB,EAAE,KAAK,EAAE,kEAAkE,EAAE,CAC9E;KACA,KAAK,EAAkB,CAAC;AAE3B,MAAM,CAAC,MAAM,kBAAkB,GAA+B,mBAAmB,CAAC;AAIlF,MAAM,oBAAoB,GAAG,CAAC;KAC3B,MAAM,EAAE;KACR,GAAG,CAAC,CAAC,EAAE,EAAE,KAAK,EAAE,iCAAiC,EAAE,CAAC;KACpD,GAAG,CAAC,EAAE,EAAE,EAAE,KAAK,EAAE,6CAA6C,EAAE,CAAC;KACjE,KAAK,CACJ,mBAAmB,EACnB,EAAE,KAAK,EAAE,mEAAmE,EAAE,CAC/E;KACA,KAAK,EAAmB,CAAC;AAE5B,MAAM,CAAC,MAAM,mBAAmB,GAAgC,oBAAoB,CAAC;AAIrF,MAAM,kBAAkB,GAAG,CAAC;KACzB,MAAM,EAAE;KACR,GAAG,CAAC,CAAC,EAAE,EAAE,KAAK,EAAE,+BAA+B,EAAE,CAAC;KAClD,GAAG,CAAC,EAAE,EAAE,EAAE,KAAK,EAAE,2CAA2C,EAAE,CAAC;KAC/D,KAAK,CACJ,mBAAmB,EACnB,EAAE,KAAK,EAAE,iEAAiE,EAAE,CAC7E;KACA,KAAK,EAAiB,CAAC;AAE1B,MAAM,CAAC,MAAM,iBAAiB,GAA8B,kBAAkB,CAAC;AAI/E,MAAM,0BAA0B,GAAG,CAAC,CAAC,MAAM,CAAC;IAC1C,KAAK,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,EAAE,EAAE,KAAK,EAAE,yBAAyB,EAAE,CAAC,CAAC,GAAG,CAAC,GAAG,EAAE,EAAE,KAAK,EAAE,sCAAsC,EAAE,CAAC;IAC1H,OAAO,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,EAAE,EAAE,KAAK,EAAE,2BAA2B,EAAE,CAAC,CAAC,GAAG,CAAC,GAAG,EAAE,EAAE,KAAK,EAAE,wCAAwC,EAAE,CAAC;IAChI,IAAI,EAAE,mBAAmB;IACzB,MAAM,EAAE,CAAC,CAAC,IAAI,CAAC,iBAAiB,CAAC;IACjC,WAAW,EAAE,CAAC,CAAC,GAAG,CAAC,QAAQ,CAAC,EAAE,KAAK,EAAE,iDAAiD,EAAE,CAAC;IACzF,SAAS,EAAE,oBAAoB;IAC/B,IAAI,EAAE,CAAC,CAAC,KAAK,CAAC,kBAAkB,CAAC;IACjC,aAAa,EAAE,CAAC,CAAC,GAAG,CAAC,EAAE,KAAK,EAAE,mCAAmC,EAAE,CAAC,CAAC,QAAQ,EAAE;CAChF,CAAC,CAAC;AAEH,MAAM,CAAC,MAAM,yBAAyB,GACpC,0BAA0B,CAAC;AAG7B,2DAA2D","sourcesContent":["import { z } from 'zod';\n\nimport { AvailableLanguage } from '@wildo-ai/saas-models/public-runtime';\n\n/**\n * @wildo_source:part:start saas.website.blog.frontmatter facet:layer:shared facet:family:website\n *\n * `BlogPostFrontmatter` — the YAML frontmatter contract every blog\n * post MDX file under `examples/<app>/website/src/content/blog/<locale>/`\n * MUST satisfy.\n *\n * **Q16=B context**: blogs are authored as full per-locale MDX files\n * (one MDX per (slug, locale) pair), NOT as label-pack-keyed content.\n * The frontmatter therefore carries strings directly (`title`,\n * `summary`) rather than label keys — there is no shared\n * label-pack-driven authoring surface for blog content. This is\n * intentional: blog copy is long-form and locale-divergent; forcing\n * it through a structural label-pack would either inflate the pack\n * or fragment the prose.\n *\n * **Field rationale**:\n *\n * - `title` — REQUIRED. Renders into `<title>`, `og:title`, and the\n *   in-page H1. Authored as a direct string, deliberately.\n * - `summary` — REQUIRED. Renders into `<meta name=\"description\">`,\n *   `og:description`, and listing-card descriptions. Direct string.\n * - `slug` — REQUIRED. URL slug (lowercase kebab-case). Brand prevents\n *   accidental swap with `WebsitePageRef` (same shape, different role).\n * - `locale` — REQUIRED. The post's locale. Drives the URL prefix\n *   (`/<locale>/blog/<slug>`) and `<html lang>`. Cross-locale\n *   correspondence is established by sharing the `slug` across\n *   per-locale MDX files (e.g. `en/why-context.md` and\n *   `fr/why-context.md` are the same post in two locales).\n * - `publishedAt` — REQUIRED. ISO-8601 date-time string. Renders into\n *   `og:article:published_time` and the listing-card date label.\n *   Stored as string (not `z.coerce.date`) because YAML frontmatter\n *   parsers preserve the original string and the SEO emitters need\n *   the original ISO formatting (no Date.toISOString() round-trip\n *   loss).\n * - `authorRef` — REQUIRED. Identifier of the author resolved by the\n *   consumer's author registry (typically a `src/content/authors/<ref>.ts`\n *   file). Brand keeps it distinct from page/section refs.\n * - `tags` — REQUIRED, possibly empty. Lowercase kebab-case tag\n *   identifiers. Drives `og:article:tag` and the listing-page facets.\n * - `coverImageUrl` — OPTIONAL. CDN URL for the blog post hero image\n *   and `og:image`.\n *\n * **Why a separate file from the page-manifest**: a blog post is NOT\n * a `WebsitePageManifest` (no React `pageComponent` to mount — the\n * MDX file IS the content). The Astro adapter emits one MDX route\n * per post via `content collections`, with `BlogPostFrontmatter`\n * driving the route generation and the SEO emission.\n */\nconst _BlogPostSlugSchema = z\n  .string()\n  .min(1, { error: 'BlogPostSlug must not be empty' })\n  .max(96, { error: 'BlogPostSlug must be at most 96 characters' })\n  .regex(\n    /^[a-z][a-z0-9-]*$/,\n    { error: 'BlogPostSlug must be lowercase kebab-case starting with a letter' },\n  )\n  .brand<'BlogPostSlug'>();\n\nexport const BlogPostSlugSchema: typeof _BlogPostSlugSchema = _BlogPostSlugSchema;\n\nexport type BlogPostSlug = z.infer<typeof _BlogPostSlugSchema>;\n\nconst _BlogAuthorRefSchema = z\n  .string()\n  .min(1, { error: 'BlogAuthorRef must not be empty' })\n  .max(64, { error: 'BlogAuthorRef must be at most 64 characters' })\n  .regex(\n    /^[a-z][a-z0-9-]*$/,\n    { error: 'BlogAuthorRef must be lowercase kebab-case starting with a letter' },\n  )\n  .brand<'BlogAuthorRef'>();\n\nexport const BlogAuthorRefSchema: typeof _BlogAuthorRefSchema = _BlogAuthorRefSchema;\n\nexport type BlogAuthorRef = z.infer<typeof _BlogAuthorRefSchema>;\n\nconst _BlogPostTagSchema = z\n  .string()\n  .min(1, { error: 'BlogPostTag must not be empty' })\n  .max(48, { error: 'BlogPostTag must be at most 48 characters' })\n  .regex(\n    /^[a-z][a-z0-9-]*$/,\n    { error: 'BlogPostTag must be lowercase kebab-case starting with a letter' },\n  )\n  .brand<'BlogPostTag'>();\n\nexport const BlogPostTagSchema: typeof _BlogPostTagSchema = _BlogPostTagSchema;\n\nexport type BlogPostTag = z.infer<typeof _BlogPostTagSchema>;\n\nconst _BlogPostFrontmatterSchema = z.object({\n  title: z.string().min(1, { error: 'title must not be empty' }).max(200, { error: 'title must be at most 200 characters' }),\n  summary: z.string().min(1, { error: 'summary must not be empty' }).max(400, { error: 'summary must be at most 400 characters' }),\n  slug: _BlogPostSlugSchema,\n  locale: z.enum(AvailableLanguage),\n  publishedAt: z.iso.datetime({ error: 'publishedAt must be an ISO-8601 datetime string' }),\n  authorRef: _BlogAuthorRefSchema,\n  tags: z.array(_BlogPostTagSchema),\n  coverImageUrl: z.url({ error: 'coverImageUrl must be a valid URL' }).optional(),\n});\n\nexport const BlogPostFrontmatterSchema: typeof _BlogPostFrontmatterSchema =\n  _BlogPostFrontmatterSchema;\n\nexport type BlogPostFrontmatter = z.infer<typeof _BlogPostFrontmatterSchema>;\n/** @wildo_source:part:end saas.website.blog.frontmatter */\n"]}

package/dist/esm/schemas/design-tokens/website-design-tokens.shared.schemas.d.ts

@@ -0,0 +1,120 @@
+import { z } from 'zod';
+/**
+ * @wildo_source:part:start saas.website.design-tokens.colors facet:layer:shared facet:family:website
+ *
+ * `WebsiteColorTokens` — minimal palette the marketing-site exposes as
+ * CSS custom properties (`--website-color-<token>`) on the
+ * `<WebsitePageLayout>` root.
+ *
+ * **Why a dedicated marketing palette** (vs. reusing
+ * `presets-components-models/design-tokens-config`):
+ *
+ * - The SaaS app's design tokens carry many semantic states (`muted`,
+ *   `destructive`, `ring`, `sidebar-*`, …) that have no marketing-site
+ *   analogue. Forcing the website to consume the full palette would
+ *   leak app-internal semantics into a public surface.
+ * - Marketing pages need *display-grade* colors (heavily branded
+ *   accents, gradient stops, hero-overlay tints) that the SaaS app's
+ *   functional palette deliberately avoids.
+ * - Designers overriding website tokens (Phase 6 dogfood proves this
+ *   path) should not be able to break the SaaS app by editing one
+ *   tailwind.config — the two surfaces stay decoupled.
+ *
+ * **Token format**: every value is a CSS color string. Shape validation
+ * is intentionally permissive (accepts hex, rgb/rgba, hsl/hsla, oklch,
+ * `currentColor`, named colors, CSS variable references) — a strict
+ * color-string regex would reject legitimate values (oklch grammar
+ * alone is ~80 lines) and a malformed-but-syntactically-valid color
+ * fails loudly at render time.
+ *
+ * **What IS strictly enforced**: every value passes `cssSafeValue`,
+ * which rejects the six characters that can break out of a CSS
+ * property declaration (`;`, `{`, `}`, `/*`, `*\/`, newline). See the
+ * `cssSafeValue` JSDoc above for the full threat model.
+ *
+ * **Adding a token**: append the field here using `cssSafeValue(...)`,
+ * document its semantic intent in the JSDoc, and update the matching
+ * CSS-emit helper in Phase 2 (`emitWebsiteColorTokensCss`).
+ */
+declare const _WebsiteColorTokensSchema: z.ZodObject<{
+    background: z.ZodString;
+    foreground: z.ZodString;
+    primary: z.ZodString;
+    primaryForeground: z.ZodString;
+    accent: z.ZodString;
+    accentForeground: z.ZodString;
+    surface: z.ZodString;
+    surfaceForeground: z.ZodString;
+    border: z.ZodString;
+    muted: z.ZodString;
+    mutedForeground: z.ZodString;
+}, z.core.$strip>;
+export declare const WebsiteColorTokensSchema: typeof _WebsiteColorTokensSchema;
+export type WebsiteColorTokens = z.infer<typeof _WebsiteColorTokensSchema>;
+/** @wildo_source:part:end saas.website.design-tokens.colors */
+/**
+ * @wildo_source:part:start saas.website.design-tokens.radius facet:layer:shared facet:family:website
+ *
+ * `WebsiteRadiusTokens` — border-radius scale exposed as
+ * `--website-radius-<token>` CSS variables.
+ *
+ * Marketing radii are intentionally a separate token set from the
+ * SaaS app's radii: the website typically wants larger pill / hero
+ * radii than the app's compact-UI radii. Keeping them separate lets
+ * either surface evolve without coupling.
+ *
+ * Values are CSS length strings (`'0.25rem'`, `'12px'`,
+ * `'9999px'`). Same permissive-shape + strict-CSS-injection
+ * rationale as `WebsiteColorTokens` (every value runs through
+ * `cssSafeValue`).
+ */
+declare const _WebsiteRadiusTokensSchema: z.ZodObject<{
+    none: z.ZodString;
+    sm: z.ZodString;
+    md: z.ZodString;
+    lg: z.ZodString;
+    xl: z.ZodString;
+    full: z.ZodString;
+}, z.core.$strip>;
+export declare const WebsiteRadiusTokensSchema: typeof _WebsiteRadiusTokensSchema;
+export type WebsiteRadiusTokens = z.infer<typeof _WebsiteRadiusTokensSchema>;
+/** @wildo_source:part:end saas.website.design-tokens.radius */
+/**
+ * @wildo_source:part:start saas.website.design-tokens.bundle facet:layer:shared facet:family:website
+ *
+ * `WebsiteDesignTokens` — the complete design-token bundle attached to
+ * `WebsiteRootConfig.designTokens`. Currently colors + radii only
+ * (per plan Phase 1 scope: "WebsiteColorTokensSchema + WebsiteRadiusTokensSchema (only)").
+ *
+ * Future expansions (typography scale, motion tokens, shadow elevation)
+ * will land as additional fields here without breaking the
+ * `WebsiteRootConfig` shape.
+ */
+declare const _WebsiteDesignTokensSchema: z.ZodObject<{
+    colors: z.ZodObject<{
+        background: z.ZodString;
+        foreground: z.ZodString;
+        primary: z.ZodString;
+        primaryForeground: z.ZodString;
+        accent: z.ZodString;
+        accentForeground: z.ZodString;
+        surface: z.ZodString;
+        surfaceForeground: z.ZodString;
+        border: z.ZodString;
+        muted: z.ZodString;
+        mutedForeground: z.ZodString;
+    }, z.core.$strip>;
+    radii: z.ZodObject<{
+        none: z.ZodString;
+        sm: z.ZodString;
+        md: z.ZodString;
+        lg: z.ZodString;
+        xl: z.ZodString;
+        full: z.ZodString;
+    }, z.core.$strip>;
+}, z.core.$strip>;
+export declare const WebsiteDesignTokensSchema: typeof _WebsiteDesignTokensSchema;
+export type WebsiteDesignTokens = z.infer<typeof _WebsiteDesignTokensSchema>;
+export {};
+/** @wildo_source:part:end saas.website.design-tokens.bundle */
+//# sourceMappingURL=website-design-tokens.shared.schemas.d.ts.map

package/dist/esm/schemas/design-tokens/website-design-tokens.shared.schemas.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"website-design-tokens.shared.schemas.d.ts","sourceRoot":"","sources":["../../../../../src/schemas/design-tokens/website-design-tokens.shared.schemas.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AA4DxB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAoCG;AACH,QAAA,MAAM,yBAAyB;;;;;;;;;;;;iBAY7B,CAAC;AAEH,eAAO,MAAM,wBAAwB,EAAE,OAAO,yBAAqD,CAAC;AAEpG,MAAM,MAAM,kBAAkB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,yBAAyB,CAAC,CAAC;AAC3E,+DAA+D;AAE/D;;;;;;;;;;;;;;;GAeG;AACH,QAAA,MAAM,0BAA0B;;;;;;;iBAO9B,CAAC;AAEH,eAAO,MAAM,yBAAyB,EAAE,OAAO,0BAAuD,CAAC;AAEvG,MAAM,MAAM,mBAAmB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,0BAA0B,CAAC,CAAC;AAC7E,+DAA+D;AAE/D;;;;;;;;;;GAUG;AACH,QAAA,MAAM,0BAA0B;;;;;;;;;;;;;;;;;;;;;;iBAG9B,CAAC;AAEH,eAAO,MAAM,yBAAyB,EAAE,OAAO,0BAAuD,CAAC;AAEvG,MAAM,MAAM,mBAAmB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,0BAA0B,CAAC,CAAC;;AAC7E,+DAA+D"}

package/dist/esm/schemas/design-tokens/website-design-tokens.shared.schemas.js

@@ -0,0 +1,152 @@
+import { z } from 'zod';
+/**
+ * CSS-injection-safe value validator shared by every design-token field.
+ *
+ * **Threat model** — TWO escape surfaces, BOTH covered:
+ *
+ *   1. CSS *declaration* break-out (Phase 6 third audit fix H-α):
+ *      the renderer `renderWebsiteDesignTokensCss` interpolates token
+ *      values **raw** into a `:root { --website-<group>-<token>: <value>; }`
+ *      block. A value containing any of `;`, `}`, `{`, `/*`, `*\/`, or a
+ *      newline can break out of the property declaration and inject
+ *      arbitrary CSS — at minimum a config typo silently corrupts the
+ *      page; at worst a malicious or untrusted config author injects a
+ *      `body { display: none; }` rule that blanks the entire site.
+ *
+ *   2. HTML *style-element* break-out (Phase 6 fourth audit fix H-Χ):
+ *      the rendered `:root { ... }` block is itself wrapped in an inline
+ *      `<style>…</style>` element by the head renderer. Per the HTML spec
+ *      the `<style>` element is a *raw-text* element — its only
+ *      terminator is the literal sequence `</style`. A token value
+ *      containing `<` (or, for symmetry, `>`) can therefore close the
+ *      `<style>` element early and follow up with `<svg onload=alert(1)>`
+ *      or any other HTML / JS payload, which the H-α deny-list (which
+ *      did NOT forbid `<` / `>`) failed to catch. CSS values legitimately
+ *      need NEITHER `<` NOR `>` (no CSS grammar uses them — no color,
+ *      length, variable reference, calc expression, or functional
+ *      notation does), so denying both is conservative and correct.
+ *
+ * **Why validate at the schema layer (not inside the renderer)**:
+ *   1. Fail at config load (build-time / boot-time), not at every
+ *      `<head>` render — a malformed token surfaces in the schema-parse
+ *      error message instead of silently emitting broken CSS / HTML.
+ *   2. Single source of truth — every field that flows into the
+ *      `<style>`-wrapped CSS block gets the same guard (impossible to
+ *      add a future token field that bypasses the renderer's escape
+ *      pass).
+ *   3. The renderer stays a simple interpolator, which makes its own
+ *      audit surface trivially small.
+ *
+ * **Why a `.refine` over a strict color-string regex**: colors accept
+ * `currentColor`, named colors, `var(--foo)` references, oklch
+ * functional notation, etc. — a strict positive grammar is ~80 lines
+ * and high-maintenance. A negative deny-list of the eight characters
+ * that are LITERALLY the only ones that can break out of either the CSS
+ * property declaration OR the wrapping `<style>` element is small,
+ * complete, and obviously correct.
+ */
+const CSS_INJECTION_FORBIDDEN_PATTERN = /[;{}<>\n\r]|\/\*|\*\//;
+const cssSafeValue = (fieldName) => z
+    .string()
+    .min(1, { error: `${fieldName} must not be empty` })
+    .refine((value) => !CSS_INJECTION_FORBIDDEN_PATTERN.test(value), {
+    error: `${fieldName} must not contain CSS-injection or HTML break-out ` +
+        `metacharacters (; { } < > /* */ newline) — token values are ` +
+        `interpolated raw into <style>:root { --website-...: <value>; }</style>`,
+});
+/**
+ * @wildo_source:part:start saas.website.design-tokens.colors facet:layer:shared facet:family:website
+ *
+ * `WebsiteColorTokens` — minimal palette the marketing-site exposes as
+ * CSS custom properties (`--website-color-<token>`) on the
+ * `<WebsitePageLayout>` root.
+ *
+ * **Why a dedicated marketing palette** (vs. reusing
+ * `presets-components-models/design-tokens-config`):
+ *
+ * - The SaaS app's design tokens carry many semantic states (`muted`,
+ *   `destructive`, `ring`, `sidebar-*`, …) that have no marketing-site
+ *   analogue. Forcing the website to consume the full palette would
+ *   leak app-internal semantics into a public surface.
+ * - Marketing pages need *display-grade* colors (heavily branded
+ *   accents, gradient stops, hero-overlay tints) that the SaaS app's
+ *   functional palette deliberately avoids.
+ * - Designers overriding website tokens (Phase 6 dogfood proves this
+ *   path) should not be able to break the SaaS app by editing one
+ *   tailwind.config — the two surfaces stay decoupled.
+ *
+ * **Token format**: every value is a CSS color string. Shape validation
+ * is intentionally permissive (accepts hex, rgb/rgba, hsl/hsla, oklch,
+ * `currentColor`, named colors, CSS variable references) — a strict
+ * color-string regex would reject legitimate values (oklch grammar
+ * alone is ~80 lines) and a malformed-but-syntactically-valid color
+ * fails loudly at render time.
+ *
+ * **What IS strictly enforced**: every value passes `cssSafeValue`,
+ * which rejects the six characters that can break out of a CSS
+ * property declaration (`;`, `{`, `}`, `/*`, `*\/`, newline). See the
+ * `cssSafeValue` JSDoc above for the full threat model.
+ *
+ * **Adding a token**: append the field here using `cssSafeValue(...)`,
+ * document its semantic intent in the JSDoc, and update the matching
+ * CSS-emit helper in Phase 2 (`emitWebsiteColorTokensCss`).
+ */
+const _WebsiteColorTokensSchema = z.object({
+    background: cssSafeValue('background color'),
+    foreground: cssSafeValue('foreground color'),
+    primary: cssSafeValue('primary color'),
+    primaryForeground: cssSafeValue('primaryForeground color'),
+    accent: cssSafeValue('accent color'),
+    accentForeground: cssSafeValue('accentForeground color'),
+    surface: cssSafeValue('surface color'),
+    surfaceForeground: cssSafeValue('surfaceForeground color'),
+    border: cssSafeValue('border color'),
+    muted: cssSafeValue('muted color'),
+    mutedForeground: cssSafeValue('mutedForeground color'),
+});
+export const WebsiteColorTokensSchema = _WebsiteColorTokensSchema;
+/** @wildo_source:part:end saas.website.design-tokens.colors */
+/**
+ * @wildo_source:part:start saas.website.design-tokens.radius facet:layer:shared facet:family:website
+ *
+ * `WebsiteRadiusTokens` — border-radius scale exposed as
+ * `--website-radius-<token>` CSS variables.
+ *
+ * Marketing radii are intentionally a separate token set from the
+ * SaaS app's radii: the website typically wants larger pill / hero
+ * radii than the app's compact-UI radii. Keeping them separate lets
+ * either surface evolve without coupling.
+ *
+ * Values are CSS length strings (`'0.25rem'`, `'12px'`,
+ * `'9999px'`). Same permissive-shape + strict-CSS-injection
+ * rationale as `WebsiteColorTokens` (every value runs through
+ * `cssSafeValue`).
+ */
+const _WebsiteRadiusTokensSchema = z.object({
+    none: cssSafeValue('none radius'),
+    sm: cssSafeValue('sm radius'),
+    md: cssSafeValue('md radius'),
+    lg: cssSafeValue('lg radius'),
+    xl: cssSafeValue('xl radius'),
+    full: cssSafeValue('full radius'),
+});
+export const WebsiteRadiusTokensSchema = _WebsiteRadiusTokensSchema;
+/** @wildo_source:part:end saas.website.design-tokens.radius */
+/**
+ * @wildo_source:part:start saas.website.design-tokens.bundle facet:layer:shared facet:family:website
+ *
+ * `WebsiteDesignTokens` — the complete design-token bundle attached to
+ * `WebsiteRootConfig.designTokens`. Currently colors + radii only
+ * (per plan Phase 1 scope: "WebsiteColorTokensSchema + WebsiteRadiusTokensSchema (only)").
+ *
+ * Future expansions (typography scale, motion tokens, shadow elevation)
+ * will land as additional fields here without breaking the
+ * `WebsiteRootConfig` shape.
+ */
+const _WebsiteDesignTokensSchema = z.object({
+    colors: _WebsiteColorTokensSchema,
+    radii: _WebsiteRadiusTokensSchema,
+});
+export const WebsiteDesignTokensSchema = _WebsiteDesignTokensSchema;
+/** @wildo_source:part:end saas.website.design-tokens.bundle */
+//# sourceMappingURL=website-design-tokens.shared.schemas.js.map

package/dist/esm/schemas/design-tokens/website-design-tokens.shared.schemas.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"website-design-tokens.shared.schemas.js","sourceRoot":"","sources":["../../../../../src/schemas/design-tokens/website-design-tokens.shared.schemas.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6CG;AACH,MAAM,+BAA+B,GAAG,uBAAuB,CAAC;AAChE,MAAM,YAAY,GAAG,CAAC,SAAiB,EAAe,EAAE,CACtD,CAAC;KACE,MAAM,EAAE;KACR,GAAG,CAAC,CAAC,EAAE,EAAE,KAAK,EAAE,GAAG,SAAS,oBAAoB,EAAE,CAAC;KACnD,MAAM,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,CAAC,+BAA+B,CAAC,IAAI,CAAC,KAAK,CAAC,EAAE;IAC/D,KAAK,EACH,GAAG,SAAS,oDAAoD;QAChE,8DAA8D;QAC9D,wEAAwE;CAC3E,CAA2B,CAAC;AAEjC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAoCG;AACH,MAAM,yBAAyB,GAAG,CAAC,CAAC,MAAM,CAAC;IACzC,UAAU,EAAE,YAAY,CAAC,kBAAkB,CAAC;IAC5C,UAAU,EAAE,YAAY,CAAC,kBAAkB,CAAC;IAC5C,OAAO,EAAE,YAAY,CAAC,eAAe,CAAC;IACtC,iBAAiB,EAAE,YAAY,CAAC,yBAAyB,CAAC;IAC1D,MAAM,EAAE,YAAY,CAAC,cAAc,CAAC;IACpC,gBAAgB,EAAE,YAAY,CAAC,wBAAwB,CAAC;IACxD,OAAO,EAAE,YAAY,CAAC,eAAe,CAAC;IACtC,iBAAiB,EAAE,YAAY,CAAC,yBAAyB,CAAC;IAC1D,MAAM,EAAE,YAAY,CAAC,cAAc,CAAC;IACpC,KAAK,EAAE,YAAY,CAAC,aAAa,CAAC;IAClC,eAAe,EAAE,YAAY,CAAC,uBAAuB,CAAC;CACvD,CAAC,CAAC;AAEH,MAAM,CAAC,MAAM,wBAAwB,GAAqC,yBAAyB,CAAC;AAGpG,+DAA+D;AAE/D;;;;;;;;;;;;;;;GAeG;AACH,MAAM,0BAA0B,GAAG,CAAC,CAAC,MAAM,CAAC;IAC1C,IAAI,EAAE,YAAY,CAAC,aAAa,CAAC;IACjC,EAAE,EAAE,YAAY,CAAC,WAAW,CAAC;IAC7B,EAAE,EAAE,YAAY,CAAC,WAAW,CAAC;IAC7B,EAAE,EAAE,YAAY,CAAC,WAAW,CAAC;IAC7B,EAAE,EAAE,YAAY,CAAC,WAAW,CAAC;IAC7B,IAAI,EAAE,YAAY,CAAC,aAAa,CAAC;CAClC,CAAC,CAAC;AAEH,MAAM,CAAC,MAAM,yBAAyB,GAAsC,0BAA0B,CAAC;AAGvG,+DAA+D;AAE/D;;;;;;;;;;GAUG;AACH,MAAM,0BAA0B,GAAG,CAAC,CAAC,MAAM,CAAC;IAC1C,MAAM,EAAE,yBAAyB;IACjC,KAAK,EAAE,0BAA0B;CAClC,CAAC,CAAC;AAEH,MAAM,CAAC,MAAM,yBAAyB,GAAsC,0BAA0B,CAAC;AAGvG,+DAA+D","sourcesContent":["import { z } from 'zod';\n\n/**\n * CSS-injection-safe value validator shared by every design-token field.\n *\n * **Threat model** — TWO escape surfaces, BOTH covered:\n *\n *   1. CSS *declaration* break-out (Phase 6 third audit fix H-α):\n *      the renderer `renderWebsiteDesignTokensCss` interpolates token\n *      values **raw** into a `:root { --website-<group>-<token>: <value>; }`\n *      block. A value containing any of `;`, `}`, `{`, `/*`, `*\\/`, or a\n *      newline can break out of the property declaration and inject\n *      arbitrary CSS — at minimum a config typo silently corrupts the\n *      page; at worst a malicious or untrusted config author injects a\n *      `body { display: none; }` rule that blanks the entire site.\n *\n *   2. HTML *style-element* break-out (Phase 6 fourth audit fix H-Χ):\n *      the rendered `:root { ... }` block is itself wrapped in an inline\n *      `<style>…</style>` element by the head renderer. Per the HTML spec\n *      the `<style>` element is a *raw-text* element — its only\n *      terminator is the literal sequence `</style`. A token value\n *      containing `<` (or, for symmetry, `>`) can therefore close the\n *      `<style>` element early and follow up with `<svg onload=alert(1)>`\n *      or any other HTML / JS payload, which the H-α deny-list (which\n *      did NOT forbid `<` / `>`) failed to catch. CSS values legitimately\n *      need NEITHER `<` NOR `>` (no CSS grammar uses them — no color,\n *      length, variable reference, calc expression, or functional\n *      notation does), so denying both is conservative and correct.\n *\n * **Why validate at the schema layer (not inside the renderer)**:\n *   1. Fail at config load (build-time / boot-time), not at every\n *      `<head>` render — a malformed token surfaces in the schema-parse\n *      error message instead of silently emitting broken CSS / HTML.\n *   2. Single source of truth — every field that flows into the\n *      `<style>`-wrapped CSS block gets the same guard (impossible to\n *      add a future token field that bypasses the renderer's escape\n *      pass).\n *   3. The renderer stays a simple interpolator, which makes its own\n *      audit surface trivially small.\n *\n * **Why a `.refine` over a strict color-string regex**: colors accept\n * `currentColor`, named colors, `var(--foo)` references, oklch\n * functional notation, etc. — a strict positive grammar is ~80 lines\n * and high-maintenance. A negative deny-list of the eight characters\n * that are LITERALLY the only ones that can break out of either the CSS\n * property declaration OR the wrapping `<style>` element is small,\n * complete, and obviously correct.\n */\nconst CSS_INJECTION_FORBIDDEN_PATTERN = /[;{}<>\\n\\r]|\\/\\*|\\*\\//;\nconst cssSafeValue = (fieldName: string): z.ZodString =>\n  z\n    .string()\n    .min(1, { error: `${fieldName} must not be empty` })\n    .refine((value) => !CSS_INJECTION_FORBIDDEN_PATTERN.test(value), {\n      error:\n        `${fieldName} must not contain CSS-injection or HTML break-out ` +\n        `metacharacters (; { } < > /* */ newline) — token values are ` +\n        `interpolated raw into <style>:root { --website-...: <value>; }</style>`,\n    }) as unknown as z.ZodString;\n\n/**\n * @wildo_source:part:start saas.website.design-tokens.colors facet:layer:shared facet:family:website\n *\n * `WebsiteColorTokens` — minimal palette the marketing-site exposes as\n * CSS custom properties (`--website-color-<token>`) on the\n * `<WebsitePageLayout>` root.\n *\n * **Why a dedicated marketing palette** (vs. reusing\n * `presets-components-models/design-tokens-config`):\n *\n * - The SaaS app's design tokens carry many semantic states (`muted`,\n *   `destructive`, `ring`, `sidebar-*`, …) that have no marketing-site\n *   analogue. Forcing the website to consume the full palette would\n *   leak app-internal semantics into a public surface.\n * - Marketing pages need *display-grade* colors (heavily branded\n *   accents, gradient stops, hero-overlay tints) that the SaaS app's\n *   functional palette deliberately avoids.\n * - Designers overriding website tokens (Phase 6 dogfood proves this\n *   path) should not be able to break the SaaS app by editing one\n *   tailwind.config — the two surfaces stay decoupled.\n *\n * **Token format**: every value is a CSS color string. Shape validation\n * is intentionally permissive (accepts hex, rgb/rgba, hsl/hsla, oklch,\n * `currentColor`, named colors, CSS variable references) — a strict\n * color-string regex would reject legitimate values (oklch grammar\n * alone is ~80 lines) and a malformed-but-syntactically-valid color\n * fails loudly at render time.\n *\n * **What IS strictly enforced**: every value passes `cssSafeValue`,\n * which rejects the six characters that can break out of a CSS\n * property declaration (`;`, `{`, `}`, `/*`, `*\\/`, newline). See the\n * `cssSafeValue` JSDoc above for the full threat model.\n *\n * **Adding a token**: append the field here using `cssSafeValue(...)`,\n * document its semantic intent in the JSDoc, and update the matching\n * CSS-emit helper in Phase 2 (`emitWebsiteColorTokensCss`).\n */\nconst _WebsiteColorTokensSchema = z.object({\n  background: cssSafeValue('background color'),\n  foreground: cssSafeValue('foreground color'),\n  primary: cssSafeValue('primary color'),\n  primaryForeground: cssSafeValue('primaryForeground color'),\n  accent: cssSafeValue('accent color'),\n  accentForeground: cssSafeValue('accentForeground color'),\n  surface: cssSafeValue('surface color'),\n  surfaceForeground: cssSafeValue('surfaceForeground color'),\n  border: cssSafeValue('border color'),\n  muted: cssSafeValue('muted color'),\n  mutedForeground: cssSafeValue('mutedForeground color'),\n});\n\nexport const WebsiteColorTokensSchema: typeof _WebsiteColorTokensSchema = _WebsiteColorTokensSchema;\n\nexport type WebsiteColorTokens = z.infer<typeof _WebsiteColorTokensSchema>;\n/** @wildo_source:part:end saas.website.design-tokens.colors */\n\n/**\n * @wildo_source:part:start saas.website.design-tokens.radius facet:layer:shared facet:family:website\n *\n * `WebsiteRadiusTokens` — border-radius scale exposed as\n * `--website-radius-<token>` CSS variables.\n *\n * Marketing radii are intentionally a separate token set from the\n * SaaS app's radii: the website typically wants larger pill / hero\n * radii than the app's compact-UI radii. Keeping them separate lets\n * either surface evolve without coupling.\n *\n * Values are CSS length strings (`'0.25rem'`, `'12px'`,\n * `'9999px'`). Same permissive-shape + strict-CSS-injection\n * rationale as `WebsiteColorTokens` (every value runs through\n * `cssSafeValue`).\n */\nconst _WebsiteRadiusTokensSchema = z.object({\n  none: cssSafeValue('none radius'),\n  sm: cssSafeValue('sm radius'),\n  md: cssSafeValue('md radius'),\n  lg: cssSafeValue('lg radius'),\n  xl: cssSafeValue('xl radius'),\n  full: cssSafeValue('full radius'),\n});\n\nexport const WebsiteRadiusTokensSchema: typeof _WebsiteRadiusTokensSchema = _WebsiteRadiusTokensSchema;\n\nexport type WebsiteRadiusTokens = z.infer<typeof _WebsiteRadiusTokensSchema>;\n/** @wildo_source:part:end saas.website.design-tokens.radius */\n\n/**\n * @wildo_source:part:start saas.website.design-tokens.bundle facet:layer:shared facet:family:website\n *\n * `WebsiteDesignTokens` — the complete design-token bundle attached to\n * `WebsiteRootConfig.designTokens`. Currently colors + radii only\n * (per plan Phase 1 scope: \"WebsiteColorTokensSchema + WebsiteRadiusTokensSchema (only)\").\n *\n * Future expansions (typography scale, motion tokens, shadow elevation)\n * will land as additional fields here without breaking the\n * `WebsiteRootConfig` shape.\n */\nconst _WebsiteDesignTokensSchema = z.object({\n  colors: _WebsiteColorTokensSchema,\n  radii: _WebsiteRadiusTokensSchema,\n});\n\nexport const WebsiteDesignTokensSchema: typeof _WebsiteDesignTokensSchema = _WebsiteDesignTokensSchema;\n\nexport type WebsiteDesignTokens = z.infer<typeof _WebsiteDesignTokensSchema>;\n/** @wildo_source:part:end saas.website.design-tokens.bundle */\n"]}

package/dist/esm/schemas/label-keys/website-label-key.schemas.d.ts

@@ -0,0 +1,73 @@
+import { z } from 'zod';
+/**
+ * @wildo_source:part:start saas.website.label-keys.format facet:layer:shared facet:family:i18n
+ *
+ * `WebsiteLabelKey` — branded i18n key for marketing-site copy.
+ *
+ * **Format**: `website.<pageRef>.<sectionRef>.<slotPath>`
+ *
+ * - `website.` — fixed namespace prefix that disambiguates marketing-site
+ *   labels from app i18n keys (`labels.`, `errors.`, `notifications.`).
+ *   Marketing-site label packs ship as a separate file per locale
+ *   (`website/src/i18n/<locale>.json`) so they never bloat the SaaS app
+ *   bundle.
+ * - `<pageRef>` — kebab-case page ref (validated independently by
+ *   `WebsitePageRefSchema`).
+ * - `<sectionRef>` — kebab-case section ref (validated independently by
+ *   `WebsiteSectionRefSchema`).
+ * - `<slotPath>` — leaf identifier the section consumes via
+ *   `useWebsiteLabel('<slotPath>')` (Phase 2). Allows dots for nested
+ *   structures (`'cta.primary'`), brackets for indexed array slots
+ *   (`'tiers[0].name'`), and hyphens for multi-word leaves.
+ *
+ * **Examples**:
+ *   - `website.landing.hero.headline`
+ *   - `website.landing.hero.cta.primary`
+ *   - `website.pricing.tiers.tiers[0].name`
+ *   - `website.contact.form.field.email-placeholder`
+ *
+ * **Why a brand**: prevents the "label key as bare string" failure mode
+ * where a typo in `'webiste.landing.hero.headline'` (note the typo) silently
+ * resolves to undefined at runtime. Sections must accept
+ * `WebsiteLabelKey`-typed props; consumers go through
+ * `WebsiteLabelKeySchema.parse(...)` (or the manifest's `metaLabelKeys`
+ * fields, which are typed against this schema) before a string flows into
+ * label resolution.
+ *
+ * **Why a single regex**: the three nested refs (`page`, `section`, `slot`)
+ * are validated separately by their own schemas inside the `defineWebsiteSection`
+ * factory and `WebsitePageManifestSchema`. This schema's job is to validate
+ * a fully-composed key — typically inserted directly into JSX as a string
+ * literal — without re-parsing the parts.
+ */
+declare const _WebsiteLabelKeySchema: z.core.$ZodBranded<z.ZodString, "WebsiteLabelKey", "out">;
+export declare const WebsiteLabelKeySchema: typeof _WebsiteLabelKeySchema;
+export type WebsiteLabelKey = z.infer<typeof _WebsiteLabelKeySchema>;
+/** @wildo_source:part:end saas.website.label-keys.format */
+/**
+ * @wildo_source:part:start saas.website.label-keys.compose-helper facet:layer:shared facet:family:i18n
+ *
+ * `composeWebsiteLabelKey` — pure helper that composes a `WebsiteLabelKey`
+ * from its three parts. Used by `useWebsiteLabel` (Phase 2) and by the
+ * label-pack validator to materialize the keys a section commits to.
+ *
+ * Returns the key as a parsed `WebsiteLabelKey` (brand applied), throwing
+ * if the composed string fails the format check (defensive guard against
+ * stale refs / inconsistent slot paths leaking past type-system narrowing).
+ *
+ * @example
+ *   composeWebsiteLabelKey({
+ *     pageRef: WebsitePageRefSchema.parse('landing'),
+ *     sectionRef: WebsiteSectionRefSchema.parse('hero'),
+ *     slotPath: 'headline',
+ *   });
+ *   // -> WebsiteLabelKey ("website.landing.hero.headline")
+ */
+export declare function composeWebsiteLabelKey(parts: {
+    pageRef: string;
+    sectionRef: string;
+    slotPath: string;
+}): WebsiteLabelKey;
+export {};
+/** @wildo_source:part:end saas.website.label-keys.compose-helper */
+//# sourceMappingURL=website-label-key.schemas.d.ts.map

package/dist/esm/schemas/label-keys/website-label-key.schemas.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"website-label-key.schemas.d.ts","sourceRoot":"","sources":["../../../../../src/schemas/label-keys/website-label-key.schemas.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAwCG;AACH,QAAA,MAAM,sBAAsB,2DAWC,CAAC;AAE9B,eAAO,MAAM,qBAAqB,EAAE,OAAO,sBAA+C,CAAC;AAE3F,MAAM,MAAM,eAAe,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,sBAAsB,CAAC,CAAC;AACrE,4DAA4D;AAE5D;;;;;;;;;;;;;;;;;;GAkBG;AACH,wBAAgB,sBAAsB,CAAC,KAAK,EAAE;IAC5C,OAAO,EAAE,MAAM,CAAC;IAChB,UAAU,EAAE,MAAM,CAAC;IACnB,QAAQ,EAAE,MAAM,CAAC;CAClB,GAAG,eAAe,CAElB;;AACD,oEAAoE"}

package/dist/esm/schemas/label-keys/website-label-key.schemas.js

@@ -0,0 +1,76 @@
+import { z } from 'zod';
+/**
+ * @wildo_source:part:start saas.website.label-keys.format facet:layer:shared facet:family:i18n
+ *
+ * `WebsiteLabelKey` — branded i18n key for marketing-site copy.
+ *
+ * **Format**: `website.<pageRef>.<sectionRef>.<slotPath>`
+ *
+ * - `website.` — fixed namespace prefix that disambiguates marketing-site
+ *   labels from app i18n keys (`labels.`, `errors.`, `notifications.`).
+ *   Marketing-site label packs ship as a separate file per locale
+ *   (`website/src/i18n/<locale>.json`) so they never bloat the SaaS app
+ *   bundle.
+ * - `<pageRef>` — kebab-case page ref (validated independently by
+ *   `WebsitePageRefSchema`).
+ * - `<sectionRef>` — kebab-case section ref (validated independently by
+ *   `WebsiteSectionRefSchema`).
+ * - `<slotPath>` — leaf identifier the section consumes via
+ *   `useWebsiteLabel('<slotPath>')` (Phase 2). Allows dots for nested
+ *   structures (`'cta.primary'`), brackets for indexed array slots
+ *   (`'tiers[0].name'`), and hyphens for multi-word leaves.
+ *
+ * **Examples**:
+ *   - `website.landing.hero.headline`
+ *   - `website.landing.hero.cta.primary`
+ *   - `website.pricing.tiers.tiers[0].name`
+ *   - `website.contact.form.field.email-placeholder`
+ *
+ * **Why a brand**: prevents the "label key as bare string" failure mode
+ * where a typo in `'webiste.landing.hero.headline'` (note the typo) silently
+ * resolves to undefined at runtime. Sections must accept
+ * `WebsiteLabelKey`-typed props; consumers go through
+ * `WebsiteLabelKeySchema.parse(...)` (or the manifest's `metaLabelKeys`
+ * fields, which are typed against this schema) before a string flows into
+ * label resolution.
+ *
+ * **Why a single regex**: the three nested refs (`page`, `section`, `slot`)
+ * are validated separately by their own schemas inside the `defineWebsiteSection`
+ * factory and `WebsitePageManifestSchema`. This schema's job is to validate
+ * a fully-composed key — typically inserted directly into JSX as a string
+ * literal — without re-parsing the parts.
+ */
+const _WebsiteLabelKeySchema = z
+    .string()
+    .min(10, { error: 'WebsiteLabelKey is too short (must include website.<page>.<section>.<slot>)' })
+    .max(256, { error: 'WebsiteLabelKey must be at most 256 characters' })
+    .regex(/^website\.[a-z][a-z0-9-]*\.[a-z][a-z0-9-]*\.[a-zA-Z0-9.\[\]_-]+$/, {
+    error: 'WebsiteLabelKey must match `website.<page>.<section>.<slot>` where page/section are kebab-case and slot allows dot/bracket/hyphen/underscore (e.g. "website.landing.hero.headline")',
+})
+    .brand();
+export const WebsiteLabelKeySchema = _WebsiteLabelKeySchema;
+/** @wildo_source:part:end saas.website.label-keys.format */
+/**
+ * @wildo_source:part:start saas.website.label-keys.compose-helper facet:layer:shared facet:family:i18n
+ *
+ * `composeWebsiteLabelKey` — pure helper that composes a `WebsiteLabelKey`
+ * from its three parts. Used by `useWebsiteLabel` (Phase 2) and by the
+ * label-pack validator to materialize the keys a section commits to.
+ *
+ * Returns the key as a parsed `WebsiteLabelKey` (brand applied), throwing
+ * if the composed string fails the format check (defensive guard against
+ * stale refs / inconsistent slot paths leaking past type-system narrowing).
+ *
+ * @example
+ *   composeWebsiteLabelKey({
+ *     pageRef: WebsitePageRefSchema.parse('landing'),
+ *     sectionRef: WebsiteSectionRefSchema.parse('hero'),
+ *     slotPath: 'headline',
+ *   });
+ *   // -> WebsiteLabelKey ("website.landing.hero.headline")
+ */
+export function composeWebsiteLabelKey(parts) {
+    return WebsiteLabelKeySchema.parse(`website.${parts.pageRef}.${parts.sectionRef}.${parts.slotPath}`);
+}
+/** @wildo_source:part:end saas.website.label-keys.compose-helper */
+//# sourceMappingURL=website-label-key.schemas.js.map

package/dist/esm/schemas/label-keys/website-label-key.schemas.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"website-label-key.schemas.js","sourceRoot":"","sources":["../../../../../src/schemas/label-keys/website-label-key.schemas.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAwCG;AACH,MAAM,sBAAsB,GAAG,CAAC;KAC7B,MAAM,EAAE;KACR,GAAG,CAAC,EAAE,EAAE,EAAE,KAAK,EAAE,6EAA6E,EAAE,CAAC;KACjG,GAAG,CAAC,GAAG,EAAE,EAAE,KAAK,EAAE,gDAAgD,EAAE,CAAC;KACrE,KAAK,CACJ,kEAAkE,EAClE;IACE,KAAK,EACH,qLAAqL;CACxL,CACF;KACA,KAAK,EAAqB,CAAC;AAE9B,MAAM,CAAC,MAAM,qBAAqB,GAAkC,sBAAsB,CAAC;AAG3F,4DAA4D;AAE5D;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,UAAU,sBAAsB,CAAC,KAItC;IACC,OAAO,qBAAqB,CAAC,KAAK,CAAC,WAAW,KAAK,CAAC,OAAO,IAAI,KAAK,CAAC,UAAU,IAAI,KAAK,CAAC,QAAQ,EAAE,CAAC,CAAC;AACvG,CAAC;AACD,oEAAoE","sourcesContent":["import { z } from 'zod';\n\n/**\n * @wildo_source:part:start saas.website.label-keys.format facet:layer:shared facet:family:i18n\n *\n * `WebsiteLabelKey` — branded i18n key for marketing-site copy.\n *\n * **Format**: `website.<pageRef>.<sectionRef>.<slotPath>`\n *\n * - `website.` — fixed namespace prefix that disambiguates marketing-site\n *   labels from app i18n keys (`labels.`, `errors.`, `notifications.`).\n *   Marketing-site label packs ship as a separate file per locale\n *   (`website/src/i18n/<locale>.json`) so they never bloat the SaaS app\n *   bundle.\n * - `<pageRef>` — kebab-case page ref (validated independently by\n *   `WebsitePageRefSchema`).\n * - `<sectionRef>` — kebab-case section ref (validated independently by\n *   `WebsiteSectionRefSchema`).\n * - `<slotPath>` — leaf identifier the section consumes via\n *   `useWebsiteLabel('<slotPath>')` (Phase 2). Allows dots for nested\n *   structures (`'cta.primary'`), brackets for indexed array slots\n *   (`'tiers[0].name'`), and hyphens for multi-word leaves.\n *\n * **Examples**:\n *   - `website.landing.hero.headline`\n *   - `website.landing.hero.cta.primary`\n *   - `website.pricing.tiers.tiers[0].name`\n *   - `website.contact.form.field.email-placeholder`\n *\n * **Why a brand**: prevents the \"label key as bare string\" failure mode\n * where a typo in `'webiste.landing.hero.headline'` (note the typo) silently\n * resolves to undefined at runtime. Sections must accept\n * `WebsiteLabelKey`-typed props; consumers go through\n * `WebsiteLabelKeySchema.parse(...)` (or the manifest's `metaLabelKeys`\n * fields, which are typed against this schema) before a string flows into\n * label resolution.\n *\n * **Why a single regex**: the three nested refs (`page`, `section`, `slot`)\n * are validated separately by their own schemas inside the `defineWebsiteSection`\n * factory and `WebsitePageManifestSchema`. This schema's job is to validate\n * a fully-composed key — typically inserted directly into JSX as a string\n * literal — without re-parsing the parts.\n */\nconst _WebsiteLabelKeySchema = z\n  .string()\n  .min(10, { error: 'WebsiteLabelKey is too short (must include website.<page>.<section>.<slot>)' })\n  .max(256, { error: 'WebsiteLabelKey must be at most 256 characters' })\n  .regex(\n    /^website\\.[a-z][a-z0-9-]*\\.[a-z][a-z0-9-]*\\.[a-zA-Z0-9.\\[\\]_-]+$/,\n    {\n      error:\n        'WebsiteLabelKey must match `website.<page>.<section>.<slot>` where page/section are kebab-case and slot allows dot/bracket/hyphen/underscore (e.g. \"website.landing.hero.headline\")',\n    },\n  )\n  .brand<'WebsiteLabelKey'>();\n\nexport const WebsiteLabelKeySchema: typeof _WebsiteLabelKeySchema = _WebsiteLabelKeySchema;\n\nexport type WebsiteLabelKey = z.infer<typeof _WebsiteLabelKeySchema>;\n/** @wildo_source:part:end saas.website.label-keys.format */\n\n/**\n * @wildo_source:part:start saas.website.label-keys.compose-helper facet:layer:shared facet:family:i18n\n *\n * `composeWebsiteLabelKey` — pure helper that composes a `WebsiteLabelKey`\n * from its three parts. Used by `useWebsiteLabel` (Phase 2) and by the\n * label-pack validator to materialize the keys a section commits to.\n *\n * Returns the key as a parsed `WebsiteLabelKey` (brand applied), throwing\n * if the composed string fails the format check (defensive guard against\n * stale refs / inconsistent slot paths leaking past type-system narrowing).\n *\n * @example\n *   composeWebsiteLabelKey({\n *     pageRef: WebsitePageRefSchema.parse('landing'),\n *     sectionRef: WebsiteSectionRefSchema.parse('hero'),\n *     slotPath: 'headline',\n *   });\n *   // -> WebsiteLabelKey (\"website.landing.hero.headline\")\n */\nexport function composeWebsiteLabelKey(parts: {\n  pageRef: string;\n  sectionRef: string;\n  slotPath: string;\n}): WebsiteLabelKey {\n  return WebsiteLabelKeySchema.parse(`website.${parts.pageRef}.${parts.sectionRef}.${parts.slotPath}`);\n}\n/** @wildo_source:part:end saas.website.label-keys.compose-helper */\n"]}