@getvitops/generator 8.2.0 → 8.3.0-alpha.1

package/config.schema.json

@@ -68,6 +68,10 @@
                                 "type": "string"
                               },
                               "description": "Step → colour overrides (hex or oklch()) pinned VERBATIM at those steps. Every other step takes its lightness from the shared ladder, with chroma and hue interpolated between the anchors — so an anchor is reproduced exactly and is the only step allowed off the ladder. An explicit anchor overrides the seed at that step; two anchors that resolve to the same step are an error."
+                            },
+                            "acknowledgeOffLadder": {
+                              "type": "boolean",
+                              "description": "Acknowledge that this hue deliberately pins colours off the shared lightness ladder (typically to match an existing brand palette exactly). Silences the per-step \"off the ladder\" build warnings for THIS hue only; the monotonicity and contrast checks still run."
                             }
                           },
                           "required": [
@@ -98,6 +102,10 @@
                                 }
                               ],
                               "description": "Fixed brand kit: authored tones placed verbatim at their nearest steps plus tinted off-white/off-black endpoints; no interpolation. Either an ordered light → dark array or a step → colour map."
+                            },
+                            "acknowledgeOffLadder": {
+                              "type": "boolean",
+                              "description": "Acknowledge that this hue deliberately pins colours off the shared lightness ladder (typically to match an existing brand palette exactly). Silences the per-step \"off the ladder\" build warnings for THIS hue only; the monotonicity and contrast checks still run."
                             }
                           },
                           "required": [
@@ -135,6 +143,21 @@
                                 "chromatic"
                               ],
                               "description": "`surface` — a page/panel colour: gets a bare `bg-<role>` plus the full emphasis range and text scale. `chromatic` (default) — a signal colour: tints and solids only, no bare `bg-<role>`."
+                            },
+                            "solid": {
+                              "description": "Ramp step (100…900) the role's solid family starts from; default 600. `bg-<role>-solid` is this step and `-solid-bold` / `-solid-x-bold` walk one and two rungs DARKER, so `solid: 400` gives 400 → 500 → 600. Use it when the brand colour is bright and lives lower on the ramp (a yellow at 400) instead of reaching for raw `bg-<hue>-<step>` classes. Like the default family it is the same in light and dark. The contrast check still runs on the pair this produces.",
+                              "type": [
+                                "number",
+                                "string"
+                              ]
+                            },
+                            "foreground": {
+                              "type": "string",
+                              "enum": [
+                                "light",
+                                "dark"
+                              ],
+                              "description": "Polarity of `text-on-<role>`, the foreground for a filled surface. Default is whichever of near-white / near-black has more contrast on the solid. Set `\"dark\"` so a bright fill carries dark text (or `\"light\"` for the reverse). The build still fails if the forced pair is below APCA Lc 60."
                             }
                           },
                           "required": [
@@ -164,13 +187,31 @@
                 "additionalProperties": false
               },
               "shadows": {
-                "description": "Named shadows → `--shadow-<name>` tokens and `.drop-shadow-<name>` utilities. Values are shadow parameter lists (offset/blur/colour). Each token feeds two consumers with different grammars — `box-shadow` (pattern geometry, via the `--ds-*` group aliases) and `filter: drop-shadow(…)` (the utilities and the `shadow:` state shortcut) — so values must stay in the intersection: **one layer, no spread radius, no `inset`**. `drop-shadow()` rejects all three, and rejecting them invalidates the whole filter, so the shadow vanishes rather than degrading.",
+                "description": "Named shadows → `--shadow-<name>` tokens and `.drop-shadow-<name>` utilities. A value is either a string (below) or `{ \"box\"?: string, \"drop\"?: string }` for a shadow that needs the two grammars to differ: `box` is what `--shadow-<name>` holds and what `box-shadow` consumers (pattern geometry, `--ds-*`) read, so it MAY use spread, `inset` and several layers; `drop` is emitted as `--shadow-<name>-drop` and is what `.drop-shadow-<name>` and the `shadow:` state shortcut read, so it must obey the drop-shadow() limits. Omit `drop` and no drop-shadow utility is emitted for that name; omit `box` and `--shadow-<name>` takes the `drop` value. The plain string form keeps working and feeds both consumers from one value. For that string form: each token feeds two consumers with different grammars — `box-shadow` (pattern geometry, via the `--ds-*` group aliases) and `filter: drop-shadow(…)` (the utilities and the `shadow:` state shortcut) — so values must stay in the intersection: **one layer, no spread radius, no `inset`**. `drop-shadow()` rejects all three, and rejecting them invalidates the whole filter, so the shadow vanishes rather than degrading.",
                 "type": "object",
                 "propertyNames": {
                   "type": "string"
                 },
                 "additionalProperties": {
-                  "type": "string"
+                  "anyOf": [
+                    {
+                      "type": "string"
+                    },
+                    {
+                      "type": "object",
+                      "properties": {
+                        "box": {
+                          "type": "string",
+                          "description": "`box-shadow` value: spread, `inset` and multiple layers allowed."
+                        },
+                        "drop": {
+                          "type": "string",
+                          "description": "`drop-shadow()` value: one layer, at most three lengths, no `inset`."
+                        }
+                      },
+                      "additionalProperties": false
+                    }
+                  ]
                 }
               },
               "fonts": {
@@ -184,7 +225,7 @@
                 }
               },
               "typeScale": {
-                "description": "Fluid modular TYPE scale → `--text-<name>` tokens, consumed by typography roles and text-size utilities.",
+                "description": "Fluid modular TYPE scale → `--text-<name>` tokens, consumed by typography roles and text-size utilities.\n\n**Recipe for marketing headings:** one ratio cannot serve both a ~16px body and a ~76px hero — a ratio big enough for the hero collapses the small end to unreadable. Extend `names` upward instead of raising the ratio: keep `base` ≈ \"1rem\" at the body step, `ratio` ≈ 1.2 at `maxVw` (≈ 1.125–1.15 `minRatio` at `minVw` so headings tame on phones), and add names (`4xl`, `5xl`) for the display sizes — the steps above `baseStep` are what headings read, the steps below it only need `xs`/`sm`. Aim the largest named step at your hero (≈ 4.5–5rem at `maxVw`), then point the `display`/`title` roles at those steps rather than hand-writing `clamp()` in a role. If a step still needs its own value, set that role's `size` literally — roles may bypass the scale.",
                 "type": "object",
                 "properties": {
                   "base": {
@@ -245,6 +286,55 @@
                 ],
                 "additionalProperties": false
               },
+              "layout": {
+                "type": "object",
+                "properties": {
+                  "widths": {
+                    "type": "object",
+                    "properties": {
+                      "measure": {
+                        "type": "string",
+                        "description": "Reading column → `--width-measure` (framework default 65ch)."
+                      },
+                      "breakout": {
+                        "type": "string",
+                        "description": "`.breakout` track → `--width-breakout` (default 90ch)."
+                      },
+                      "spotlight": {
+                        "type": "string",
+                        "description": "`.spotlight` track → `--width-spotlight` (default 120ch)."
+                      },
+                      "nav": {
+                        "type": "string",
+                        "description": "Navigation column beside content → `--width-nav` (default 16rem)."
+                      }
+                    },
+                    "additionalProperties": false,
+                    "description": "Content track widths for `.centered`. In `ch` so the reading measure stays character-based; keep measure ≤ breakout ≤ spotlight."
+                  },
+                  "regionSpace": {
+                    "type": "object",
+                    "properties": {
+                      "min": {
+                        "type": "string",
+                        "description": "Floor → `--region-space-min` (default 3rem)."
+                      },
+                      "preferred": {
+                        "type": "string",
+                        "description": "Preferred value → `--region-space` (default 8vh)."
+                      },
+                      "max": {
+                        "type": "string",
+                        "description": "Ceiling → `--region-space-max` (default 8rem)."
+                      }
+                    },
+                    "additionalProperties": false,
+                    "description": "Vertical padding of `.region`: `padding-block: clamp(min, preferred, max)`."
+                  }
+                },
+                "additionalProperties": false,
+                "description": "Optional layout tokens. Each key you set is emitted as a `:root` custom property (css, bricks and tailwind formats); each you omit keeps the framework default. Lets the live editor tune widths and region spacing instead of a hand-written override stylesheet."
+              },
               "spaceScale": {
                 "description": "Fluid modular SPACE scale → `--space-<name>` tokens, consumed by spacing/gap utilities and vertical rhythm.",
                 "type": "object",
@@ -466,7 +556,7 @@
                           "number"
                         ]
                       },
-                      "description": "A bag of CSS-ish keys, each mapped to a declaration plus a `--<role>-<sfx>` override hook. The recognised set is **closed**: `family`, `size`, `weight`, `style`, `line-height`, `tracking` (→ `letter-spacing`), `text-transform`, `text-decoration`, `text-wrap`, `color`. Note the last four are spelled with their full CSS property names — `transform` and `decoration` are NOT accepted. Anything unrecognised is **ignored**, not passed through, so the generator warns rather than emitting it: a silently-dropped `transform: uppercase` is how title-case navigation reaches production. Note also that `style`, `text-transform`, `text-decoration` and `text-wrap` are emitted on **every** role at their identity value (`normal`/`none`/`none`/`wrap`) whether declared or not, so applying one role class over another fully resets it — which means **omitting `text-wrap` is not \"inherit\"**: it emits `text-wrap: wrap` and cancels the `pretty` the role would otherwise inherit from a `pretty` ancestor such as a `body`-mapped role. Declare it on every role — `balance` for heading-like roles, `pretty` for copy, `wrap` for short single-line labels."
+                      "description": "A bag of CSS-ish keys, each mapped to a declaration plus a `--<role>-<sfx>` override hook. The recognised set is **closed**: `family`, `size`, `weight`, `style`, `line-height`, `tracking` (→ `letter-spacing`), `text-transform`, `text-decoration`, `text-wrap`, `color`. The canonical spellings of the last four are their full CSS property names (`text-transform`, `text-decoration`, …); `transform` and `decoration` are accepted as aliases of the first two and normalised to them. Anything unrecognised is **ignored**, not passed through, so the generator warns rather than emitting it: a silently-dropped key (a typo for `text-transform`, say) is how title-case navigation reaches production. Note also that `style`, `text-transform`, `text-decoration` and `text-wrap` are emitted on **every** role at their identity value (`normal`/`none`/`none`/`wrap`) whether declared or not, so applying one role class over another fully resets it — which means **omitting `text-wrap` is not \"inherit\"**: it emits `text-wrap: wrap` and cancels the `pretty` the role would otherwise inherit from a `pretty` ancestor such as a `body`-mapped role. Declare it on every role — `balance` for heading-like roles, `pretty` for copy, `wrap` for short single-line labels."
                     }
                   },
                   "headings": {
@@ -604,7 +694,7 @@
           "type": "string"
         },
         "defaultColorScheme": {
-          "description": "Initial appearance. `\"system\"` follows the OS via `prefers-color-scheme` and is what makes `<wc-color-scheme-toggle>`'s \"System\" position resolve to anything — it removes the theme attribute, so without this the page falls through to light. It also gives a no-JS page the OS appearance. Defaults to `\"light\"`, because switching an existing site to `\"system\"` visibly flips it dark for dark-OS visitors.",
+          "description": "Initial appearance. `\"dark\"` makes the site DARK-ONLY: the dark tokens become the `:root` appearance (with `color-scheme: dark`), no light block or `data-theme` flip is emitted, and the light-mode contrast checks are skipped — so a palette that only works dark (bright fills with dark text, for example) builds. Do not ship `<wc-color-scheme-toggle>` on such a site. `\"system\"` follows the OS via `prefers-color-scheme` and is what makes `<wc-color-scheme-toggle>`'s \"System\" position resolve to anything — it removes the theme attribute, so without this the page falls through to light. It also gives a no-JS page the OS appearance. Defaults to `\"light\"`, because switching an existing site to `\"system\"` visibly flips it dark for dark-OS visitors.",
           "type": "string",
           "enum": [
             "light",
@@ -694,6 +784,7 @@
           "type": "object",
           "properties": {
             "streetAddress": {
+              "description": "Street line. Optional: a business with no public street address (home-based, service-area) omits it, and the generated legal documents and JSON-LD simply leave the line out.",
               "type": "string"
             },
             "addressLocality": {
@@ -713,12 +804,28 @@
             }
           },
           "required": [
-            "streetAddress",
             "addressLocality",
             "addressCountry"
           ],
           "additionalProperties": false
         },
+        "description": {
+          "description": "One or two sentences on what the organization does → JSON-LD `description` and a fallback for SEO. Localisable.",
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "object",
+              "propertyNames": {
+                "type": "string"
+              },
+              "additionalProperties": {
+                "type": "string"
+              }
+            }
+          ]
+        },
         "taxID": {
           "description": "Tax identification number.",
           "type": "string"
@@ -759,6 +866,7 @@
                   "type": "object",
                   "properties": {
                     "streetAddress": {
+                      "description": "Street line. Optional: a business with no public street address (home-based, service-area) omits it, and the generated legal documents and JSON-LD simply leave the line out.",
                       "type": "string"
                     },
                     "addressLocality": {
@@ -778,7 +886,6 @@
                     }
                   },
                   "required": [
-                    "streetAddress",
                     "addressLocality",
                     "addressCountry"
                   ],
@@ -849,6 +956,7 @@
                 "type": "object",
                 "properties": {
                   "streetAddress": {
+                    "description": "Street line. Optional: a business with no public street address (home-based, service-area) omits it, and the generated legal documents and JSON-LD simply leave the line out.",
                     "type": "string"
                   },
                   "addressLocality": {
@@ -868,7 +976,6 @@
                   }
                 },
                 "required": [
-                  "streetAddress",
                   "addressLocality",
                   "addressCountry"
                 ],
@@ -2954,7 +3061,8 @@
               "description": "Which legal template set the generated documents use. Default `ca`.",
               "type": "string",
               "enum": [
-                "ca"
+                "ca",
+                "qc"
               ]
             },
             "privacyPolicy": {
@@ -2995,6 +3103,7 @@
                           "type": "object",
                           "properties": {
                             "streetAddress": {
+                              "description": "Street line. Optional: a business with no public street address (home-based, service-area) omits it, and the generated legal documents and JSON-LD simply leave the line out.",
                               "type": "string"
                             },
                             "addressLocality": {
@@ -3014,7 +3123,6 @@
                             }
                           },
                           "required": [
-                            "streetAddress",
                             "addressLocality",
                             "addressCountry"
                           ],
@@ -3026,6 +3134,14 @@
                     }
                   ]
                 },
+                "privacyOfficerTitle": {
+                  "description": "Title of the person in charge of the protection of personal information (e.g. \"President\"). Quebec Law 25 requires the title and contact details to be published; the `qc` templates print it beside the `privacyOfficer` contact. Not asserted when absent.",
+                  "type": "string"
+                },
+                "impactAssessments": {
+                  "description": "Attests that a privacy impact assessment is carried out before personal information is communicated outside Quebec (Law 25, s. 17). The `qc` privacy policy states that assurance only when this is `true` — a fact the config cannot otherwise know, so it is never assumed.",
+                  "type": "boolean"
+                },
                 "retention": {
                   "description": "How long personal information is kept, in prose (e.g. \"24 months after last contact\").",
                   "type": "string"

package/dist/{config-BfcWKH-5.mjs → config-D5xuz8--.mjs}

@@ -1,4 +1,4 @@
-import { a as expandPalette, b as roleHue, d as tokenVar, g as ROLE_TOKEN_KEYS, h as REQUIRED_ROLES, o as functionalRole, x as roleKind } from "./tokens-C1RJwFeG.mjs";
+import { C as roleKind, S as roleHue, _ as ROLE_TOKEN_KEYS, a as expandPalette, d as tokenVar, g as REQUIRED_ROLES, n as NUMERIC_STEPS, o as functionalRole } from "./tokens-CaIGQQLk.mjs";
 import { AD_PROVIDERS, AdPropertySchema, AdProviderSchema, BIGIN_DATA_CENTERS, CRM_PROVIDERS, CrmSchema, DeploymentSchema, IndexNowSchema, IndexingSchema, LocalizableSchema, NotificationsSchema, ReviewLocationSchema, ReviewsSchema, SearchConsoleSchema, SearchConsoleSetupSchema, SecuritySchema, SeoSchema, TrackingSchema, desc } from "@getvitops/config";
 import * as z from "@zod/mini";
 import { AD_PLATFORMS } from "@getvitops/utils/ads";
@@ -311,11 +311,16 @@ function tokenRefIssues(ds) {
 const CssDecls = desc(z.record(z.string(), z.string()), "A CSS declaration block: property → value. Values stay strings (they can be hex, var(), clamp(), keywords, …); the generator, not the schema, interprets them.");
 const Scalar = z.union([z.string(), z.number()]);
 const VarMap = z.record(z.string(), Scalar);
+const AckOffLadder = z.optional(desc(z.boolean(), "Acknowledge that this hue deliberately pins colours off the shared lightness ladder (typically to match an existing brand palette exactly). Silences the per-step \"off the ladder\" build warnings for THIS hue only; the monotonicity and contrast checks still run."));
 const SeededRamp = desc(z.strictObject({
 	seed: desc(z.string(), "Seed colour (hex or oklch()). An 11-step numeric scale (50…950, tinted near-white → tinted near-black) is generated in OKLCH from it; the seed is preserved at its natural step."),
-	anchors: z.optional(desc(z.record(z.string(), z.string()), "Step → colour overrides (hex or oklch()) pinned VERBATIM at those steps. Every other step takes its lightness from the shared ladder, with chroma and hue interpolated between the anchors — so an anchor is reproduced exactly and is the only step allowed off the ladder. An explicit anchor overrides the seed at that step; two anchors that resolve to the same step are an error."))
+	anchors: z.optional(desc(z.record(z.string(), z.string()), "Step → colour overrides (hex or oklch()) pinned VERBATIM at those steps. Every other step takes its lightness from the shared ladder, with chroma and hue interpolated between the anchors — so an anchor is reproduced exactly and is the only step allowed off the ladder. An explicit anchor overrides the seed at that step; two anchors that resolve to the same step are an error.")),
+	acknowledgeOffLadder: AckOffLadder
 }), "Seeded hue: the 11-step scale is GENERATED in OKLCH from `seed` (anchors pin specific steps).");
-const FixedRamp = desc(z.strictObject({ tones: desc(z.union([z.array(z.string()), z.record(z.string(), z.string())]), "Fixed brand kit: authored tones placed verbatim at their nearest steps plus tinted off-white/off-black endpoints; no interpolation. Either an ordered light → dark array or a step → colour map.") }), "Fixed hue: authored brand tones used verbatim; no generation.");
+const FixedRamp = desc(z.strictObject({
+	tones: desc(z.union([z.array(z.string()), z.record(z.string(), z.string())]), "Fixed brand kit: authored tones placed verbatim at their nearest steps plus tinted off-white/off-black endpoints; no interpolation. Either an ordered light → dark array or a step → colour map."),
+	acknowledgeOffLadder: AckOffLadder
+}), "Fixed hue: authored brand tones used verbatim; no generation.");
 const Ramp = desc(z.union([SeededRamp, FixedRamp]), "A palette hue, authored one of two ways: `{ seed, anchors? }` generates an 11-step numeric OKLCH scale (50…950) from the seed, or `{ tones }` supplies a fixed brand kit used verbatim.");
 /**
 * A role points at a hue, and optionally declares its kind. The bare-string form
@@ -324,7 +329,9 @@ const Ramp = desc(z.union([SeededRamp, FixedRamp]), "A palette hue, authored one
 */
 const RoleSpecSchema = z.union([desc(z.string(), "A palette hue name. Shorthand for `{ hue, kind: \"chromatic\" }`."), z.strictObject({
 	hue: desc(z.string(), "The palette hue this role resolves to."),
-	kind: z.optional(desc(z.enum(["surface", "chromatic"]), "`surface` — a page/panel colour: gets a bare `bg-<role>` plus the full emphasis range and text scale. `chromatic` (default) — a signal colour: tints and solids only, no bare `bg-<role>`."))
+	kind: z.optional(desc(z.enum(["surface", "chromatic"]), "`surface` — a page/panel colour: gets a bare `bg-<role>` plus the full emphasis range and text scale. `chromatic` (default) — a signal colour: tints and solids only, no bare `bg-<role>`.")),
+	solid: z.optional(desc(z.union([z.number(), z.string()]), "Ramp step (100…900) the role's solid family starts from; default 600. `bg-<role>-solid` is this step and `-solid-bold` / `-solid-x-bold` walk one and two rungs DARKER, so `solid: 400` gives 400 → 500 → 600. Use it when the brand colour is bright and lives lower on the ramp (a yellow at 400) instead of reaching for raw `bg-<hue>-<step>` classes. Like the default family it is the same in light and dark. The contrast check still runs on the pair this produces.")),
+	foreground: z.optional(desc(z.enum(["light", "dark"]), "Polarity of `text-on-<role>`, the foreground for a filled surface. Default is whichever of near-white / near-black has more contrast on the solid. Set `\"dark\"` so a bright fill carries dark text (or `\"light\"` for the reverse). The build still fails if the forced pair is below APCA Lc 60."))
 })]);
 const UtilityName = z.enum([
 	"bg",
@@ -337,9 +344,13 @@ const UtilityName = z.enum([
 ]);
 const Colors = desc(z.strictObject({
 	palette: desc(z.record(z.string(), Ramp), "Palette hues by name. Each becomes an 11-step numeric OKLCH scale (`--color-<hue>-50…950`). Every ramp shares one fixed lightness ladder, so a step means the same lightness in every hue; only chroma and hue vary. Beyond the outermost authored colour the chroma decays towards a small endpoint value (0.008 light / 0.015 dark) so the near-white and near-black ends keep a whisper of the hue — but that is a **ceiling**, not a target, so a low-chroma seed stays low and **a chroma-0 seed gives a true neutral** rather than a tinted one. The ladder is also enforced: if pinned colours leave a ramp non-monotonic (some step darker than the one below it), the build fails rather than shipping a scale whose hover states run backwards."),
-	roles: desc(z.record(z.string(), RoleSpecSchema), `Maps semantic role names onto palette hues. Role names are ARBITRARY — add a key and the generator emits that role's token set (\`--color-<target>-<role>[-<variant>]\` for target bg/text/icon/border), its dark-mode flip and its utility classes.\n\nA value is either a hue name (\`"danger": "rust"\`) or \`{ "hue": …, "kind": "surface" | "chromatic" }\`. **The kind decides the shape of the token set.** \`chromatic\` (the default, and what the bare-string form means) is a signal colour: its backgrounds split into tints (\`bg-<role>-x-muted\`/\`-muted\`) and solids (\`bg-<role>-solid[-bold|-x-bold]\`), with deliberately **no bare \`bg-<role>\`** — "how loud?" is a question the author answers. \`surface\` is a page/panel colour: it has a bare \`bg-<role>\` plus the full emphasis range and text scale.\n\nDark mode flips automatically; there is no per-appearance scheme grammar. The solid family and its computed \`text-on-<role>\` foreground stay mode-stable so a filled button keeps its identity. Six roles are a required core, because the shipped framework CSS references them with no fallback: ${REQUIRED_ROLES.join(", ")}. Conventional additions are ui-secondary/accent, brand-secondary, info and success.`),
+	roles: desc(z.record(z.string(), RoleSpecSchema), `Maps semantic role names onto palette hues. Role names are ARBITRARY — add a key and the generator emits that role's token set (\`--color-<target>-<role>[-<variant>]\` for target bg/text/icon/border), its dark-mode flip and its utility classes.\n\nA value is either a hue name (\`"danger": "rust"\`) or \`{ "hue": …, "kind": "surface" | "chromatic" }\`. **The kind decides the shape of the token set.** \`chromatic\` (the default, and what the bare-string form means) is a signal colour: its backgrounds split into tints (\`bg-<role>-x-muted\`/\`-muted\`) and solids (\`bg-<role>-solid[-bold|-x-bold]\`), with deliberately **no bare \`bg-<role>\`** — "how loud?" is a question the author answers. \`surface\` is a page/panel colour: it has a bare \`bg-<role>\` plus the full emphasis range and text scale.\n\nDark mode flips automatically; there is no per-appearance scheme grammar. The solid family and its computed \`text-on-<role>\` foreground stay mode-stable so a filled button keeps its identity. \n\n**Contrast is enforced at build time, in both appearances** (APCA Lc): body text ≥ 75, secondary and muted text (\`text-muted\`) ≥ **60 against the page plane** it sits on, icons and guaranteed boundaries ≥ 45, and \`text-on-<role>\` ≥ 60 on the role's solid. So a mockup's muted grey that lands near Lc 57 fails the build — lighten the anchor on a dark page (or darken it on a light one) until it clears 60. \`text-x-muted\`/\`text-xx-muted\` are exempt (placeholders, disabled). A role can move its fill off the default step 600 with \`solid\`, and pin the polarity of its on-colour with \`foreground\`; a dark-only site (\`defaultColorScheme: "dark"\`) is only checked in dark. Six roles are a required core, because the shipped framework CSS references them with no fallback: ${REQUIRED_ROLES.join(", ")}. Conventional additions are ui-secondary/accent, brand-secondary, info and success.`),
 	utilities: z.optional(desc(z.array(UtilityName), "Which colour utility-class families to emit (`bg-*`, `text-*`, `icon-*`, `border-*`, `outline-*`, `fill-*`, `stroke-*`). Defaults to bg, text, icon, border. `icon` is a separate non-text tier (a glyph may run more vivid than text); `outline`/`fill`/`stroke` have no tokens of their own and alias the border and icon tiers."))
 }), "The colour system (the only required section): `palette` hues become generated OKLCH scales; `roles` map semantic roles onto those hues, from which all role tokens and dark mode derive.");
+const Shadow = z.union([z.string(), z.strictObject({
+	box: z.optional(desc(z.string(), "`box-shadow` value: spread, `inset` and multiple layers allowed.")),
+	drop: z.optional(desc(z.string(), "`drop-shadow()` value: one layer, at most three lengths, no `inset`."))
+})]);
 const Scale = z.strictObject({
 	base: desc(z.string(), "Anchor size (a CSS length, e.g. \"1rem\") — the value at `baseStep`."),
 	ratio: desc(z.number(), "Modular ratio between adjacent steps at large viewports."),
@@ -371,7 +382,7 @@ const Patterns = desc(z.strictObject({
 	z: desc(z.optional(z.record(z.string(), z.number())), "Z-index tiers → `--z-tier-<name>`."),
 	items: desc(z.optional(z.record(z.string(), Pattern)), "The component patterns to emit, keyed by name.")
 }), "Component patterns and their token cascade: `defaults` → `groups` → per-pattern `overrides`, plus shape (`radii`) and z-index primitives.");
-const TypographyRole = desc(z.record(z.string(), Scalar), "A bag of CSS-ish keys, each mapped to a declaration plus a `--<role>-<sfx>` override hook. The recognised set is **closed**: `family`, `size`, `weight`, `style`, `line-height`, `tracking` (→ `letter-spacing`), `text-transform`, `text-decoration`, `text-wrap`, `color`. Note the last four are spelled with their full CSS property names — `transform` and `decoration` are NOT accepted. Anything unrecognised is **ignored**, not passed through, so the generator warns rather than emitting it: a silently-dropped `transform: uppercase` is how title-case navigation reaches production. Note also that `style`, `text-transform`, `text-decoration` and `text-wrap` are emitted on **every** role at their identity value (`normal`/`none`/`none`/`wrap`) whether declared or not, so applying one role class over another fully resets it — which means **omitting `text-wrap` is not \"inherit\"**: it emits `text-wrap: wrap` and cancels the `pretty` the role would otherwise inherit from a `pretty` ancestor such as a `body`-mapped role. Declare it on every role — `balance` for heading-like roles, `pretty` for copy, `wrap` for short single-line labels.");
+const TypographyRole = desc(z.record(z.string(), Scalar), "A bag of CSS-ish keys, each mapped to a declaration plus a `--<role>-<sfx>` override hook. The recognised set is **closed**: `family`, `size`, `weight`, `style`, `line-height`, `tracking` (→ `letter-spacing`), `text-transform`, `text-decoration`, `text-wrap`, `color`. The canonical spellings of the last four are their full CSS property names (`text-transform`, `text-decoration`, …); `transform` and `decoration` are accepted as aliases of the first two and normalised to them. Anything unrecognised is **ignored**, not passed through, so the generator warns rather than emitting it: a silently-dropped key (a typo for `text-transform`, say) is how title-case navigation reaches production. Note also that `style`, `text-transform`, `text-decoration` and `text-wrap` are emitted on **every** role at their identity value (`normal`/`none`/`none`/`wrap`) whether declared or not, so applying one role class over another fully resets it — which means **omitting `text-wrap` is not \"inherit\"**: it emits `text-wrap: wrap` and cancels the `pretty` the role would otherwise inherit from a `pretty` ancestor such as a `body`-mapped role. Declare it on every role — `balance` for heading-like roles, `pretty` for copy, `wrap` for short single-line labels.");
 const Typography = desc(z.strictObject({
 	families: desc(z.optional(z.record(z.string(), z.string())), "Role-facing family aliases → CSS font values, usually referencing the top-level `fonts` tokens (e.g. \"var(--font-display)\")."),
 	roles: desc(z.optional(z.record(z.string(), TypographyRole)), "Semantic type roles (display, title, heading, body, quote, caption, eyebrow, code, lead, footnote, tag, …), each emitted as a `font-<role>` class."),
@@ -389,6 +400,20 @@ const Animations = desc(z.strictObject({
 		compose: desc(z.optional(z.array(z.array(z.string()))), "Combinations of base parts, each emitted as a `.<parts>-journey` class.")
 	})), "Multi-part journey classes composed from `base` building blocks.")
 }), "Animation effect + journey classes (pure value layers). The animation engine itself — keyframes, drivers, floats, utilities — is static framework CSS, not configured here.");
+const Length = z.string();
+const Layout = desc(z.strictObject({
+	widths: z.optional(desc(z.strictObject({
+		measure: z.optional(desc(Length, "Reading column → `--width-measure` (framework default 65ch).")),
+		breakout: z.optional(desc(Length, "`.breakout` track → `--width-breakout` (default 90ch).")),
+		spotlight: z.optional(desc(Length, "`.spotlight` track → `--width-spotlight` (default 120ch).")),
+		nav: z.optional(desc(Length, "Navigation column beside content → `--width-nav` (default 16rem)."))
+	}), "Content track widths for `.centered`. In `ch` so the reading measure stays character-based; keep measure ≤ breakout ≤ spotlight.")),
+	regionSpace: z.optional(desc(z.strictObject({
+		min: z.optional(desc(Length, "Floor → `--region-space-min` (default 3rem).")),
+		preferred: z.optional(desc(Length, "Preferred value → `--region-space` (default 8vh).")),
+		max: z.optional(desc(Length, "Ceiling → `--region-space-max` (default 8rem)."))
+	}), "Vertical padding of `.region`: `padding-block: clamp(min, preferred, max)`."))
+}), "Optional layout tokens. Each key you set is emitted as a `:root` custom property (css, bricks and tailwind formats); each you omit keeps the framework default. Lets the live editor tune widths and region spacing instead of a hand-written override stylesheet.");
 const DesignSystemSchema = z.strictObject({
 	$schema: desc(z.optional(z.string()), "URL of the published JSON Schema (stamped by `vitops init`) so editors provide autocomplete + validation."),
 	meta: desc(z.optional(z.strictObject({
@@ -396,9 +421,10 @@ const DesignSystemSchema = z.strictObject({
 		description: desc(z.optional(z.string()), "One or two sentences on the brand personality and the feeling the UI should evoke — what an agent needs when no token answers the question. Becomes the DESIGN.md `description` field and opens its Overview section; if omitted, a generic description of the system's mechanics is used instead.")
 	})), "Brand identity for agent-facing output. Consumed only by the `design` format (`DESIGN.md`); it emits no CSS and no tokens."),
 	colors: Colors,
-	shadows: desc(z.optional(z.record(z.string(), z.string())), "Named shadows → `--shadow-<name>` tokens and `.drop-shadow-<name>` utilities. Values are shadow parameter lists (offset/blur/colour). Each token feeds two consumers with different grammars — `box-shadow` (pattern geometry, via the `--ds-*` group aliases) and `filter: drop-shadow(…)` (the utilities and the `shadow:` state shortcut) — so values must stay in the intersection: **one layer, no spread radius, no `inset`**. `drop-shadow()` rejects all three, and rejecting them invalidates the whole filter, so the shadow vanishes rather than degrading."),
+	shadows: desc(z.optional(z.record(z.string(), Shadow)), "Named shadows → `--shadow-<name>` tokens and `.drop-shadow-<name>` utilities. A value is either a string (below) or `{ \"box\"?: string, \"drop\"?: string }` for a shadow that needs the two grammars to differ: `box` is what `--shadow-<name>` holds and what `box-shadow` consumers (pattern geometry, `--ds-*`) read, so it MAY use spread, `inset` and several layers; `drop` is emitted as `--shadow-<name>-drop` and is what `.drop-shadow-<name>` and the `shadow:` state shortcut read, so it must obey the drop-shadow() limits. Omit `drop` and no drop-shadow utility is emitted for that name; omit `box` and `--shadow-<name>` takes the `drop` value. The plain string form keeps working and feeds both consumers from one value. For that string form: each token feeds two consumers with different grammars — `box-shadow` (pattern geometry, via the `--ds-*` group aliases) and `filter: drop-shadow(…)` (the utilities and the `shadow:` state shortcut) — so values must stay in the intersection: **one layer, no spread radius, no `inset`**. `drop-shadow()` rejects all three, and rejecting them invalidates the whole filter, so the shadow vanishes rather than degrading."),
 	fonts: desc(z.optional(z.record(z.string(), z.string())), "Raw font stacks by name, emitted as `--font-<name>` tokens (referenced by `typography.families`). **Stacks only — vitops does not load webfonts.** A value here is a `font-family` list and nothing more: it emits no `@font-face`, no preload, and no metrics-matched fallback. If a family needs loading, declare it in Astro's `fonts:` config (`astro.config`, or the site config's `fonts` array) and point the token at the family's `cssVariable` — `\"display\": \"var(--font-league-spartan), sans-serif\"`. Installing a `@fontsource*` package and importing its CSS also works but gives up subsetting, preload and `size-adjust`/`ascent-override` fallbacks, so it regresses CLS."),
-	typeScale: desc(z.optional(Scale), "Fluid modular TYPE scale → `--text-<name>` tokens, consumed by typography roles and text-size utilities."),
+	typeScale: desc(z.optional(Scale), "Fluid modular TYPE scale → `--text-<name>` tokens, consumed by typography roles and text-size utilities.\n\n**Recipe for marketing headings:** one ratio cannot serve both a ~16px body and a ~76px hero — a ratio big enough for the hero collapses the small end to unreadable. Extend `names` upward instead of raising the ratio: keep `base` ≈ \"1rem\" at the body step, `ratio` ≈ 1.2 at `maxVw` (≈ 1.125–1.15 `minRatio` at `minVw` so headings tame on phones), and add names (`4xl`, `5xl`) for the display sizes — the steps above `baseStep` are what headings read, the steps below it only need `xs`/`sm`. Aim the largest named step at your hero (≈ 4.5–5rem at `maxVw`), then point the `display`/`title` roles at those steps rather than hand-writing `clamp()` in a role. If a step still needs its own value, set that role's `size` literally — roles may bypass the scale."),
+	layout: z.optional(Layout),
 	spaceScale: desc(z.optional(Scale), "Fluid modular SPACE scale → `--space-<name>` tokens, consumed by spacing/gap utilities and vertical rhythm."),
 	patterns: z.optional(Patterns),
 	typography: z.optional(Typography),
@@ -473,7 +499,8 @@ const dropShadowIssue = (value) => {
 const RAMP_KEYS = /* @__PURE__ */ new Set([
 	"seed",
 	"anchors",
-	"tones"
+	"tones",
+	"acknowledgeOffLadder"
 ]);
 /**
 * Replace the bare "Invalid input" a failed union produces with the reason.
@@ -536,13 +563,44 @@ function validate(input) {
 			warnings: []
 		};
 	}
+	for (const [role, spec] of Object.entries(roles)) {
+		if (typeof spec === "string" || spec.solid == null) continue;
+		const step = String(spec.solid);
+		if (!NUMERIC_STEPS.includes(step) || step === "50" || step === "950") return {
+			ok: false,
+			data: void 0,
+			errors: [{
+				code: "custom",
+				path: [
+					"colors",
+					"roles",
+					role,
+					"solid"
+				],
+				message: `solid step "${step}" is not one of 100, 200, … 900`
+			}],
+			warnings: []
+		};
+	}
 	const warnings = [];
 	const missing = REQUIRED_ROLES.filter((r) => roles[r] == null);
 	if (missing.length) warnings.push(`colors.roles is missing ${missing.map((r) => `"${r}"`).join(", ")} — the framework's own component CSS references ${missing.length === 1 ? "it" : "them"} with no fallback, so those components will render uncoloured. Add any role you like, but keep these defined.`);
 	const radii = Object.keys(result.data.patterns?.radii ?? {});
 	const items = new Set(Object.keys(result.data.patterns?.items ?? {}));
 	for (const name of radii) if (items.has(name)) warnings.push(`patterns.radii.${name} collides with the "${name}" pattern on --br-${name}; the pattern's override hook wins — rename the radius`);
-	for (const [name, value] of Object.entries(result.data.shadows ?? {})) {
+	for (const [name, spec] of Object.entries(result.data.shadows ?? {})) {
+		if (typeof spec !== "string" && spec.box == null && spec.drop == null) return {
+			ok: false,
+			data: void 0,
+			errors: [{
+				code: "custom",
+				path: ["shadows", name],
+				message: "a split shadow needs at least one of `box` and `drop`"
+			}],
+			warnings: []
+		};
+		const value = typeof spec === "string" ? spec : spec.drop;
+		if (value == null) continue;
 		const issue = dropShadowIssue(value);
 		if (issue) warnings.push(`shadows.${name} carries ${issue}, which \`filter: drop-shadow()\` rejects — \`.drop-shadow-${name}\` will render no shadow at all (the token still works as a \`box-shadow\`). Use one layer of at most three lengths.`);
 	}
@@ -652,7 +710,7 @@ const DesignSystemBlock = desc(z.strictObject({
 		"light",
 		"dark",
 		"system"
-	])), "Initial appearance. `\"system\"` follows the OS via `prefers-color-scheme` and is what makes `<wc-color-scheme-toggle>`'s \"System\" position resolve to anything — it removes the theme attribute, so without this the page falls through to light. It also gives a no-JS page the OS appearance. Defaults to `\"light\"`, because switching an existing site to `\"system\"` visibly flips it dark for dark-OS visitors.")
+	])), "Initial appearance. `\"dark\"` makes the site DARK-ONLY: the dark tokens become the `:root` appearance (with `color-scheme: dark`), no light block or `data-theme` flip is emitted, and the light-mode contrast checks are skipped — so a palette that only works dark (bright fills with dark text, for example) builds. Do not ship `<wc-color-scheme-toggle>` on such a site. `\"system\"` follows the OS via `prefers-color-scheme` and is what makes `<wc-color-scheme-toggle>`'s \"System\" position resolve to anything — it removes the theme attribute, so without this the page falls through to light. It also gives a no-JS page the OS appearance. Defaults to `\"light\"`, because switching an existing site to `\"system\"` visibly flips it dark for dark-OS visitors.")
 }), "The design system: named themes plus the system-wide facts (which theme, which appearance). A bare design system, or a bare theme map, is accepted as shorthand for `{ themes: … }`.");
 const LocaleSchema = z.strictObject({
 	name: desc(z.string(), "Display name of the locale (e.g. \"English\")."),
@@ -672,7 +730,7 @@ const DomainAliasSchema = z.strictObject({
 	environment: z.optional(z.string())
 });
 const PostalAddressSchema = desc(z.strictObject({
-	streetAddress: z.string(),
+	streetAddress: desc(z.optional(z.string()), "Street line. Optional: a business with no public street address (home-based, service-area) omits it, and the generated legal documents and JSON-LD simply leave the line out."),
 	addressLocality: desc(z.string(), "City."),
 	addressRegion: desc(z.optional(z.string()), "State / province."),
 	postalCode: z.optional(z.string()),
@@ -755,6 +813,7 @@ const OrganizationSchema = z.strictObject({
 	email: desc(z.optional(z.email()), "General contact address. Also the last fallback for privacy requests — see `contact`."),
 	phone: desc(z.optional(z.string()), "General contact telephone number."),
 	address: desc(z.optional(PostalAddressSchema), "Registered/mailing address. Its `addressRegion` and `addressCountry` are what the governing-law clause of the generated terms of service defaults to."),
+	description: desc(z.optional(LocalizableSchema), "One or two sentences on what the organization does → JSON-LD `description` and a fallback for SEO. Localisable."),
 	taxID: desc(z.optional(z.string()), "Tax identification number."),
 	vatID: desc(z.optional(z.string()), "VAT identification number."),
 	sameAs: desc(z.optional(z.array(z.url())), "Profile URLs → JSON-LD `sameAs` (mirrors `links`).")
@@ -990,7 +1049,7 @@ const PlanSchema = z.strictObject({
 * anything without a registered template. Add a member here and a matching entry
 * in `legal/templates/index.ts` — the two are checked against each other.
 */
-const JURISDICTIONS = ["ca"];
+const JURISDICTIONS = ["ca", "qc"];
 const JurisdictionSchema = z.enum(JURISDICTIONS);
 /**
 * The country each template set frames cross-border transfers as *leaving*.
@@ -1005,7 +1064,10 @@ const JurisdictionSchema = z.enum(JURISDICTIONS);
 * `governingCountry`.) `satisfies` makes a new jurisdiction unable to forget it,
 * the same guard style as `TEMPLATES`.
 */
-const JURISDICTION_COUNTRIES = { ca: "Canada" };
+const JURISDICTION_COUNTRIES = {
+	ca: "Canada",
+	qc: "Quebec"
+};
 /**
 * A third party that receives personal information. The generator derives the
 * ones it can see (analytics IDs, Turnstile, the deploy platform); this is for
@@ -1083,6 +1145,8 @@ const SiteSectionSchema = z.strictObject({
 			url: z.optional(z.url()),
 			lastUpdated: z.optional(IsoDate),
 			privacyOfficer: desc(z.optional(ContactConfigSchema), "Who privacy requests go to. Falls back to `contact`, then `primaryLocation`."),
+			privacyOfficerTitle: desc(z.optional(z.string()), "Title of the person in charge of the protection of personal information (e.g. \"President\"). Quebec Law 25 requires the title and contact details to be published; the `qc` templates print it beside the `privacyOfficer` contact. Not asserted when absent."),
+			impactAssessments: desc(z.optional(z.boolean()), "Attests that a privacy impact assessment is carried out before personal information is communicated outside Quebec (Law 25, s. 17). The `qc` privacy policy states that assurance only when this is `true` — a fact the config cannot otherwise know, so it is never assumed."),
 			retention: desc(z.optional(z.string()), "How long personal information is kept, in prose (e.g. \"24 months after last contact\")."),
 			processors: desc(z.optional(z.array(ProcessorSchema)), "Third parties that receive personal information and cannot be inferred from the rest of the config (payment processors, CRMs, mail senders). Known providers implied by `analytics`, `security` and `deployment` are added automatically — list only the rest.")
 		})),
@@ -1740,4 +1804,4 @@ function formatConfig(value, col = 0, indent = 0) {
 }
 
 export { jsonSchema as A, resolveTheme as C, DesignSystemSchema as D, validateConfig as E, movedTokens as M, SCHEMA_LOCAL_PATH as O, resolvePrivacyContact as S, stripNulls as T, getAt as _, CONFIG_VERSION as a, resolveConfig as b, JURISDICTIONS as c, SiteFontSchema as d, configJsonSchema as f, formatConfig as g, experimentDimensionWarnings as h, CONFIG_SCHEMA_URL as i, validate as j, SCHEMA_URL as k, JURISDICTION_COUNTRIES as l, designSystemPath as m, BIGIN_DATA_CENTERS as n, CRM_PROVIDERS as o, deepMerge as p, CONFIG_SCHEMA_LOCAL_PATH as r, ConfigSchema as s, AD_PROVIDERS as t, PLAN_CAPABILITIES as u, isConfig as v, setAt as w, resolveInput as x, mergePatch as y };
-//# sourceMappingURL=config-BfcWKH-5.mjs.map
+//# sourceMappingURL=config-D5xuz8--.mjs.map