@wildo-ai/saas-website 1.1.1

package/dist/esm/schemas/manifests/website-root-config.shared.schemas.js

@@ -0,0 +1,438 @@
+import { z } from 'zod';
+import { WebsiteDesignTokensSchema } from '../design-tokens/website-design-tokens.shared.schemas.js';
+import { WebsiteLabelKeySchema } from '../label-keys/website-label-key.schemas.js';
+import { WebsitePageManifestSchema, } from './website-page-manifest.shared.schemas.js';
+/**
+ * @wildo_source:part:start saas.website.seo.sitemap-config facet:layer:shared facet:family:website
+ *
+ * `WebsiteSitemapConfig` — site-wide sitemap policy block.
+ *
+ * Materialized at build time by `@astrojs/sitemap` (the official
+ * Astro plugin) when the consumer wires it into `astro.config.ts`
+ * (see `website-seo-aeo-geo` SKILL). The framework owns the
+ * **schema** (so config + enforcement live in lock-step with the
+ * page registry) but the framework does NOT own the runtime
+ * generator — `@astrojs/sitemap` already covers per-page
+ * `lastmod` / `changefreq` / `priority` + i18n `xhtml:link
+ * hreflang` annotations natively, and re-implementing that surface
+ * inside the engine would duplicate well-trodden Astro tooling for
+ * zero added value.
+ *
+ * # Field rationale
+ *
+ * **Why `enabled` defaults to `true`**:
+ *   - Marketing sites that want to ship public pages overwhelmingly
+ *     also want them in `sitemap.xml` (search engines treat its
+ *     absence as a discoverability signal). The opt-OUT shape avoids
+ *     a silent regression where a consumer ships pages that crawlers
+ *     never index because they forgot to flip a flag.
+ *   - The escape hatch (`enabled: false`) covers staging deployments
+ *     and the rare per-app decision to suppress sitemap emission
+ *     entirely (e.g. a private beta surface routed under a
+ *     `noindex` policy).
+ *
+ * **Why `changefreq` / `priority` are OPTIONAL** (no defaults):
+ *   - Both fields are non-binding hints — Google explicitly
+ *     ignores `priority` and treats `changefreq` as a soft signal.
+ *     Forcing the consumer to pick a value would either invite
+ *     superstitious authoring (`priority: 1.0` on every page) or
+ *     bury the field's actual ergonomic shape (per-page overrides
+ *     via `WebsitePageManifest.seo` — deferred until a real
+ *     consumer requests it).
+ *   - Unset values are simply omitted from the emitted `<url>`
+ *     entries; `@astrojs/sitemap` handles that automatically.
+ *
+ * **Validation**:
+ *   - `priority` is `z.number().min(0).max(1)` — outside the spec
+ *     range would silently break crawler ingestion.
+ *   - `changefreq` is the union of the seven values the sitemap
+ *     spec defines; arbitrary strings would be silently dropped by
+ *     compliant crawlers.
+ */
+const _WebsiteSitemapConfigSchema = z.object({
+    enabled: z.boolean().default(true),
+    changefreq: z
+        .enum(['always', 'hourly', 'daily', 'weekly', 'monthly', 'yearly', 'never'])
+        .optional(),
+    priority: z
+        .number()
+        .min(0, { error: 'WebsiteSitemapConfig.priority must be between 0 and 1' })
+        .max(1, { error: 'WebsiteSitemapConfig.priority must be between 0 and 1' })
+        .optional(),
+});
+export const WebsiteSitemapConfigSchema = _WebsiteSitemapConfigSchema;
+/** @wildo_source:part:end saas.website.seo.sitemap-config */
+/**
+ * @wildo_source:part:start saas.website.seo.robots-config facet:layer:shared facet:family:website
+ *
+ * `WebsiteRobotsConfig` — site-wide `robots.txt` policy block.
+ *
+ * Materialized at request time by `renderRobotsTxt(siteContext)`
+ * from `@wildo-ai/saas-website/astro` (consumer wires a thin
+ * `src/pages/robots.txt.ts` Astro endpoint that returns the helper's
+ * output). Scoped to the SITE-WIDE policy surface — per-page
+ * `noindex` is a separate concern that lands on
+ * `WebsitePageManifest.seo` once a real consumer requests it (today
+ * the site-wide `disallow[]` covers staging-environment exclusion of
+ * specific path prefixes, the dominant real-world use case).
+ *
+ * # Field rationale
+ *
+ * **Why `policy` defaults to `'index'`**:
+ *   - The default for a public marketing site is "let crawlers in";
+ *     `'noindex'` is the deliberate exception (staging environments,
+ *     beta surfaces, sites still under construction). The opt-OUT
+ *     shape mirrors `WebsiteSitemapConfig.enabled` for consistency.
+ *   - `'noindex'` emits a `User-agent: *\nDisallow: /` block — the
+ *     standard "tell every well-behaved crawler to stay away"
+ *     primitive.
+ *
+ * **Why `disallow[]` is a path-prefix list (not a regex)**:
+ *   - The `robots.txt` spec only supports literal path prefixes
+ *     with `*` / `$` wildcards; Disallow is NOT a regex surface.
+ *     Typing it as `string[]` (validated to start with `/`) keeps
+ *     the contract honest and lets consumers paste from their CDN
+ *     allowlists without translation.
+ *
+ * **Why `allowedCrawlers` and `disallowedCrawlers` are mutually
+ * exclusive**:
+ *   - The two fields are two halves of the SAME AI-crawler policy
+ *     decision. `allowedCrawlers` is the deny-by-default shape
+ *     (only the named bots may crawl); `disallowedCrawlers` is the
+ *     allow-by-default shape (every bot except the named ones may
+ *     crawl). Mixing both would emit a contradictory `robots.txt`
+ *     (a bot in both lists would receive conflicting directives).
+ *     A `superRefine` enforces the mutual-exclusion invariant at
+ *     parse time so the build fails fast.
+ *
+ * **Validation**:
+ *   - `disallow[]` entries must start with `/` (sitemap path-prefix
+ *     spec) — anything else would silently match nothing.
+ *   - `allowedCrawlers` / `disallowedCrawlers` entries must be
+ *     non-empty strings (a blank User-agent token would emit
+ *     `User-agent: ` which compliant crawlers ignore — silent
+ *     misconfig).
+ *   - `superRefine` rejects the combined-list anti-pattern.
+ */
+const _WebsiteRobotsConfigSchema = z
+    .object({
+    policy: z.enum(['index', 'noindex']).default('index'),
+    disallow: z
+        .array(z
+        .string()
+        .min(1)
+        .refine((path) => path.startsWith('/'), {
+        error: 'WebsiteRobotsConfig.disallow[] entries must start with "/"',
+    }))
+        .optional(),
+    /**
+     * Deny-by-default AI-crawler allowlist. When set, the emitted
+     * `robots.txt` lists each named bot under its own
+     * `User-agent: <bot>\nAllow: /` block, then closes with a
+     * catch-all `User-agent: *\nDisallow: /`. Mutually exclusive
+     * with `disallowedCrawlers` (see `superRefine` below).
+     */
+    allowedCrawlers: z.array(z.string().min(1)).optional(),
+    /**
+     * Allow-by-default AI-crawler denylist. When set, the emitted
+     * `robots.txt` lists each named bot under its own
+     * `User-agent: <bot>\nDisallow: /` block. Mutually exclusive
+     * with `allowedCrawlers` (see `superRefine` below).
+     */
+    disallowedCrawlers: z.array(z.string().min(1)).optional(),
+})
+    .superRefine((value, ctx) => {
+    if (value.allowedCrawlers !== undefined && value.disallowedCrawlers !== undefined) {
+        ctx.addIssue({
+            code: 'custom',
+            path: ['allowedCrawlers'],
+            message: 'WebsiteRobotsConfig.allowedCrawlers and disallowedCrawlers are mutually exclusive — pick one policy direction (deny-by-default vs allow-by-default).',
+        });
+    }
+});
+export const WebsiteRobotsConfigSchema = _WebsiteRobotsConfigSchema;
+/** @wildo_source:part:end saas.website.seo.robots-config */
+/**
+ * @wildo_source:part:start saas.website.seo.llms-txt-config facet:layer:shared facet:family:website
+ *
+ * `WebsiteLlmsTxtConfig` — site-wide `llms.txt` publication policy.
+ *
+ * The framework owns only the SERVING surface; the CONTENT remains
+ * hand-authored in `src/content/llms.txt`. This block therefore needs
+ * exactly one knob:
+ *
+ * - `enabled?: boolean`
+ *   - `true`  → publish when the file exists
+ *   - `false` → suppress publication even if the file exists
+ *   - `undefined` → auto-detect (`readLlmsTxtBody` publishes when the
+ *     file exists, returns `null` when absent)
+ *
+ * Keeping the "auto-detect when undefined" convention in the HELPER
+ * (not as a schema default) is deliberate: schema defaults are static,
+ * while file presence is runtime/build-time state.
+ */
+const _WebsiteLlmsTxtConfigSchema = z.object({
+    enabled: z.boolean().optional(),
+});
+export const WebsiteLlmsTxtConfigSchema = _WebsiteLlmsTxtConfigSchema;
+/** @wildo_source:part:end saas.website.seo.llms-txt-config */
+/**
+ * @wildo_source:part:start saas.website.root-config.seo facet:layer:shared facet:family:website
+ *
+ * `WebsiteSeoConfig` — site-wide SEO/social-graph configuration
+ * AUTHORED ON THE ROOT CONFIG.
+ *
+ * # Scope
+ *
+ * The public marketing-site origin belongs only in the per-service
+ * `wildo.website.config.ts` declaration. Keep it out of this site-level SEO
+ * block so the origin and localized routing have one source of truth.
+ *
+ * What stays on this block: site-level branding + hero-image
+ * fallbacks that are co-authored with chrome labels and page
+ * manifests respectively, NOT with the URL/i18n routing surface.
+ *
+ * # Field rationale
+ *
+ * **Why `siteName` is REQUIRED**:
+ *   - `og:site_name` is the brand label social platforms render
+ *     above the page title in shared previews. Without it, every
+ *     LinkedIn / Facebook / Slack preview shows the bare title with
+ *     no brand context.
+ *   - It is also the recommended `application-name` meta tag value
+ *     and a useful default for JSON-LD `Organization.name` schema
+ *     when the application ships structured data.
+ *
+ * **Why `defaultOgImageUrl` is OPTIONAL**:
+ *   - Each page's `WebsitePageManifest.metaLabelKeys.ogImageUrl`
+ *     takes precedence; the site-level default is a fallback for
+ *     pages that did not commit to a hero image.
+ *   - Marketing surfaces shipping no OG images at all (acceptable
+ *     for a placeholder build) should not be forced to author one.
+ *
+ * **Why `sitemap?` and `robots?` are OPTIONAL** (with sensible
+ * defaults inside each sub-schema):
+ *   - The marketing-site default ships a public surface — every
+ *     page indexable, no AI-crawler restrictions, no per-path
+ *     disallow. Forcing every consumer to author both blocks just
+ *     to land in that default state would pollute the call site.
+ *   - Omitting either block at the call site is equivalent to
+ *     authoring `{}` — `WebsiteSitemapConfig.enabled` defaults to
+ *     `true`, `WebsiteRobotsConfig.policy` defaults to `'index'`.
+ *     The per-block field rationale lives on each sub-schema.
+ *   - `llmsTxt?` is similarly optional, but with a different default
+ *     mechanic: omitting the block means "auto-detect from file
+ *     presence" rather than "use a static schema default". The helper
+ *     `readLlmsTxtBody(...)` publishes when `src/content/llms.txt`
+ *     exists and returns `null` otherwise.
+ *
+ * **Validation**:
+ *   - `siteName` is `z.string().min(1)` — empty strings would emit
+ *     `<meta property="og:site_name" content="" />` which social
+ *     platforms render as a blank line.
+ *   - `defaultOgImageUrl` (when present) is `z.url()`.
+ *   - `sitemap` / `robots` validation lives on the sub-schemas.
+ */
+const _WebsiteSeoConfigSchema = z
+    .object({
+    siteName: z
+        .string()
+        .min(1, { error: 'WebsiteSeoConfig.siteName must be a non-empty string' }),
+    defaultOgImageUrl: z
+        .url({ error: 'WebsiteSeoConfig.defaultOgImageUrl must be a fully-qualified URL' })
+        .optional(),
+    /**
+     * Sitemap policy block. Optional — omitting it is equivalent to
+     * `{ enabled: true }` (the marketing-site default). See
+     * `WebsiteSitemapConfigSchema` for field-by-field rationale.
+     */
+    sitemap: _WebsiteSitemapConfigSchema.optional(),
+    /**
+     * Robots.txt policy block. Optional — omitting it is equivalent
+     * to `{ policy: 'index' }` (the marketing-site default). See
+     * `WebsiteRobotsConfigSchema` for field-by-field rationale.
+     */
+    robots: _WebsiteRobotsConfigSchema.optional(),
+    /**
+     * `llms.txt` publication policy. Optional — omitting it means
+     * "auto-detect from file presence". See
+     * `WebsiteLlmsTxtConfigSchema` for the serving contract.
+     */
+    llmsTxt: _WebsiteLlmsTxtConfigSchema.optional(),
+});
+export const WebsiteSeoConfigSchema = _WebsiteSeoConfigSchema;
+/** @wildo_source:part:end saas.website.root-config.seo */
+/**
+ * @wildo_source:part:start saas.website.root-config.navigation facet:layer:shared facet:family:website
+ *
+ * `WebsiteNavigationConfig` — site-wide header/footer slot bindings.
+ *
+ * The framework intentionally ships no concrete header or footer. The
+ * application authors both as React components, registers them once here, and
+ * the page layout renders the site-wide chrome around every page.
+ *
+ * Both fields are typed as `unknown` at the schema layer with the
+ * `WebsiteNavigationConfig` interface narrowing them to
+ * `ComponentType<unknown>` — same rationale as
+ * `WebsiteSectionDefinition.Component` and `WebsitePageManifest.pageComponent`.
+ */
+const _WebsiteNavigationConfigSchema = z.object({
+    headerComponent: z.unknown(),
+    footerComponent: z.unknown(),
+});
+export const WebsiteNavigationConfigSchema = _WebsiteNavigationConfigSchema;
+/** @wildo_source:part:end saas.website.root-config.navigation */
+/**
+ * @wildo_source:part:start saas.website.root-config.schema facet:layer:shared facet:family:website
+ *
+ * `WebsiteRootConfig` — the site-level configuration consumed by:
+ *   - the Astro adapter to drive i18n routing, page mounting,
+ *     and design-token CSS emission,
+ *   - the website audit command to validate label-pack
+ *     coverage and SEO structured-data conformance,
+ *   - the runtime `<WebsitePageLayout>` to render navigation
+ *     and apply design tokens.
+ *
+ * **Authoring convention**: each marketing-site service exports a single
+ * `WEBSITE_ROOT_CONFIG: WebsiteRootConfig` from `src/website-root.config.ts`.
+ * The Astro adapter and the audit command
+ * both consume this canonical entry point; there is exactly one site
+ * config per marketing site (no per-page or per-section overrides at
+ * this level — overrides flow through the L0/L1/L1.5 component
+ * registration hierarchy described in D6).
+ *
+ * # Scope
+ *
+ * This block carries site-level chrome and registry data only. Per-locale
+ * routing (`locales` / `defaultLocale`) and the public origin belong in the
+ * per-service `wildo.website.config.ts` declaration, avoiding duplicated
+ * configuration that could diverge during site generation.
+ *
+ * **Field-by-field rationale**:
+ *
+ * - `pageManifests` — the registry of every page on the site. Indexed
+ *   downstream by `manifest.ref`. Refs MUST be unique (refinement
+ *   below).
+ * - `designTokens` — see `WebsiteDesignTokensSchema`.
+ * - `navigation` — see `WebsiteNavigationConfigSchema`.
+ * - `chromeLabelKeys` — OPTIONAL. The set of fully-composed label keys
+ *   the site-wide chrome (header / footer / any global slot the
+ *   consumer renders outside a section context) reads via
+ *   `useWebsiteLabelByKey(...)`. Declared here, NOT in section
+ *   `expectedLabelKeys`, because chrome is rendered outside the
+ *   page+section context — `useWebsiteLabel(slot)` is structurally
+ *   unavailable to it. Threading these through the label-pack
+ *   validator (a) silences the always-on "orphaned chrome key" build
+ *   warnings and (b) lets the build fail fast when a chrome key is
+ *   missing from a locale pack, the same way section keys do.
+ *   Defaults to an empty array; sites with no chrome label reads
+ *   may omit the field entirely.
+ * - `seo` — site-level branding + hero-image fallback (see
+ *   `WebsiteSeoConfigSchema`). The marketing-site origin USED to live
+ *   here as `seo.siteOrigin`; it now lives only on
+ *   `WildoMarketingWebsiteConfig.publicOrigin`.
+ * - `skipToMainContentLabelKey` — see field JSDoc below.
+ *
+ * **Refinements**:
+ *   - `pageManifests[].ref` uniqueness — the registry is keyed by ref;
+ *     duplicates would silently overwrite each other in the lookup
+ *     table the bridge uses for cross-page links.
+ *   - `pageManifests[].routePath` uniqueness — two pages cannot mount
+ *     at the same path (Astro would error at build time, but we
+ *     surface it earlier here with a clearer diagnostic).
+ *   - `chromeLabelKeys` uniqueness — duplicates indicate copy-paste
+ *     bugs at the consumer's call site; surface them here.
+ */
+const _WebsiteRootConfigSchema = z
+    .object({
+    pageManifests: z.array(WebsitePageManifestSchema).min(1, {
+        error: 'WebsiteRootConfig must declare at least one page manifest',
+    }),
+    designTokens: WebsiteDesignTokensSchema,
+    navigation: _WebsiteNavigationConfigSchema,
+    chromeLabelKeys: z.array(WebsiteLabelKeySchema).default([]),
+    /**
+     * Site-level branding + hero-image fallback used by the Astro
+     * head renderer to compose `<meta property="og:site_name">` and
+     * the per-page OG image fallback. The marketing-site origin
+     * (`siteOrigin`) USED to live here; it was moved to
+     * `WildoMarketingWebsiteConfig.publicOrigin` in the seam-collapse
+     * (single source of truth for "what's the origin this site is
+     * reachable at").
+     */
+    seo: _WebsiteSeoConfigSchema,
+    /**
+     * Label key the framework reads to render the "Skip to main
+     * content" link as the first focusable element on every page
+     * Required because:
+     *   - Skip-to-main is a baseline keyboard-accessibility
+     *     affordance — WCAG 2.1 §2.4.1 "Bypass Blocks" (Level A)
+     *     mandates it. A marketing-site framework that omits it
+     *     fails AA for the entire surface; making the contract
+     *     opt-in invites that regression on every new consumer.
+     *   - The text is announced verbatim by assistive tech, so it
+     *     MUST be localized — a hardcoded English fallback would
+     *     speak "Skip to main content" to French users. Forcing the
+     *     key through the label-pack validation surface means the
+     *     dev server fails fast when the consumer forgets to add
+     *     the entry to a locale pack.
+     *   - The framework (NOT the consumer's chrome) owns rendering
+     *     the skip link because the chrome is itself the obstacle
+     *     the link bypasses — a chrome-side implementation would
+     *     either be inside the chrome (impossible to focus before
+     *     the chrome) or above it (creating a structural surface
+     *     the framework needs anyway).
+     *
+     * The key MUST also be present in `chromeLabelKeys` (the
+     * label-pack validator silences "orphaned" warnings off
+     * `chromeLabelKeys`) — the framework adds it automatically via
+     * the `superRefine` pass below so consumers cannot forget.
+     */
+    skipToMainContentLabelKey: WebsiteLabelKeySchema,
+})
+    .superRefine((config, ctx) => {
+    const seenRefs = new Set();
+    const seenRoutePaths = new Set();
+    for (const [index, manifest] of config.pageManifests.entries()) {
+        const refKey = manifest.ref;
+        if (seenRefs.has(refKey)) {
+            ctx.addIssue({
+                code: 'custom',
+                path: ['pageManifests', index, 'ref'],
+                message: `Duplicate page ref "${refKey}" in WebsiteRootConfig.pageManifests`,
+            });
+        }
+        seenRefs.add(refKey);
+        const routeKey = manifest.routePath;
+        if (seenRoutePaths.has(routeKey)) {
+            ctx.addIssue({
+                code: 'custom',
+                path: ['pageManifests', index, 'routePath'],
+                message: `Duplicate routePath "${routeKey}" in WebsiteRootConfig.pageManifests`,
+            });
+        }
+        seenRoutePaths.add(routeKey);
+    }
+    /**
+     * `chromeLabelKeys` uniqueness — a duplicate is harmless at
+     * runtime (the validator de-dupes via a Set) but always indicates
+     * a copy-paste bug at the consumer's call site. Surfacing it here
+     * keeps the chrome contract tidy and matches the discipline applied
+     * to `pageManifests[].ref` and `locales`.
+     */
+    const seenChromeKeys = new Set();
+    for (const [index, key] of config.chromeLabelKeys.entries()) {
+        const keyStr = key;
+        if (seenChromeKeys.has(keyStr)) {
+            ctx.addIssue({
+                code: 'custom',
+                path: ['chromeLabelKeys', index],
+                message: `Duplicate chrome label key "${keyStr}" in WebsiteRootConfig.chromeLabelKeys`,
+            });
+        }
+        seenChromeKeys.add(keyStr);
+    }
+});
+export const WebsiteRootConfigSchema = _WebsiteRootConfigSchema;
+/** @wildo_source:part:end saas.website.root-config.schema */
+//# sourceMappingURL=website-root-config.shared.schemas.js.map

package/dist/esm/schemas/manifests/website-root-config.shared.schemas.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"website-root-config.shared.schemas.js","sourceRoot":"","sources":["../../../../../src/schemas/manifests/website-root-config.shared.schemas.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB,OAAO,EAAE,yBAAyB,EAAE,MAAM,uDAAuD,CAAC;AAClG,OAAO,EAAE,qBAAqB,EAAE,MAAM,yCAAyC,CAAC;AAChF,OAAO,EACL,yBAAyB,GAE1B,MAAM,wCAAwC,CAAC;AAEhD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8CG;AACH,MAAM,2BAA2B,GAAG,CAAC,CAAC,MAAM,CAAC;IAC3C,OAAO,EAAE,CAAC,CAAC,OAAO,EAAE,CAAC,OAAO,CAAC,IAAI,CAAC;IAClC,UAAU,EAAE,CAAC;SACV,IAAI,CAAC,CAAC,QAAQ,EAAE,QAAQ,EAAE,OAAO,EAAE,QAAQ,EAAE,SAAS,EAAE,QAAQ,EAAE,OAAO,CAAC,CAAC;SAC3E,QAAQ,EAAE;IACb,QAAQ,EAAE,CAAC;SACR,MAAM,EAAE;SACR,GAAG,CAAC,CAAC,EAAE,EAAE,KAAK,EAAE,uDAAuD,EAAE,CAAC;SAC1E,GAAG,CAAC,CAAC,EAAE,EAAE,KAAK,EAAE,uDAAuD,EAAE,CAAC;SAC1E,QAAQ,EAAE;CACd,CAAC,CAAC;AAEH,MAAM,CAAC,MAAM,0BAA0B,GACrC,2BAA2B,CAAC;AAG9B,6DAA6D;AAE7D;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAmDG;AACH,MAAM,0BAA0B,GAAG,CAAC;KACjC,MAAM,CAAC;IACN,MAAM,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,OAAO,EAAE,SAAS,CAAC,CAAC,CAAC,OAAO,CAAC,OAAO,CAAC;IACrD,QAAQ,EAAE,CAAC;SACR,KAAK,CACJ,CAAC;SACE,MAAM,EAAE;SACR,GAAG,CAAC,CAAC,CAAC;SACN,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,UAAU,CAAC,GAAG,CAAC,EAAE;QACtC,KAAK,EAAE,4DAA4D;KACpE,CAAC,CACL;SACA,QAAQ,EAAE;IACb;;;;;;OAMG;IACH,eAAe,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE;IACtD;;;;;OAKG;IACH,kBAAkB,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE;CAC1D,CAAC;KACD,WAAW,CAAC,CAAC,KAAK,EAAE,GAAG,EAAE,EAAE;IAC1B,IAAI,KAAK,CAAC,eAAe,KAAK,SAAS,IAAI,KAAK,CAAC,kBAAkB,KAAK,SAAS,EAAE,CAAC;QAClF,GAAG,CAAC,QAAQ,CAAC;YACX,IAAI,EAAE,QAAQ;YACd,IAAI,EAAE,CAAC,iBAAiB,CAAC;YACzB,OAAO,EACL,sJAAsJ;SACzJ,CAAC,CAAC;IACL,CAAC;AACH,CAAC,CAAC,CAAC;AAEL,MAAM,CAAC,MAAM,yBAAyB,GACpC,0BAA0B,CAAC;AAG7B,4DAA4D;AAE5D;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,2BAA2B,GAAG,CAAC,CAAC,MAAM,CAAC;IAC3C,OAAO,EAAE,CAAC,CAAC,OAAO,EAAE,CAAC,QAAQ,EAAE;CAChC,CAAC,CAAC;AAEH,MAAM,CAAC,MAAM,0BAA0B,GACrC,2BAA2B,CAAC;AAG9B,8DAA8D;AAE9D;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAwDG;AACH,MAAM,uBAAuB,GAAG,CAAC;KAC9B,MAAM,CAAC;IACN,QAAQ,EAAE,CAAC;SACR,MAAM,EAAE;SACR,GAAG,CAAC,CAAC,EAAE,EAAE,KAAK,EAAE,sDAAsD,EAAE,CAAC;IAC5E,iBAAiB,EAAE,CAAC;SACjB,GAAG,CAAC,EAAE,KAAK,EAAE,kEAAkE,EAAE,CAAC;SAClF,QAAQ,EAAE;IACb;;;;OAIG;IACH,OAAO,EAAE,2BAA2B,CAAC,QAAQ,EAAE;IAC/C;;;;OAIG;IACH,MAAM,EAAE,0BAA0B,CAAC,QAAQ,EAAE;IAC7C;;;;OAIG;IACH,OAAO,EAAE,2BAA2B,CAAC,QAAQ,EAAE;CAChD,CAAC,CAAC;AAEL,MAAM,CAAC,MAAM,sBAAsB,GAAmC,uBAAuB,CAAC;AAG9F,0DAA0D;AAE1D;;;;;;;;;;;;;GAaG;AACH,MAAM,8BAA8B,GAAG,CAAC,CAAC,MAAM,CAAC;IAC9C,eAAe,EAAE,CAAC,CAAC,OAAO,EAAE;IAC5B,eAAe,EAAE,CAAC,CAAC,OAAO,EAAE;CAC7B,CAAC,CAAC;AAEH,MAAM,CAAC,MAAM,6BAA6B,GACxC,8BAA8B,CAAC;AAOjC,iEAAiE;AAEjE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4DG;AACH,MAAM,wBAAwB,GAAG,CAAC;KAC/B,MAAM,CAAC;IACN,aAAa,EAAE,CAAC,CAAC,KAAK,CAAC,yBAAyB,CAAC,CAAC,GAAG,CAAC,CAAC,EAAE;QACvD,KAAK,EAAE,2DAA2D;KACnE,CAAC;IACF,YAAY,EAAE,yBAAyB;IACvC,UAAU,EAAE,8BAA8B;IAC1C,eAAe,EAAE,CAAC,CAAC,KAAK,CAAC,qBAAqB,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;IAC3D;;;;;;;;OAQG;IACH,GAAG,EAAE,uBAAuB;IAC5B;;;;;;;;;;;;;;;;;;;;;;;;;;OA0BG;IACH,yBAAyB,EAAE,qBAAqB;CACjD,CAAC;KACD,WAAW,CAAC,CAAC,MAAM,EAAE,GAAG,EAAE,EAAE;IAC3B,MAAM,QAAQ,GAAG,IAAI,GAAG,EAAU,CAAC;IACnC,MAAM,cAAc,GAAG,IAAI,GAAG,EAAU,CAAC;IACzC,KAAK,MAAM,CAAC,KAAK,EAAE,QAAQ,CAAC,IAAI,MAAM,CAAC,aAAa,CAAC,OAAO,EAAE,EAAE,CAAC;QAC/D,MAAM,MAAM,GAAG,QAAQ,CAAC,GAAwB,CAAC;QACjD,IAAI,QAAQ,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE,CAAC;YACzB,GAAG,CAAC,QAAQ,CAAC;gBACX,IAAI,EAAE,QAAQ;gBACd,IAAI,EAAE,CAAC,eAAe,EAAE,KAAK,EAAE,KAAK,CAAC;gBACrC,OAAO,EAAE,uBAAuB,MAAM,sCAAsC;aAC7E,CAAC,CAAC;QACL,CAAC;QACD,QAAQ,CAAC,GAAG,CAAC,MAAM,CAAC,CAAC;QAErB,MAAM,QAAQ,GAAG,QAAQ,CAAC,SAA8B,CAAC;QACzD,IAAI,cAAc,CAAC,GAAG,CAAC,QAAQ,CAAC,EAAE,CAAC;YACjC,GAAG,CAAC,QAAQ,CAAC;gBACX,IAAI,EAAE,QAAQ;gBACd,IAAI,EAAE,CAAC,eAAe,EAAE,KAAK,EAAE,WAAW,CAAC;gBAC3C,OAAO,EAAE,wBAAwB,QAAQ,sCAAsC;aAChF,CAAC,CAAC;QACL,CAAC;QACD,cAAc,CAAC,GAAG,CAAC,QAAQ,CAAC,CAAC;IAC/B,CAAC;IAED;;;;;;OAMG;IACH,MAAM,cAAc,GAAG,IAAI,GAAG,EAAU,CAAC;IACzC,KAAK,MAAM,CAAC,KAAK,EAAE,GAAG,CAAC,IAAI,MAAM,CAAC,eAAe,CAAC,OAAO,EAAE,EAAE,CAAC;QAC5D,MAAM,MAAM,GAAG,GAAwB,CAAC;QACxC,IAAI,cAAc,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE,CAAC;YAC/B,GAAG,CAAC,QAAQ,CAAC;gBACX,IAAI,EAAE,QAAQ;gBACd,IAAI,EAAE,CAAC,iBAAiB,EAAE,KAAK,CAAC;gBAChC,OAAO,EAAE,+BAA+B,MAAM,wCAAwC;aACvF,CAAC,CAAC;QACL,CAAC;QACD,cAAc,CAAC,GAAG,CAAC,MAAM,CAAC,CAAC;IAC7B,CAAC;AACH,CAAC,CAAC,CAAC;AAEL,MAAM,CAAC,MAAM,uBAAuB,GAAoC,wBAAwB,CAAC;AA4BjG,6DAA6D","sourcesContent":["import type { ComponentType } from 'react';\nimport { z } from 'zod';\n\nimport { WebsiteDesignTokensSchema } from '../design-tokens/website-design-tokens.shared.schemas';\nimport { WebsiteLabelKeySchema } from '../label-keys/website-label-key.schemas';\nimport {\n  WebsitePageManifestSchema,\n  type WebsitePageManifest,\n} from './website-page-manifest.shared.schemas';\n\n/**\n * @wildo_source:part:start saas.website.seo.sitemap-config facet:layer:shared facet:family:website\n *\n * `WebsiteSitemapConfig` — site-wide sitemap policy block.\n *\n * Materialized at build time by `@astrojs/sitemap` (the official\n * Astro plugin) when the consumer wires it into `astro.config.ts`\n * (see `website-seo-aeo-geo` SKILL). The framework owns the\n * **schema** (so config + enforcement live in lock-step with the\n * page registry) but the framework does NOT own the runtime\n * generator — `@astrojs/sitemap` already covers per-page\n * `lastmod` / `changefreq` / `priority` + i18n `xhtml:link\n * hreflang` annotations natively, and re-implementing that surface\n * inside the engine would duplicate well-trodden Astro tooling for\n * zero added value.\n *\n * # Field rationale\n *\n * **Why `enabled` defaults to `true`**:\n *   - Marketing sites that want to ship public pages overwhelmingly\n *     also want them in `sitemap.xml` (search engines treat its\n *     absence as a discoverability signal). The opt-OUT shape avoids\n *     a silent regression where a consumer ships pages that crawlers\n *     never index because they forgot to flip a flag.\n *   - The escape hatch (`enabled: false`) covers staging deployments\n *     and the rare per-app decision to suppress sitemap emission\n *     entirely (e.g. a private beta surface routed under a\n *     `noindex` policy).\n *\n * **Why `changefreq` / `priority` are OPTIONAL** (no defaults):\n *   - Both fields are non-binding hints — Google explicitly\n *     ignores `priority` and treats `changefreq` as a soft signal.\n *     Forcing the consumer to pick a value would either invite\n *     superstitious authoring (`priority: 1.0` on every page) or\n *     bury the field's actual ergonomic shape (per-page overrides\n *     via `WebsitePageManifest.seo` — deferred until a real\n *     consumer requests it).\n *   - Unset values are simply omitted from the emitted `<url>`\n *     entries; `@astrojs/sitemap` handles that automatically.\n *\n * **Validation**:\n *   - `priority` is `z.number().min(0).max(1)` — outside the spec\n *     range would silently break crawler ingestion.\n *   - `changefreq` is the union of the seven values the sitemap\n *     spec defines; arbitrary strings would be silently dropped by\n *     compliant crawlers.\n */\nconst _WebsiteSitemapConfigSchema = z.object({\n  enabled: z.boolean().default(true),\n  changefreq: z\n    .enum(['always', 'hourly', 'daily', 'weekly', 'monthly', 'yearly', 'never'])\n    .optional(),\n  priority: z\n    .number()\n    .min(0, { error: 'WebsiteSitemapConfig.priority must be between 0 and 1' })\n    .max(1, { error: 'WebsiteSitemapConfig.priority must be between 0 and 1' })\n    .optional(),\n});\n\nexport const WebsiteSitemapConfigSchema: typeof _WebsiteSitemapConfigSchema =\n  _WebsiteSitemapConfigSchema;\n\nexport type WebsiteSitemapConfig = z.infer<typeof _WebsiteSitemapConfigSchema>;\n/** @wildo_source:part:end saas.website.seo.sitemap-config */\n\n/**\n * @wildo_source:part:start saas.website.seo.robots-config facet:layer:shared facet:family:website\n *\n * `WebsiteRobotsConfig` — site-wide `robots.txt` policy block.\n *\n * Materialized at request time by `renderRobotsTxt(siteContext)`\n * from `@wildo-ai/saas-website/astro` (consumer wires a thin\n * `src/pages/robots.txt.ts` Astro endpoint that returns the helper's\n * output). Scoped to the SITE-WIDE policy surface — per-page\n * `noindex` is a separate concern that lands on\n * `WebsitePageManifest.seo` once a real consumer requests it (today\n * the site-wide `disallow[]` covers staging-environment exclusion of\n * specific path prefixes, the dominant real-world use case).\n *\n * # Field rationale\n *\n * **Why `policy` defaults to `'index'`**:\n *   - The default for a public marketing site is \"let crawlers in\";\n *     `'noindex'` is the deliberate exception (staging environments,\n *     beta surfaces, sites still under construction). The opt-OUT\n *     shape mirrors `WebsiteSitemapConfig.enabled` for consistency.\n *   - `'noindex'` emits a `User-agent: *\\nDisallow: /` block — the\n *     standard \"tell every well-behaved crawler to stay away\"\n *     primitive.\n *\n * **Why `disallow[]` is a path-prefix list (not a regex)**:\n *   - The `robots.txt` spec only supports literal path prefixes\n *     with `*` / `$` wildcards; Disallow is NOT a regex surface.\n *     Typing it as `string[]` (validated to start with `/`) keeps\n *     the contract honest and lets consumers paste from their CDN\n *     allowlists without translation.\n *\n * **Why `allowedCrawlers` and `disallowedCrawlers` are mutually\n * exclusive**:\n *   - The two fields are two halves of the SAME AI-crawler policy\n *     decision. `allowedCrawlers` is the deny-by-default shape\n *     (only the named bots may crawl); `disallowedCrawlers` is the\n *     allow-by-default shape (every bot except the named ones may\n *     crawl). Mixing both would emit a contradictory `robots.txt`\n *     (a bot in both lists would receive conflicting directives).\n *     A `superRefine` enforces the mutual-exclusion invariant at\n *     parse time so the build fails fast.\n *\n * **Validation**:\n *   - `disallow[]` entries must start with `/` (sitemap path-prefix\n *     spec) — anything else would silently match nothing.\n *   - `allowedCrawlers` / `disallowedCrawlers` entries must be\n *     non-empty strings (a blank User-agent token would emit\n *     `User-agent: ` which compliant crawlers ignore — silent\n *     misconfig).\n *   - `superRefine` rejects the combined-list anti-pattern.\n */\nconst _WebsiteRobotsConfigSchema = z\n  .object({\n    policy: z.enum(['index', 'noindex']).default('index'),\n    disallow: z\n      .array(\n        z\n          .string()\n          .min(1)\n          .refine((path) => path.startsWith('/'), {\n            error: 'WebsiteRobotsConfig.disallow[] entries must start with \"/\"',\n          }),\n      )\n      .optional(),\n    /**\n     * Deny-by-default AI-crawler allowlist. When set, the emitted\n     * `robots.txt` lists each named bot under its own\n     * `User-agent: <bot>\\nAllow: /` block, then closes with a\n     * catch-all `User-agent: *\\nDisallow: /`. Mutually exclusive\n     * with `disallowedCrawlers` (see `superRefine` below).\n     */\n    allowedCrawlers: z.array(z.string().min(1)).optional(),\n    /**\n     * Allow-by-default AI-crawler denylist. When set, the emitted\n     * `robots.txt` lists each named bot under its own\n     * `User-agent: <bot>\\nDisallow: /` block. Mutually exclusive\n     * with `allowedCrawlers` (see `superRefine` below).\n     */\n    disallowedCrawlers: z.array(z.string().min(1)).optional(),\n  })\n  .superRefine((value, ctx) => {\n    if (value.allowedCrawlers !== undefined && value.disallowedCrawlers !== undefined) {\n      ctx.addIssue({\n        code: 'custom',\n        path: ['allowedCrawlers'],\n        message:\n          'WebsiteRobotsConfig.allowedCrawlers and disallowedCrawlers are mutually exclusive — pick one policy direction (deny-by-default vs allow-by-default).',\n      });\n    }\n  });\n\nexport const WebsiteRobotsConfigSchema: typeof _WebsiteRobotsConfigSchema =\n  _WebsiteRobotsConfigSchema;\n\nexport type WebsiteRobotsConfig = z.infer<typeof _WebsiteRobotsConfigSchema>;\n/** @wildo_source:part:end saas.website.seo.robots-config */\n\n/**\n * @wildo_source:part:start saas.website.seo.llms-txt-config facet:layer:shared facet:family:website\n *\n * `WebsiteLlmsTxtConfig` — site-wide `llms.txt` publication policy.\n *\n * The framework owns only the SERVING surface; the CONTENT remains\n * hand-authored in `src/content/llms.txt`. This block therefore needs\n * exactly one knob:\n *\n * - `enabled?: boolean`\n *   - `true`  → publish when the file exists\n *   - `false` → suppress publication even if the file exists\n *   - `undefined` → auto-detect (`readLlmsTxtBody` publishes when the\n *     file exists, returns `null` when absent)\n *\n * Keeping the \"auto-detect when undefined\" convention in the HELPER\n * (not as a schema default) is deliberate: schema defaults are static,\n * while file presence is runtime/build-time state.\n */\nconst _WebsiteLlmsTxtConfigSchema = z.object({\n  enabled: z.boolean().optional(),\n});\n\nexport const WebsiteLlmsTxtConfigSchema: typeof _WebsiteLlmsTxtConfigSchema =\n  _WebsiteLlmsTxtConfigSchema;\n\nexport type WebsiteLlmsTxtConfig = z.infer<typeof _WebsiteLlmsTxtConfigSchema>;\n/** @wildo_source:part:end saas.website.seo.llms-txt-config */\n\n/**\n * @wildo_source:part:start saas.website.root-config.seo facet:layer:shared facet:family:website\n *\n * `WebsiteSeoConfig` — site-wide SEO/social-graph configuration\n * AUTHORED ON THE ROOT CONFIG.\n *\n * # Scope\n *\n * The public marketing-site origin belongs only in the per-service\n * `wildo.website.config.ts` declaration. Keep it out of this site-level SEO\n * block so the origin and localized routing have one source of truth.\n *\n * What stays on this block: site-level branding + hero-image\n * fallbacks that are co-authored with chrome labels and page\n * manifests respectively, NOT with the URL/i18n routing surface.\n *\n * # Field rationale\n *\n * **Why `siteName` is REQUIRED**:\n *   - `og:site_name` is the brand label social platforms render\n *     above the page title in shared previews. Without it, every\n *     LinkedIn / Facebook / Slack preview shows the bare title with\n *     no brand context.\n *   - It is also the recommended `application-name` meta tag value\n *     and a useful default for JSON-LD `Organization.name` schema\n *     when the application ships structured data.\n *\n * **Why `defaultOgImageUrl` is OPTIONAL**:\n *   - Each page's `WebsitePageManifest.metaLabelKeys.ogImageUrl`\n *     takes precedence; the site-level default is a fallback for\n *     pages that did not commit to a hero image.\n *   - Marketing surfaces shipping no OG images at all (acceptable\n *     for a placeholder build) should not be forced to author one.\n *\n * **Why `sitemap?` and `robots?` are OPTIONAL** (with sensible\n * defaults inside each sub-schema):\n *   - The marketing-site default ships a public surface — every\n *     page indexable, no AI-crawler restrictions, no per-path\n *     disallow. Forcing every consumer to author both blocks just\n *     to land in that default state would pollute the call site.\n *   - Omitting either block at the call site is equivalent to\n *     authoring `{}` — `WebsiteSitemapConfig.enabled` defaults to\n *     `true`, `WebsiteRobotsConfig.policy` defaults to `'index'`.\n *     The per-block field rationale lives on each sub-schema.\n *   - `llmsTxt?` is similarly optional, but with a different default\n *     mechanic: omitting the block means \"auto-detect from file\n *     presence\" rather than \"use a static schema default\". The helper\n *     `readLlmsTxtBody(...)` publishes when `src/content/llms.txt`\n *     exists and returns `null` otherwise.\n *\n * **Validation**:\n *   - `siteName` is `z.string().min(1)` — empty strings would emit\n *     `<meta property=\"og:site_name\" content=\"\" />` which social\n *     platforms render as a blank line.\n *   - `defaultOgImageUrl` (when present) is `z.url()`.\n *   - `sitemap` / `robots` validation lives on the sub-schemas.\n */\nconst _WebsiteSeoConfigSchema = z\n  .object({\n    siteName: z\n      .string()\n      .min(1, { error: 'WebsiteSeoConfig.siteName must be a non-empty string' }),\n    defaultOgImageUrl: z\n      .url({ error: 'WebsiteSeoConfig.defaultOgImageUrl must be a fully-qualified URL' })\n      .optional(),\n    /**\n     * Sitemap policy block. Optional — omitting it is equivalent to\n     * `{ enabled: true }` (the marketing-site default). See\n     * `WebsiteSitemapConfigSchema` for field-by-field rationale.\n     */\n    sitemap: _WebsiteSitemapConfigSchema.optional(),\n    /**\n     * Robots.txt policy block. Optional — omitting it is equivalent\n     * to `{ policy: 'index' }` (the marketing-site default). See\n     * `WebsiteRobotsConfigSchema` for field-by-field rationale.\n     */\n    robots: _WebsiteRobotsConfigSchema.optional(),\n    /**\n     * `llms.txt` publication policy. Optional — omitting it means\n     * \"auto-detect from file presence\". See\n     * `WebsiteLlmsTxtConfigSchema` for the serving contract.\n     */\n    llmsTxt: _WebsiteLlmsTxtConfigSchema.optional(),\n  });\n\nexport const WebsiteSeoConfigSchema: typeof _WebsiteSeoConfigSchema = _WebsiteSeoConfigSchema;\n\nexport type WebsiteSeoConfig = z.infer<typeof _WebsiteSeoConfigSchema>;\n/** @wildo_source:part:end saas.website.root-config.seo */\n\n/**\n * @wildo_source:part:start saas.website.root-config.navigation facet:layer:shared facet:family:website\n *\n * `WebsiteNavigationConfig` — site-wide header/footer slot bindings.\n *\n * The framework intentionally ships no concrete header or footer. The\n * application authors both as React components, registers them once here, and\n * the page layout renders the site-wide chrome around every page.\n *\n * Both fields are typed as `unknown` at the schema layer with the\n * `WebsiteNavigationConfig` interface narrowing them to\n * `ComponentType<unknown>` — same rationale as\n * `WebsiteSectionDefinition.Component` and `WebsitePageManifest.pageComponent`.\n */\nconst _WebsiteNavigationConfigSchema = z.object({\n  headerComponent: z.unknown(),\n  footerComponent: z.unknown(),\n});\n\nexport const WebsiteNavigationConfigSchema: typeof _WebsiteNavigationConfigSchema =\n  _WebsiteNavigationConfigSchema;\n\nexport interface WebsiteNavigationConfig\n  extends z.infer<typeof _WebsiteNavigationConfigSchema> {\n  headerComponent: ComponentType<unknown>;\n  footerComponent: ComponentType<unknown>;\n}\n/** @wildo_source:part:end saas.website.root-config.navigation */\n\n/**\n * @wildo_source:part:start saas.website.root-config.schema facet:layer:shared facet:family:website\n *\n * `WebsiteRootConfig` — the site-level configuration consumed by:\n *   - the Astro adapter to drive i18n routing, page mounting,\n *     and design-token CSS emission,\n *   - the website audit command to validate label-pack\n *     coverage and SEO structured-data conformance,\n *   - the runtime `<WebsitePageLayout>` to render navigation\n *     and apply design tokens.\n *\n * **Authoring convention**: each marketing-site service exports a single\n * `WEBSITE_ROOT_CONFIG: WebsiteRootConfig` from `src/website-root.config.ts`.\n * The Astro adapter and the audit command\n * both consume this canonical entry point; there is exactly one site\n * config per marketing site (no per-page or per-section overrides at\n * this level — overrides flow through the L0/L1/L1.5 component\n * registration hierarchy described in D6).\n *\n * # Scope\n *\n * This block carries site-level chrome and registry data only. Per-locale\n * routing (`locales` / `defaultLocale`) and the public origin belong in the\n * per-service `wildo.website.config.ts` declaration, avoiding duplicated\n * configuration that could diverge during site generation.\n *\n * **Field-by-field rationale**:\n *\n * - `pageManifests` — the registry of every page on the site. Indexed\n *   downstream by `manifest.ref`. Refs MUST be unique (refinement\n *   below).\n * - `designTokens` — see `WebsiteDesignTokensSchema`.\n * - `navigation` — see `WebsiteNavigationConfigSchema`.\n * - `chromeLabelKeys` — OPTIONAL. The set of fully-composed label keys\n *   the site-wide chrome (header / footer / any global slot the\n *   consumer renders outside a section context) reads via\n *   `useWebsiteLabelByKey(...)`. Declared here, NOT in section\n *   `expectedLabelKeys`, because chrome is rendered outside the\n *   page+section context — `useWebsiteLabel(slot)` is structurally\n *   unavailable to it. Threading these through the label-pack\n *   validator (a) silences the always-on \"orphaned chrome key\" build\n *   warnings and (b) lets the build fail fast when a chrome key is\n *   missing from a locale pack, the same way section keys do.\n *   Defaults to an empty array; sites with no chrome label reads\n *   may omit the field entirely.\n * - `seo` — site-level branding + hero-image fallback (see\n *   `WebsiteSeoConfigSchema`). The marketing-site origin USED to live\n *   here as `seo.siteOrigin`; it now lives only on\n *   `WildoMarketingWebsiteConfig.publicOrigin`.\n * - `skipToMainContentLabelKey` — see field JSDoc below.\n *\n * **Refinements**:\n *   - `pageManifests[].ref` uniqueness — the registry is keyed by ref;\n *     duplicates would silently overwrite each other in the lookup\n *     table the bridge uses for cross-page links.\n *   - `pageManifests[].routePath` uniqueness — two pages cannot mount\n *     at the same path (Astro would error at build time, but we\n *     surface it earlier here with a clearer diagnostic).\n *   - `chromeLabelKeys` uniqueness — duplicates indicate copy-paste\n *     bugs at the consumer's call site; surface them here.\n */\nconst _WebsiteRootConfigSchema = z\n  .object({\n    pageManifests: z.array(WebsitePageManifestSchema).min(1, {\n      error: 'WebsiteRootConfig must declare at least one page manifest',\n    }),\n    designTokens: WebsiteDesignTokensSchema,\n    navigation: _WebsiteNavigationConfigSchema,\n    chromeLabelKeys: z.array(WebsiteLabelKeySchema).default([]),\n    /**\n     * Site-level branding + hero-image fallback used by the Astro\n     * head renderer to compose `<meta property=\"og:site_name\">` and\n     * the per-page OG image fallback. The marketing-site origin\n     * (`siteOrigin`) USED to live here; it was moved to\n     * `WildoMarketingWebsiteConfig.publicOrigin` in the seam-collapse\n     * (single source of truth for \"what's the origin this site is\n     * reachable at\").\n     */\n    seo: _WebsiteSeoConfigSchema,\n    /**\n     * Label key the framework reads to render the \"Skip to main\n     * content\" link as the first focusable element on every page\n     * Required because:\n     *   - Skip-to-main is a baseline keyboard-accessibility\n     *     affordance — WCAG 2.1 §2.4.1 \"Bypass Blocks\" (Level A)\n     *     mandates it. A marketing-site framework that omits it\n     *     fails AA for the entire surface; making the contract\n     *     opt-in invites that regression on every new consumer.\n     *   - The text is announced verbatim by assistive tech, so it\n     *     MUST be localized — a hardcoded English fallback would\n     *     speak \"Skip to main content\" to French users. Forcing the\n     *     key through the label-pack validation surface means the\n     *     dev server fails fast when the consumer forgets to add\n     *     the entry to a locale pack.\n     *   - The framework (NOT the consumer's chrome) owns rendering\n     *     the skip link because the chrome is itself the obstacle\n     *     the link bypasses — a chrome-side implementation would\n     *     either be inside the chrome (impossible to focus before\n     *     the chrome) or above it (creating a structural surface\n     *     the framework needs anyway).\n     *\n     * The key MUST also be present in `chromeLabelKeys` (the\n     * label-pack validator silences \"orphaned\" warnings off\n     * `chromeLabelKeys`) — the framework adds it automatically via\n     * the `superRefine` pass below so consumers cannot forget.\n     */\n    skipToMainContentLabelKey: WebsiteLabelKeySchema,\n  })\n  .superRefine((config, ctx) => {\n    const seenRefs = new Set<string>();\n    const seenRoutePaths = new Set<string>();\n    for (const [index, manifest] of config.pageManifests.entries()) {\n      const refKey = manifest.ref as unknown as string;\n      if (seenRefs.has(refKey)) {\n        ctx.addIssue({\n          code: 'custom',\n          path: ['pageManifests', index, 'ref'],\n          message: `Duplicate page ref \"${refKey}\" in WebsiteRootConfig.pageManifests`,\n        });\n      }\n      seenRefs.add(refKey);\n\n      const routeKey = manifest.routePath as unknown as string;\n      if (seenRoutePaths.has(routeKey)) {\n        ctx.addIssue({\n          code: 'custom',\n          path: ['pageManifests', index, 'routePath'],\n          message: `Duplicate routePath \"${routeKey}\" in WebsiteRootConfig.pageManifests`,\n        });\n      }\n      seenRoutePaths.add(routeKey);\n    }\n\n    /**\n     * `chromeLabelKeys` uniqueness — a duplicate is harmless at\n     * runtime (the validator de-dupes via a Set) but always indicates\n     * a copy-paste bug at the consumer's call site. Surfacing it here\n     * keeps the chrome contract tidy and matches the discipline applied\n     * to `pageManifests[].ref` and `locales`.\n     */\n    const seenChromeKeys = new Set<string>();\n    for (const [index, key] of config.chromeLabelKeys.entries()) {\n      const keyStr = key as unknown as string;\n      if (seenChromeKeys.has(keyStr)) {\n        ctx.addIssue({\n          code: 'custom',\n          path: ['chromeLabelKeys', index],\n          message: `Duplicate chrome label key \"${keyStr}\" in WebsiteRootConfig.chromeLabelKeys`,\n        });\n      }\n      seenChromeKeys.add(keyStr);\n    }\n  });\n\nexport const WebsiteRootConfigSchema: typeof _WebsiteRootConfigSchema = _WebsiteRootConfigSchema;\n\n/**\n * Runtime shape of `WebsiteRootConfig`.\n *\n * Hand-written (NOT a bare `z.infer<typeof _WebsiteRootConfigSchema>`)\n * because `z.infer` walks the schema tree and would type\n * `pageManifests[number].pageComponent`, `navigation.headerComponent`\n * and `navigation.footerComponent` as `unknown` (their schema field\n * type), losing the `ComponentType<unknown>` narrowing carried by the\n * hand-written `WebsitePageManifest` and `WebsiteNavigationConfig`\n * interfaces. Factories such as `defineWebsiteRootConfig` and the\n * layout primitives consume `WebsiteRootConfig` and must see those\n * fields pre-narrowed; otherwise every consumer would need a local\n * `as ComponentType` cast at the JSX call site, defeating the type-safe\n * component contract.\n *\n * The `Omit` + intersection pattern keeps the rest of the inferred\n * shape (`designTokens`, `seo`, `chromeLabelKeys`,\n * `skipToMainContentLabelKey`) sourced directly from the schema.\n */\nexport type WebsiteRootConfig = Omit<\n  z.infer<typeof _WebsiteRootConfigSchema>,\n  'pageManifests' | 'navigation'\n> & {\n  pageManifests: WebsitePageManifest[];\n  navigation: WebsiteNavigationConfig;\n};\n/** @wildo_source:part:end saas.website.root-config.schema */\n"]}

package/dist/esm/schemas/refs/page-ref.schemas.d.ts

@@ -0,0 +1,40 @@
+import { z } from 'zod';
+/**
+ * @wildo_source:part:start saas.website.refs.page facet:layer:shared facet:family:website
+ *
+ * `WebsitePageRef` — branded kebab-case identifier for a single marketing-site
+ * page (e.g. `'landing'`, `'pricing'`, `'contact-us'`).
+ *
+ * The ref is the **structural identity** of a page across three independent
+ * surfaces:
+ *
+ * 1. **Label-key root**: every label key the page consumes is derived as
+ *    `website.<pageRef>.<sectionRef>.<slot>` (see `WebsiteLabelKeySchema`).
+ *    Renaming a `WebsitePageRef` therefore renames every label key the
+ *    page commits to — handle as a labelled rename, never a silent edit.
+ * 2. **Manifest registry key**: `WebsiteRootConfig.pageManifests[]` is keyed
+ *    by `ref`; the Astro adapter looks pages up by ref when resolving
+ *    cross-page links (`hreflang`, locale switcher, primary nav).
+ * 3. **Skill mapping**: skills like `website-page-authoring` reference the
+ *    ref vocabulary documented here, NOT individual page files.
+ *
+ * **Format**: lowercase ASCII letters, digits and `-`. Must start with a
+ * letter (no leading digit / hyphen). 1–64 characters. The format is the
+ * smallest set that survives URL paths, file names, JSON keys and i18n keys
+ * without escaping or case-folding.
+ *
+ * **Why a brand**: prevents accidental cross-talk with `WebsiteSectionRef`
+ * (also kebab-case) and with arbitrary user-supplied strings. Consumers must
+ * go through `WebsitePageRefSchema.parse(...)` (or the manifest factory)
+ * before a value flows into label-key resolution or routing.
+ *
+ * @example
+ *   const ref = WebsitePageRefSchema.parse('landing');
+ *   // ref: WebsitePageRef ("landing")
+ */
+declare const _WebsitePageRefSchema: z.core.$ZodBranded<z.ZodString, "WebsitePageRef", "out">;
+export declare const WebsitePageRefSchema: typeof _WebsitePageRefSchema;
+export type WebsitePageRef = z.infer<typeof _WebsitePageRefSchema>;
+export {};
+/** @wildo_source:part:end saas.website.refs.page */
+//# sourceMappingURL=page-ref.schemas.d.ts.map

package/dist/esm/schemas/refs/page-ref.schemas.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"page-ref.schemas.d.ts","sourceRoot":"","sources":["../../../../../src/schemas/refs/page-ref.schemas.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgCG;AACH,QAAA,MAAM,qBAAqB,0DAQC,CAAC;AAE7B,eAAO,MAAM,oBAAoB,EAAE,OAAO,qBAA6C,CAAC;AAExF,MAAM,MAAM,cAAc,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,qBAAqB,CAAC,CAAC;;AACnE,oDAAoD"}

package/dist/esm/schemas/refs/page-ref.schemas.js

@@ -0,0 +1,43 @@
+import { z } from 'zod';
+/**
+ * @wildo_source:part:start saas.website.refs.page facet:layer:shared facet:family:website
+ *
+ * `WebsitePageRef` — branded kebab-case identifier for a single marketing-site
+ * page (e.g. `'landing'`, `'pricing'`, `'contact-us'`).
+ *
+ * The ref is the **structural identity** of a page across three independent
+ * surfaces:
+ *
+ * 1. **Label-key root**: every label key the page consumes is derived as
+ *    `website.<pageRef>.<sectionRef>.<slot>` (see `WebsiteLabelKeySchema`).
+ *    Renaming a `WebsitePageRef` therefore renames every label key the
+ *    page commits to — handle as a labelled rename, never a silent edit.
+ * 2. **Manifest registry key**: `WebsiteRootConfig.pageManifests[]` is keyed
+ *    by `ref`; the Astro adapter looks pages up by ref when resolving
+ *    cross-page links (`hreflang`, locale switcher, primary nav).
+ * 3. **Skill mapping**: skills like `website-page-authoring` reference the
+ *    ref vocabulary documented here, NOT individual page files.
+ *
+ * **Format**: lowercase ASCII letters, digits and `-`. Must start with a
+ * letter (no leading digit / hyphen). 1–64 characters. The format is the
+ * smallest set that survives URL paths, file names, JSON keys and i18n keys
+ * without escaping or case-folding.
+ *
+ * **Why a brand**: prevents accidental cross-talk with `WebsiteSectionRef`
+ * (also kebab-case) and with arbitrary user-supplied strings. Consumers must
+ * go through `WebsitePageRefSchema.parse(...)` (or the manifest factory)
+ * before a value flows into label-key resolution or routing.
+ *
+ * @example
+ *   const ref = WebsitePageRefSchema.parse('landing');
+ *   // ref: WebsitePageRef ("landing")
+ */
+const _WebsitePageRefSchema = z
+    .string()
+    .min(1, { error: 'WebsitePageRef must be at least 1 character' })
+    .max(64, { error: 'WebsitePageRef must be at most 64 characters' })
+    .regex(/^[a-z][a-z0-9-]*$/, { error: 'WebsitePageRef must be lowercase kebab-case starting with a letter (e.g. "landing", "pricing-tiers")' })
+    .brand();
+export const WebsitePageRefSchema = _WebsitePageRefSchema;
+/** @wildo_source:part:end saas.website.refs.page */
+//# sourceMappingURL=page-ref.schemas.js.map

package/dist/esm/schemas/refs/page-ref.schemas.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"page-ref.schemas.js","sourceRoot":"","sources":["../../../../../src/schemas/refs/page-ref.schemas.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgCG;AACH,MAAM,qBAAqB,GAAG,CAAC;KAC5B,MAAM,EAAE;KACR,GAAG,CAAC,CAAC,EAAE,EAAE,KAAK,EAAE,6CAA6C,EAAE,CAAC;KAChE,GAAG,CAAC,EAAE,EAAE,EAAE,KAAK,EAAE,8CAA8C,EAAE,CAAC;KAClE,KAAK,CACJ,mBAAmB,EACnB,EAAE,KAAK,EAAE,sGAAsG,EAAE,CAClH;KACA,KAAK,EAAoB,CAAC;AAE7B,MAAM,CAAC,MAAM,oBAAoB,GAAiC,qBAAqB,CAAC;AAGxF,oDAAoD","sourcesContent":["import { z } from 'zod';\n\n/**\n * @wildo_source:part:start saas.website.refs.page facet:layer:shared facet:family:website\n *\n * `WebsitePageRef` — branded kebab-case identifier for a single marketing-site\n * page (e.g. `'landing'`, `'pricing'`, `'contact-us'`).\n *\n * The ref is the **structural identity** of a page across three independent\n * surfaces:\n *\n * 1. **Label-key root**: every label key the page consumes is derived as\n *    `website.<pageRef>.<sectionRef>.<slot>` (see `WebsiteLabelKeySchema`).\n *    Renaming a `WebsitePageRef` therefore renames every label key the\n *    page commits to — handle as a labelled rename, never a silent edit.\n * 2. **Manifest registry key**: `WebsiteRootConfig.pageManifests[]` is keyed\n *    by `ref`; the Astro adapter looks pages up by ref when resolving\n *    cross-page links (`hreflang`, locale switcher, primary nav).\n * 3. **Skill mapping**: skills like `website-page-authoring` reference the\n *    ref vocabulary documented here, NOT individual page files.\n *\n * **Format**: lowercase ASCII letters, digits and `-`. Must start with a\n * letter (no leading digit / hyphen). 1–64 characters. The format is the\n * smallest set that survives URL paths, file names, JSON keys and i18n keys\n * without escaping or case-folding.\n *\n * **Why a brand**: prevents accidental cross-talk with `WebsiteSectionRef`\n * (also kebab-case) and with arbitrary user-supplied strings. Consumers must\n * go through `WebsitePageRefSchema.parse(...)` (or the manifest factory)\n * before a value flows into label-key resolution or routing.\n *\n * @example\n *   const ref = WebsitePageRefSchema.parse('landing');\n *   // ref: WebsitePageRef (\"landing\")\n */\nconst _WebsitePageRefSchema = z\n  .string()\n  .min(1, { error: 'WebsitePageRef must be at least 1 character' })\n  .max(64, { error: 'WebsitePageRef must be at most 64 characters' })\n  .regex(\n    /^[a-z][a-z0-9-]*$/,\n    { error: 'WebsitePageRef must be lowercase kebab-case starting with a letter (e.g. \"landing\", \"pricing-tiers\")' },\n  )\n  .brand<'WebsitePageRef'>();\n\nexport const WebsitePageRefSchema: typeof _WebsitePageRefSchema = _WebsitePageRefSchema;\n\nexport type WebsitePageRef = z.infer<typeof _WebsitePageRefSchema>;\n/** @wildo_source:part:end saas.website.refs.page */\n"]}

package/dist/esm/schemas/refs/section-ref.schemas.d.ts

@@ -0,0 +1,41 @@
+import { z } from 'zod';
+/**
+ * @wildo_source:part:start saas.website.refs.section facet:layer:shared facet:family:website
+ *
+ * `WebsiteSectionRef` — branded kebab-case identifier for one section on a
+ * page (e.g. `'hero'`, `'social-proof'`, `'pricing-teaser'`, `'final-cta'`).
+ *
+ * The section ref is the **section-level structural identity**:
+ *
+ * 1. **Label-key root**: every label leaf consumed inside a section is
+ *    rooted at `website.<pageRef>.<sectionRef>.<slot>`. The hook
+ *    `useWebsiteLabel('headline')` (Phase 2) reads `WebsiteSectionContext`
+ *    to derive the full key; the section author never types the page or
+ *    section ref into a label call.
+ * 2. **Page manifest contract**: `WebsitePageManifest.sectionRefs[]`
+ *    declares the refs the page commits to. The label-pack validator
+ *    cross-references the manifest's declared refs against the actual
+ *    sections rendered, surfacing mismatches at build start.
+ * 3. **DOM landmark**: `<WebsiteSection ref="…">` (Phase 2) emits
+ *    `<section data-section-ref="…">` so analytics, scroll-tracking, and
+ *    automated audits can identify sections without parsing class names.
+ *
+ * **Format**: lowercase ASCII letters, digits and `-`. Must start with a
+ * letter. 1–64 characters. Same shape as `WebsitePageRef` for consistency
+ * across both ref scopes.
+ *
+ * **Why a brand**: same reasoning as `WebsitePageRef`. The two refs are
+ * structurally identical strings but semantically distinct — branding
+ * prevents accidental swaps between page-level and section-level APIs at
+ * compile time.
+ *
+ * @example
+ *   const heroRef = WebsiteSectionRefSchema.parse('hero');
+ *   const ctaRef = WebsiteSectionRefSchema.parse('final-cta');
+ */
+declare const _WebsiteSectionRefSchema: z.core.$ZodBranded<z.ZodString, "WebsiteSectionRef", "out">;
+export declare const WebsiteSectionRefSchema: typeof _WebsiteSectionRefSchema;
+export type WebsiteSectionRef = z.infer<typeof _WebsiteSectionRefSchema>;
+export {};
+/** @wildo_source:part:end saas.website.refs.section */
+//# sourceMappingURL=section-ref.schemas.d.ts.map

package/dist/esm/schemas/refs/section-ref.schemas.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"section-ref.schemas.d.ts","sourceRoot":"","sources":["../../../../../src/schemas/refs/section-ref.schemas.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAiCG;AACH,QAAA,MAAM,wBAAwB,6DAQC,CAAC;AAEhC,eAAO,MAAM,uBAAuB,EAAE,OAAO,wBAAmD,CAAC;AAEjG,MAAM,MAAM,iBAAiB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,wBAAwB,CAAC,CAAC;;AACzE,uDAAuD"}