@cube-dev/ui-kit 0.163.0 → 0.164.0

package/dist/tokens/palette-config.js

@@ -1,4 +1,5 @@
-/** @license MIT | @cube-dev/ui-kit v0.163.0 | Cube Dev Team */
+/** @license MIT | @cube-dev/ui-kit v0.164.0 | Cube Dev Team */
+import { colorSeed } from "./color-seed.js";
 import { useSyncExternalStore } from "react";
 
 //#region src/tokens/palette-config.ts
@@ -6,9 +7,10 @@ import { useSyncExternalStore } from "react";
 * Runtime configuration for the Glaze-generated color palette.
 *
 * The palette recipe itself lives in `./palette.ts`; this module owns only the
-* *seeds* it is built from, plus a version counter the token caches watch. It
-* deliberately imports nothing else — not the token modules, not `glaze` — so
-* there is no import cycle and no ordering hazard.
+* *seeds* it is built from, plus a version counter the token caches watch. Its only
+* import is the leaf `./color-seed` helper — never the token modules — so there is
+* no import cycle and no ordering hazard. See that file for why reading a colour
+* cannot depend on the global Glaze config `./palette.ts` installs.
 *
 * Reading is free; writing rebuilds the palette on the next token read. See
 * `Getting Started/Theming` in Storybook for the full contract.
@@ -22,6 +24,31 @@ const DEFAULT_NOTE_HUE = 302.3;
 /** Seed saturation. Per-color `saturation` in the recipe is a 0–1 factor of it. */
 const DEFAULT_SATURATION = 100;
 /**
+* Share of {@link DEFAULT_SATURATION} the neutral `surface` carries — the recipe's
+* own `SURFACE_SATURATION` factor, as a fraction.
+*
+* It lives here rather than in the recipe because the dependency runs one way:
+* `./palette.ts` imports the config, not the reverse — and the config needs this
+* number to default `baseSaturation`. It is the anchor of the base zone's own 0–100
+* scale: the share the *accent zone* lends the chrome when no `baseColor` names one
+* outright, so an untouched palette lands on `12`.
+*/
+const SURFACE_SATURATION_SHARE = .12;
+/**
+* Ceiling on a base saturation derived from a {@link PaletteConfig.base} color.
+*
+* A named base color lands the chrome near itself rather than at the 12% share the
+* accent lends it, which is the whole reason to name one — but a fully saturated
+* chrome stops being chrome. `50` is well past where the base colors begin to
+* converge (`surface-inverse` tops out around `25`), so the clip costs nothing that
+* was still moving and stops a vivid brand hex from being read as an instruction to
+* paint the page with it.
+*
+* The manual slider in the tuner shares the number, so the two agree on what the top
+* of the range means.
+*/
+const MAX_BASE_SATURATION = 50;
+/**
 * Seed saturation for the `code-*` syntax family, deliberately **not** the same
 * constant as {@link DEFAULT_SATURATION}.
 *
@@ -39,38 +66,111 @@ const DEFAULT_THEME_HUES = {
 	warning: DEFAULT_WARNING_HUE,
 	note: DEFAULT_NOTE_HUE
 };
+/**
+* Warned once per process, not once per call.
+*
+* `resolveConfig` runs on every write AND on every `resolvePaletteConfig` preview, so an
+* unguarded warning would fire on every frame of a slider drag.
+*/
+let warnedAboutPastelSaturation = false;
+/**
+* One zone's seed, normalized to the four things a resolver can ask for.
+*
+* The single place a {@link PaletteSeed} is taken apart, so the six zones cannot drift
+* in how they read one. A string that {@link colorSeed} cannot parse comes back as the
+* numeric path with nothing pinned, which is exactly the fallback the docs promise: the
+* zone keeps its defaults rather than the render going down over a typo.
+*/
+function seedOf(seed) {
+	if (typeof seed === "string") {
+		const parsed = colorSeed(seed);
+		return parsed ? {
+			color: seed,
+			hue: parsed.hue,
+			saturation: parsed.saturation,
+			tone: parsed.tone
+		} : {
+			color: null,
+			hue: void 0,
+			saturation: void 0,
+			tone: null
+		};
+	}
+	return {
+		color: null,
+		hue: seed?.hue,
+		saturation: seed?.saturation,
+		tone: null
+	};
+}
+/**
+* Whether a zone pinned a saturation *as a number*.
+*
+* A color's chroma is not a pinned saturation — it reaches the palette through `from`,
+* not through the seed — so it must not answer the question `pastel` asks below.
+*/
+function pinnedSaturation(seed) {
+	return typeof seed === "string" ? void 0 : seed?.saturation;
+}
 function resolveConfig(input) {
-	const saturation = input.saturation ?? DEFAULT_SATURATION;
 	const themes = input.themes ?? {};
-	const hue = input.hue ?? DEFAULT_HUE;
+	const accent = seedOf(input.accent);
+	const base = seedOf(input.base);
+	const accentSaturationPin = pinnedSaturation(input.accent);
+	const pastel = input.pastel ?? accentSaturationPin === void 0;
+	const hue = accent.hue ?? DEFAULT_HUE;
+	const baseHue = base.hue ?? hue;
+	if (input.pastel === true && accentSaturationPin !== void 0 && accentSaturationPin !== DEFAULT_SATURATION && !warnedAboutPastelSaturation) {
+		warnedAboutPastelSaturation = true;
+		console.warn(`[cube-ui-kit] palette \`accent.saturation\` (${accentSaturationPin}) is ignored because \`pastel\` is on — pastel pins it to ${DEFAULT_SATURATION}. Drop \`pastel\`, or set it to \`false\`, to tune saturation yourself.`);
+	}
+	const saturation = pastel ? DEFAULT_SATURATION : accentSaturationPin ?? DEFAULT_SATURATION;
 	return {
 		hue,
-		baseHue: input.baseHue ?? hue,
+		baseHue,
 		saturation,
-		pastel: input.pastel ?? true,
+		baseSaturation: pinnedSaturation(input.base) ?? (base.color ? Math.min(base.saturation, MAX_BASE_SATURATION, saturation) : Math.min(accent.saturation ?? saturation, saturation) * SURFACE_SATURATION_SHARE),
+		surfaceMode: input.surfaceMode ?? "neutral",
+		accentColor: accent.color,
+		baseColor: base.color,
+		accentTone: accent.tone,
+		accentSaturation: accent.color === null ? null : accent.saturation,
+		pastel,
 		contrastLevel: input.contrastLevel ?? "auto",
 		themes: {
-			success: {
-				hue: themes.success?.hue ?? DEFAULT_THEME_HUES.success,
-				saturation: themes.success?.saturation ?? saturation
-			},
-			danger: {
-				hue: themes.danger?.hue ?? DEFAULT_THEME_HUES.danger,
-				saturation: themes.danger?.saturation ?? saturation
-			},
-			warning: {
-				hue: themes.warning?.hue ?? DEFAULT_THEME_HUES.warning,
-				saturation: themes.warning?.saturation ?? saturation
-			},
-			note: {
-				hue: themes.note?.hue ?? DEFAULT_THEME_HUES.note,
-				saturation: themes.note?.saturation ?? saturation
-			},
+			success: resolveThemeSeed("success", themes.success, saturation),
+			danger: resolveThemeSeed("danger", themes.danger, saturation),
+			warning: resolveThemeSeed("warning", themes.warning, saturation),
+			note: resolveThemeSeed("note", themes.note, saturation),
 			code: { saturation: themes.code?.saturation ?? DEFAULT_CODE_SATURATION }
 		}
 	};
 }
 /**
+* One status theme's seed, on whichever path it is on.
+*
+* The color arm takes all three of the color's components — hue, chroma and tone — where
+* the accent zone deliberately leaves the chroma out of its seed. The asymmetry is the
+* point: this seed is inherited by nothing, so raising it re-chromatizes nothing, and
+* raising it is what holds the theme's tinted surface, border and text ramp in the same
+* proportion to the fill that the shipped derivation gives them.
+*/
+function resolveThemeSeed(name, seed, saturation) {
+	const parsed = seedOf(seed);
+	if (parsed.color !== null) return {
+		hue: parsed.hue,
+		saturation: parsed.saturation,
+		color: parsed.color,
+		colorTone: parsed.tone
+	};
+	return {
+		hue: parsed.hue ?? DEFAULT_THEME_HUES[name],
+		saturation: parsed.saturation ?? saturation,
+		color: null,
+		colorTone: null
+	};
+}
+/**
 * The palette as it ships, with no tuning applied. Frozen — it is the baseline
 * every resolution falls back to, so a stray write to it would move the defaults
 * for the whole process.
@@ -87,6 +187,16 @@ let resolved = DEFAULT_PALETTE_CONFIG;
 let version = 0;
 const listeners = /* @__PURE__ */ new Set();
 function mergeSeed(base, patch) {
+	if (patch === void 0) return base;
+	if (base === void 0) return patch;
+	if (typeof base === "string" || typeof patch === "string") return patch;
+	return {
+		...base,
+		...patch
+	};
+}
+/** {@link mergeSeed} for the code seed, which is not a {@link PaletteSeed}. */
+function mergeCodeSeed(base, patch) {
 	if (!base) return patch;
 	if (!patch) return base;
 	return {
@@ -101,40 +211,62 @@ function mergeSeed(base, patch) {
 function mergeInput(base, patch) {
 	const next = {
 		...base,
-		...patch
+		...patch,
+		...base.accent !== void 0 || patch.accent !== void 0 ? { accent: mergeSeed(base.accent, patch.accent) } : null,
+		...base.base !== void 0 || patch.base !== void 0 ? { base: mergeSeed(base.base, patch.base) } : null
 	};
 	if (base.themes || patch.themes) next.themes = {
 		success: mergeSeed(base.themes?.success, patch.themes?.success),
 		danger: mergeSeed(base.themes?.danger, patch.themes?.danger),
 		warning: mergeSeed(base.themes?.warning, patch.themes?.warning),
 		note: mergeSeed(base.themes?.note, patch.themes?.note),
-		code: mergeSeed(base.themes?.code, patch.themes?.code)
+		code: mergeCodeSeed(base.themes?.code, patch.themes?.code)
 	};
 	return next;
 }
 function isSameConfig(a, b) {
-	return a.hue === b.hue && a.baseHue === b.baseHue && a.saturation === b.saturation && a.pastel === b.pastel && a.contrastLevel === b.contrastLevel && a.themes.code.saturation === b.themes.code.saturation && [
+	return a.hue === b.hue && a.baseHue === b.baseHue && a.saturation === b.saturation && a.baseSaturation === b.baseSaturation && a.surfaceMode === b.surfaceMode && a.accentColor === b.accentColor && a.baseColor === b.baseColor && a.pastel === b.pastel && a.contrastLevel === b.contrastLevel && a.themes.code.saturation === b.themes.code.saturation && [
 		"success",
 		"danger",
 		"warning",
 		"note"
-	].every((name) => a.themes[name].hue === b.themes[name].hue && a.themes[name].saturation === b.themes[name].saturation);
+	].every((name) => a.themes[name].hue === b.themes[name].hue && a.themes[name].saturation === b.themes[name].saturation && a.themes[name].color === b.themes[name].color);
 }
 /**
 * Which fields are *explicitly set*, as an order-independent signature.
 *
 * Two configs can resolve to identical values yet differ in which of those values
-* are pinned rather than inherited — pinning `primary.saturation` to the number it
-* already inherited is the obvious case. That difference is invisible to
+* are pinned rather than inherited — pinning a status theme's saturation to the number
+* it already inherited is the obvious case. That difference is invisible to
 * {@link isSameConfig} but visible through {@link getPaletteConfigInput}, so it has
 * to count as a change or a settings UI reading it would never re-render.
 */
 function pinSignature(config) {
 	const set = (value) => value === void 0 ? "0" : "1";
+	/**
+	* One zone, in three states — absent, numbers, or a color.
+	*
+	* **Absent is its own state**, not "numbers with nothing pinned". `base: {}` and no
+	* `base` at all resolve identically, but they read back differently, and a settings UI
+	* asks exactly that question to decide whether the chrome has a seed of its own or is
+	* still following the accent.
+	*
+	* A color carries its **value**, not just its presence. Presence alone cannot tell one
+	* unparseable string from another: both resolve to `null`, so `isSameConfig` sees no
+	* movement either, and replacing `'bad-one'` with `'bad-two'` returned early — leaving
+	* the field on the first string with no notification that the write was dropped.
+	*
+	* It also means two spellings of the same color (`'#ff0000'` / `'rgb(255 0 0)'`) bump
+	* the version. That is the same argument the presence check was already making: what a
+	* settings UI reads back changed, so it has to re-render. And a zone switching from
+	* `{ hue: 45 }` to a color that happens to derive hue 45 resolves to the same numbers,
+	* so without this the version would never bump and the control would look stuck.
+	*/
+	const seed = (value) => value === void 0 ? "-" : typeof value === "string" ? JSON.stringify(value) : `${set(value.hue)}${set(value.saturation)}`;
 	return [
-		set(config.hue),
-		set(config.baseHue),
-		set(config.saturation),
+		seed(config.accent),
+		seed(config.base),
+		set(config.surfaceMode),
 		set(config.pastel),
 		set(config.contrastLevel),
 		set(config.themes?.code?.saturation),
@@ -143,8 +275,8 @@ function pinSignature(config) {
 			"danger",
 			"warning",
 			"note"
-		].flatMap((name) => [set(config.themes?.[name]?.hue), set(config.themes?.[name]?.saturation)])
-	].join("");
+		].map((name) => seed(config.themes?.[name]))
+	].join("|");
 }
 /**
 * Snapshot a config so the store owns it outright.
@@ -159,21 +291,27 @@ function pinSignature(config) {
 function freezeConfig(config) {
 	const themes = config.themes;
 	if (themes) {
-		for (const seed of Object.values(themes)) if (seed) Object.freeze(seed);
+		for (const seed of Object.values(themes)) if (seed && typeof seed === "object") Object.freeze(seed);
 		Object.freeze(themes);
 	}
+	const zones = config;
+	if (typeof zones.accent === "object") Object.freeze(zones.accent);
+	if (typeof zones.base === "object") Object.freeze(zones.base);
 	return Object.freeze(config);
 }
 /** {@link freezeConfig} on a copy, for a config we did not create ourselves. */
 function snapshotConfig(config) {
 	const themes = config.themes;
+	const copy = (seed) => typeof seed === "object" ? { ...seed } : seed;
 	return freezeConfig({
 		...config,
+		...config.accent !== void 0 ? { accent: copy(config.accent) } : null,
+		...config.base !== void 0 ? { base: copy(config.base) } : null,
 		...themes ? { themes: {
-			...themes.success ? { success: { ...themes.success } } : null,
-			...themes.danger ? { danger: { ...themes.danger } } : null,
-			...themes.warning ? { warning: { ...themes.warning } } : null,
-			...themes.note ? { note: { ...themes.note } } : null,
+			...themes.success !== void 0 ? { success: copy(themes.success) } : null,
+			...themes.danger !== void 0 ? { danger: copy(themes.danger) } : null,
+			...themes.warning !== void 0 ? { warning: copy(themes.warning) } : null,
+			...themes.note !== void 0 ? { note: copy(themes.note) } : null,
 			...themes.code ? { code: { ...themes.code } } : null
 		} } : null
 	});
@@ -195,8 +333,8 @@ function commit(nextInput) {
 * object, and re-applying the same object twice is the same as applying it once.
 *
 * ```ts
-* setPaletteConfig({ hue: 200, baseHue: 60 });
-* setPaletteConfig({ hue: 200 }); // baseHue is gone — back to inheriting `hue`
+* setPaletteConfig({ accent: { hue: 200 }, base: { hue: 60 } });
+* setPaletteConfig({ accent: { hue: 200 } }); // `base` is gone — follows accent again
 * ```
 *
 * To adjust one field of the config already in place — a slider in a settings UI —
@@ -204,7 +342,7 @@ function commit(nextInput) {
 * preserves which fields are pinned and which still inherit:
 *
 * ```ts
-* setPaletteConfig((config) => ({ ...config, hue: 200 }));
+* setPaletteConfig((config) => ({ ...config, accent: { hue: 200 } }));
 * ```
 *
 * The palette is rebuilt lazily on the next token read, and any mounted `<Root>`
@@ -246,10 +384,10 @@ function getPaletteConfig() {
 * to offer a way back:
 *
 * ```ts
-* const pinned = getPaletteConfigInput().baseHue !== undefined;
+* const own = getPaletteConfigInput().base !== undefined;
 *
 * // Re-link it to the brand by dropping the field.
-* setPaletteConfig(({ baseHue, ...config }) => config);
+* setPaletteConfig(({ base, ...config }) => config);
 * ```
 *
 * It is also the value handed to a {@link setPaletteConfig} updater.
@@ -301,12 +439,13 @@ function usePaletteVersion() {
 *
 * <HueSlider
 *   value={palette.hue}
-*   onChange={(hue) => setPalette((config) => ({ ...config, hue }))}
+*   onChange={(hue) => setPalette((config) => ({ ...config, accent: { hue } }))}
 * />
 * ```
 *
-* The first element is the *resolved* config, so `palette.hue` is always a number.
-* The updater's argument is the sparse one — see {@link getPaletteConfigInput}.
+* The first element is the *resolved* config, so `palette.hue` is always a number — it
+* keeps the flat shape the recipe reads, whichever way the zones were seeded. The
+* updater's argument is the sparse one — see {@link getPaletteConfigInput}.
 *
 * The config is global process state, so every consumer of this hook — and every
 * mounted `<Root>` — sees the same palette.
@@ -317,5 +456,5 @@ function usePaletteConfig() {
 }
 
 //#endregion
-export { DEFAULT_PALETTE_CONFIG, DEFAULT_SATURATION, getPaletteConfig, getPaletteConfigInput, getPaletteVersion, invalidatePaletteTokens, resetPaletteConfig, resolvePaletteConfig, setPaletteConfig, subscribePaletteConfig, usePaletteConfig, usePaletteVersion };
+export { DEFAULT_HUE, DEFAULT_PALETTE_CONFIG, DEFAULT_SATURATION, MAX_BASE_SATURATION, SURFACE_SATURATION_SHARE, getPaletteConfig, getPaletteConfigInput, getPaletteVersion, invalidatePaletteTokens, resetPaletteConfig, resolvePaletteConfig, setPaletteConfig, subscribePaletteConfig, usePaletteConfig, usePaletteVersion };
 //# sourceMappingURL=palette-config.js.map

package/dist/tokens/palette-config.js.map

@@ -1 +1 @@
-{"version":3,"file":"palette-config.js","names":[],"sources":["../../src/tokens/palette-config.ts"],"sourcesContent":["import { useSyncExternalStore } from 'react';\n\n/**\n * Runtime configuration for the Glaze-generated color palette.\n *\n * The palette recipe itself lives in `./palette.ts`; this module owns only the\n * *seeds* it is built from, plus a version counter the token caches watch. It\n * deliberately imports nothing else — not the token modules, not `glaze` — so\n * there is no import cycle and no ordering hazard.\n *\n * Reading is free; writing rebuilds the palette on the next token read. See\n * `Getting Started/Theming` in Storybook for the full contract.\n */\n\n// ============================================================================\n// Default seeds\n// ============================================================================\n\n/** Brand hue. Drives the `default`, `primary`, `purple` and `special` themes. */\nexport const DEFAULT_HUE = 280.3;\nexport const DEFAULT_SUCCESS_HUE = 156.9;\nexport const DEFAULT_DANGER_HUE = 23.1;\nexport const DEFAULT_WARNING_HUE = 84.3;\nexport const DEFAULT_NOTE_HUE = 302.3;\n\n/** Seed saturation. Per-color `saturation` in the recipe is a 0–1 factor of it. */\nexport const DEFAULT_SATURATION = 100;\n\n/**\n * Seed saturation for the `code-*` syntax family, deliberately **not** the same\n * constant as {@link DEFAULT_SATURATION}.\n *\n * The two were one value until the app seed moved to 100 for the pastel palette.\n * Sharing it would have dragged the syntax colors along for the ride — the exact\n * coupling that `PaletteCodeSeed` and the `pastel` opt-out both exist to prevent,\n * and the reason the code family answers to its own saturation and nothing else.\n * Splitting the constant is what lets the app seed move while the code palette\n * stays on the value it was calibrated against.\n */\nexport const DEFAULT_CODE_SATURATION = 80;\n\n// ============================================================================\n// Types\n// ============================================================================\n\n/** Hue / saturation seed override for one colored theme. */\nexport interface PaletteThemeSeed {\n  /** Hue in degrees (0–360). */\n  hue?: number;\n  /** Saturation (0–100). Defaults to the palette-level `saturation`. */\n  saturation?: number;\n}\n\n/**\n * The `code-*` syntax family takes a saturation and nothing else — and answers to\n * nothing else either. This is the one knob that moves it.\n *\n * Its hues are absolute literals by design, so syntax colors never rotate with the\n * brand — strings would collide with numbers the moment the brand went green. Unlike\n * every other theme, its saturation does **not** inherit the palette-level one: the\n * code palette is calibrated once and stays there, so re-seeding the app cannot\n * quietly wash out a code block. {@link PaletteConfig.pastel} skips it for the same\n * reason.\n */\nexport interface PaletteCodeSeed {\n  /** Saturation (0–100). Defaults to {@link DEFAULT_CODE_SATURATION}, not to `saturation`. */\n  saturation?: number;\n}\n\n/** Names of the themes whose seeds can be overridden individually. */\nexport type PaletteThemeName =\n  | 'success'\n  | 'danger'\n  | 'warning'\n  | 'note'\n  | 'code';\n\n/**\n * Palette tuning. Every field is optional; omitted fields keep their default,\n * and per-theme fields left unset inherit the palette-level value.\n */\nexport interface PaletteConfig {\n  /**\n   * Accent hue in degrees (0–360) — the brand.\n   *\n   * Drives the `accent-*` family on every theme, `primary` / `purple` / `special`,\n   * and the brand-tinted odds and ends (`focus`, the loading faces, the disabled\n   * chip). Also the default for {@link PaletteConfig.baseHue}.\n   */\n  hue?: number;\n  /**\n   * Hue of the **base** zone in degrees (0–360): the neutral chrome — `surface`\n   * and its ladder, the `surface-text*` ramp, `border`, `placeholder`. Defaults to\n   * `hue`, so the chrome carries a faint tint of the brand unless you say otherwise.\n   *\n   * Splitting it lets the chrome sit on a different hue from the accent — a warm\n   * grey UI with a cool blue brand, say. Only the `default` theme is affected: a\n   * colored theme's tinted `surface` deliberately follows *its own* hue, because a\n   * danger banner should read as red.\n   */\n  baseHue?: number;\n  /**\n   * Seed saturation (0–100), and the fallback for every theme that does not set\n   * its own.\n   *\n   * One scale for the whole theme, by design. Every color's own `saturation` is a\n   * 0–1 factor of this seed — `surface` at 0.12, `border` at 0.175, the text ramp\n   * at 0.2, the accent family at ~1.0 — so moving it rescales the palette while\n   * keeping those proportions. Unlike hue, which is configured separately for the\n   * brand and for each status theme, saturation is deliberately not split: the\n   * ratio between a subtle surface tint and a saturated accent is part of the\n   * design.\n   */\n  saturation?: number;\n  /**\n   * Global. Widens the usable chroma range by relaxing the sRGB-safe limit,\n   * producing a softer, more even palette across hues. Glaze treats `pastel` as\n   * instance-level, so it is threaded into every theme.\n   *\n   * Every theme except `code`. The syntax family is calibrated on its own\n   * saturation and is deliberately left out — softening it collapses the chroma\n   * spread the syntax hues rely on to stay apart. To soften a code block, lower\n   * {@link PaletteCodeSeed.saturation} instead.\n   */\n  pastel?: boolean;\n  /**\n   * Global. `'auto'` (the default) keeps the two-tier model: normal colors plus\n   * a separate high-contrast tier driven by `<html data-contrast=\"high\">` /\n   * `prefers-contrast: more`.\n   *\n   * A number (0–100) replaces that switch with a slider — and, because a manual\n   * level already carries the contrast preference, **drops the high-contrast\n   * tier entirely**. `0` reproduces the normal output and `100` the\n   * high-contrast output, bit for bit.\n   */\n  contrastLevel?: number | 'auto';\n  /** Per-theme seed overrides. */\n  themes?: {\n    success?: PaletteThemeSeed;\n    danger?: PaletteThemeSeed;\n    warning?: PaletteThemeSeed;\n    note?: PaletteThemeSeed;\n    code?: PaletteCodeSeed;\n  };\n}\n\n/** {@link PaletteConfig} with every field resolved to a concrete value. */\nexport interface ResolvedPaletteConfig {\n  hue: number;\n  baseHue: number;\n  saturation: number;\n  pastel: boolean;\n  contrastLevel: number | 'auto';\n  themes: {\n    success: { hue: number; saturation: number };\n    danger: { hue: number; saturation: number };\n    warning: { hue: number; saturation: number };\n    note: { hue: number; saturation: number };\n    code: { saturation: number };\n  };\n}\n\n// ============================================================================\n// Resolution\n// ============================================================================\n\nconst DEFAULT_THEME_HUES = {\n  success: DEFAULT_SUCCESS_HUE,\n  danger: DEFAULT_DANGER_HUE,\n  warning: DEFAULT_WARNING_HUE,\n  note: DEFAULT_NOTE_HUE,\n} as const;\n\nfunction resolveConfig(input: PaletteConfig): ResolvedPaletteConfig {\n  const saturation = input.saturation ?? DEFAULT_SATURATION;\n  const themes = input.themes ?? {};\n\n  const hue = input.hue ?? DEFAULT_HUE;\n\n  return {\n    hue,\n    baseHue: input.baseHue ?? hue,\n    saturation,\n    pastel: input.pastel ?? true,\n    contrastLevel: input.contrastLevel ?? 'auto',\n    themes: {\n      success: {\n        hue: themes.success?.hue ?? DEFAULT_THEME_HUES.success,\n        saturation: themes.success?.saturation ?? saturation,\n      },\n      danger: {\n        hue: themes.danger?.hue ?? DEFAULT_THEME_HUES.danger,\n        saturation: themes.danger?.saturation ?? saturation,\n      },\n      warning: {\n        hue: themes.warning?.hue ?? DEFAULT_THEME_HUES.warning,\n        saturation: themes.warning?.saturation ?? saturation,\n      },\n      note: {\n        hue: themes.note?.hue ?? DEFAULT_THEME_HUES.note,\n        saturation: themes.note?.saturation ?? saturation,\n      },\n      // Deliberately NOT `?? saturation`: the code palette is calibrated once and\n      // does not follow the palette-level seed. See `PaletteCodeSeed`.\n      code: { saturation: themes.code?.saturation ?? DEFAULT_CODE_SATURATION },\n    },\n  };\n}\n\n/**\n * The palette as it ships, with no tuning applied. Frozen — it is the baseline\n * every resolution falls back to, so a stray write to it would move the defaults\n * for the whole process.\n */\nexport const DEFAULT_PALETTE_CONFIG: ResolvedPaletteConfig = freezeConfig(\n  resolveConfig({}),\n);\n\n// ============================================================================\n// Store\n// ============================================================================\n\n/**\n * The last config *as written*, sparse — not the resolved one. Keeping the sparse\n * form is what makes inheritance live: a `saturation` with no `themes.danger.\n * saturation` beside it means danger genuinely follows the palette, rather than\n * having been frozen at whatever the palette read when it was set.\n */\nlet input: PaletteConfig = {};\nlet resolved: ResolvedPaletteConfig = DEFAULT_PALETTE_CONFIG;\nlet version = 0;\n\nconst listeners = new Set<() => void>();\n\nfunction mergeSeed<T extends PaletteThemeSeed | PaletteCodeSeed>(\n  base: T | undefined,\n  patch: T | undefined,\n): T | undefined {\n  if (!base) return patch;\n  // A patch that omits the theme entirely says nothing about it, so the base\n  // survives. Clearing one of its fields is `{ theme: { hue: undefined } }`.\n  if (!patch) return base;\n\n  return { ...base, ...patch };\n}\n\n/**\n * Layer a patch over a base config. Used by {@link resolvePaletteConfig} for\n * previews — *not* by {@link setPaletteConfig}, which replaces.\n */\nfunction mergeInput(base: PaletteConfig, patch: PaletteConfig): PaletteConfig {\n  const next: PaletteConfig = { ...base, ...patch };\n\n  if (base.themes || patch.themes) {\n    next.themes = {\n      success: mergeSeed(base.themes?.success, patch.themes?.success),\n      danger: mergeSeed(base.themes?.danger, patch.themes?.danger),\n      warning: mergeSeed(base.themes?.warning, patch.themes?.warning),\n      note: mergeSeed(base.themes?.note, patch.themes?.note),\n      code: mergeSeed(base.themes?.code, patch.themes?.code),\n    };\n  }\n\n  return next;\n}\n\nfunction isSameConfig(a: ResolvedPaletteConfig, b: ResolvedPaletteConfig) {\n  return (\n    a.hue === b.hue &&\n    a.baseHue === b.baseHue &&\n    a.saturation === b.saturation &&\n    a.pastel === b.pastel &&\n    a.contrastLevel === b.contrastLevel &&\n    a.themes.code.saturation === b.themes.code.saturation &&\n    (['success', 'danger', 'warning', 'note'] as const).every(\n      (name) =>\n        a.themes[name].hue === b.themes[name].hue &&\n        a.themes[name].saturation === b.themes[name].saturation,\n    )\n  );\n}\n\n/**\n * Which fields are *explicitly set*, as an order-independent signature.\n *\n * Two configs can resolve to identical values yet differ in which of those values\n * are pinned rather than inherited — pinning `primary.saturation` to the number it\n * already inherited is the obvious case. That difference is invisible to\n * {@link isSameConfig} but visible through {@link getPaletteConfigInput}, so it has\n * to count as a change or a settings UI reading it would never re-render.\n */\nfunction pinSignature(config: PaletteConfig): string {\n  const set = (value: unknown) => (value === undefined ? '0' : '1');\n\n  return [\n    set(config.hue),\n    set(config.baseHue),\n    set(config.saturation),\n    set(config.pastel),\n    set(config.contrastLevel),\n    set(config.themes?.code?.saturation),\n    ...(['success', 'danger', 'warning', 'note'] as const).flatMap((name) => [\n      set(config.themes?.[name]?.hue),\n      set(config.themes?.[name]?.saturation),\n    ]),\n  ].join('');\n}\n\n/**\n * Snapshot a config so the store owns it outright.\n *\n * Two hazards this closes. The caller's object stays theirs, so mutating it after\n * the call cannot desync `input` from `resolved`. And what we hand back from\n * {@link getPaletteConfig} / {@link getPaletteConfigInput} is frozen, so a caller\n * who writes to it gets a clear failure rather than silently corrupting the store\n * — the version would not bump, and every token cache would go on serving values\n * that no longer match the config.\n */\nfunction freezeConfig<T extends PaletteConfig | ResolvedPaletteConfig>(\n  config: T,\n): T {\n  const themes = config.themes;\n\n  if (themes) {\n    for (const seed of Object.values(themes)) {\n      if (seed) Object.freeze(seed);\n    }\n    Object.freeze(themes);\n  }\n\n  return Object.freeze(config);\n}\n\n/** {@link freezeConfig} on a copy, for a config we did not create ourselves. */\nfunction snapshotConfig(config: PaletteConfig): PaletteConfig {\n  const themes = config.themes;\n\n  return freezeConfig({\n    ...config,\n    ...(themes\n      ? {\n          themes: {\n            ...(themes.success ? { success: { ...themes.success } } : null),\n            ...(themes.danger ? { danger: { ...themes.danger } } : null),\n            ...(themes.warning ? { warning: { ...themes.warning } } : null),\n            ...(themes.note ? { note: { ...themes.note } } : null),\n            ...(themes.code ? { code: { ...themes.code } } : null),\n          },\n        }\n      : null),\n  });\n}\n\nfunction commit(nextInput: PaletteConfig) {\n  const nextResolved = resolveConfig(nextInput);\n\n  // Bail before bumping the version when nothing observable moved, so re-applying\n  // the same config — an inline `<Root palette={{ … }}>` literal on every\n  // render, a StrictMode double render — costs nothing.\n  if (\n    isSameConfig(resolved, nextResolved) &&\n    pinSignature(input) === pinSignature(nextInput)\n  ) {\n    return;\n  }\n\n  input = snapshotConfig(nextInput);\n  resolved = freezeConfig(nextResolved);\n  version++;\n\n  listeners.forEach((listener) => listener());\n}\n\n/**\n * Set the palette config.\n *\n * **Replaces**, like `useState` — the config you pass *is* the config, resolved\n * against the shipped defaults. Nothing accumulates, so a field you leave out is a\n * field you do not have: dropping a customization means dropping it from the\n * object, and re-applying the same object twice is the same as applying it once.\n *\n * ```ts\n * setPaletteConfig({ hue: 200, baseHue: 60 });\n * setPaletteConfig({ hue: 200 }); // baseHue is gone — back to inheriting `hue`\n * ```\n *\n * To adjust one field of the config already in place — a slider in a settings UI —\n * pass an updater. It receives the config as written, sparse, so spreading it\n * preserves which fields are pinned and which still inherit:\n *\n * ```ts\n * setPaletteConfig((config) => ({ ...config, hue: 200 }));\n * ```\n *\n * The palette is rebuilt lazily on the next token read, and any mounted `<Root>`\n * re-injects the token block — no component re-render is involved, because every\n * color in the kit resolves through a CSS custom property.\n */\nexport function setPaletteConfig(\n  config: PaletteConfig | ((previous: PaletteConfig) => PaletteConfig),\n): void {\n  commit(typeof config === 'function' ? config(input) : config);\n}\n\n/**\n * Drop all tuning and restore the palette the kit ships with. Identical to\n * `setPaletteConfig({})`; it exists to be readable at a call site.\n */\nexport function resetPaletteConfig(): void {\n  commit({});\n}\n\n/**\n * Force every token to re-resolve without changing the palette config.\n *\n * Only needed if you drive Glaze directly — `glaze.configure({ darkTone })` and\n * the like. Glaze invalidates its own caches, but the kit's token maps are\n * memoized against *this* module's version, so they need telling. Calling it\n * before the first paint is unnecessary; nothing has been resolved yet.\n */\nexport function invalidatePaletteTokens(): void {\n  version++;\n  listeners.forEach((listener) => listener());\n}\n\n/** The current config, with every field resolved to a concrete value. */\nexport function getPaletteConfig(): ResolvedPaletteConfig {\n  return resolved;\n}\n\n/**\n * The config **as set**, sparse — omitted fields are the ones still inheriting.\n *\n * {@link getPaletteConfig} resolves everything to concrete values, which loses the\n * distinction between \"explicitly 80\" and \"80 because it follows the brand\". A\n * settings UI needs that distinction to show an inherited value as inherited, and\n * to offer a way back:\n *\n * ```ts\n * const pinned = getPaletteConfigInput().baseHue !== undefined;\n *\n * // Re-link it to the brand by dropping the field.\n * setPaletteConfig(({ baseHue, ...config }) => config);\n * ```\n *\n * It is also the value handed to a {@link setPaletteConfig} updater.\n */\nexport function getPaletteConfigInput(): PaletteConfig {\n  return input;\n}\n\n/**\n * Resolve a patch **over** the current config, without applying it.\n *\n * This one layers, unlike {@link setPaletteConfig}: a preview wants \"the theme in\n * use, but in dark\", so the fields it does not mention have to come from the live\n * config rather than from the defaults. The store is not touched and no listener\n * fires.\n */\nexport function resolvePaletteConfig(\n  config?: PaletteConfig,\n): ResolvedPaletteConfig {\n  if (!config) return resolved;\n\n  return resolveConfig(mergeInput(input, config));\n}\n\n/**\n * Increments whenever the resolved config changes. The token caches in\n * `./palette.ts`, `./colors.ts` and `./index.ts` compare against it instead of\n * memoizing forever — the same idiom Glaze uses for its own config version.\n */\nexport function getPaletteVersion(): number {\n  return version;\n}\n\n/** Subscribe to palette config changes. Returns an unsubscribe function. */\nexport function subscribePaletteConfig(listener: () => void): () => void {\n  listeners.add(listener);\n\n  return () => {\n    listeners.delete(listener);\n  };\n}\n\n// ============================================================================\n// React bindings\n// ============================================================================\n\n/**\n * Re-render on palette config changes. Returns the version, not the config, so\n * the snapshot is a primitive and React never warns about an uncached snapshot.\n */\nexport function usePaletteVersion(): number {\n  return useSyncExternalStore(\n    subscribePaletteConfig,\n    getPaletteVersion,\n    getPaletteVersion,\n  );\n}\n\n/**\n * Read and tune the palette from React, `useState`-style — including the part\n * where the setter *replaces*. A control that changes one field wants the updater\n * form, or it will drop every other field:\n *\n * ```tsx\n * const [palette, setPalette] = usePaletteConfig();\n *\n * <HueSlider\n *   value={palette.hue}\n *   onChange={(hue) => setPalette((config) => ({ ...config, hue }))}\n * />\n * ```\n *\n * The first element is the *resolved* config, so `palette.hue` is always a number.\n * The updater's argument is the sparse one — see {@link getPaletteConfigInput}.\n *\n * The config is global process state, so every consumer of this hook — and every\n * mounted `<Root>` — sees the same palette.\n */\nexport function usePaletteConfig(): readonly [\n  ResolvedPaletteConfig,\n  typeof setPaletteConfig,\n] {\n  usePaletteVersion();\n\n  return [getPaletteConfig(), setPaletteConfig];\n}\n"],"mappings":";;;;;;;;;;;;;;;;AAmBA,MAAa,cAAc;AAC3B,MAAa,sBAAsB;AACnC,MAAa,qBAAqB;AAClC,MAAa,sBAAsB;AACnC,MAAa,mBAAmB;;AAGhC,MAAa,qBAAqB;;;;;;;;;;;;AAalC,MAAa,0BAA0B;AA+HvC,MAAM,qBAAqB;CACzB,SAAS;CACT,QAAQ;CACR,SAAS;CACT,MAAM;CACP;AAED,SAAS,cAAc,OAA6C;CAClE,MAAM,aAAa,MAAM,cAAc;CACvC,MAAM,SAAS,MAAM,UAAU,EAAE;CAEjC,MAAM,MAAM,MAAM,OAAO;AAEzB,QAAO;EACL;EACA,SAAS,MAAM,WAAW;EAC1B;EACA,QAAQ,MAAM,UAAU;EACxB,eAAe,MAAM,iBAAiB;EACtC,QAAQ;GACN,SAAS;IACP,KAAK,OAAO,SAAS,OAAO,mBAAmB;IAC/C,YAAY,OAAO,SAAS,cAAc;IAC3C;GACD,QAAQ;IACN,KAAK,OAAO,QAAQ,OAAO,mBAAmB;IAC9C,YAAY,OAAO,QAAQ,cAAc;IAC1C;GACD,SAAS;IACP,KAAK,OAAO,SAAS,OAAO,mBAAmB;IAC/C,YAAY,OAAO,SAAS,cAAc;IAC3C;GACD,MAAM;IACJ,KAAK,OAAO,MAAM,OAAO,mBAAmB;IAC5C,YAAY,OAAO,MAAM,cAAc;IACxC;GAGD,MAAM,EAAE,YAAY,OAAO,MAAM,cAAc,yBAAyB;GACzE;EACF;;;;;;;AAQH,MAAa,yBAAgD,aAC3D,cAAc,EAAE,CAAC,CAClB;;;;;;;AAYD,IAAI,QAAuB,EAAE;AAC7B,IAAI,WAAkC;AACtC,IAAI,UAAU;AAEd,MAAM,4BAAY,IAAI,KAAiB;AAEvC,SAAS,UACP,MACA,OACe;AACf,KAAI,CAAC,KAAM,QAAO;AAGlB,KAAI,CAAC,MAAO,QAAO;AAEnB,QAAO;EAAE,GAAG;EAAM,GAAG;EAAO;;;;;;AAO9B,SAAS,WAAW,MAAqB,OAAqC;CAC5E,MAAM,OAAsB;EAAE,GAAG;EAAM,GAAG;EAAO;AAEjD,KAAI,KAAK,UAAU,MAAM,OACvB,MAAK,SAAS;EACZ,SAAS,UAAU,KAAK,QAAQ,SAAS,MAAM,QAAQ,QAAQ;EAC/D,QAAQ,UAAU,KAAK,QAAQ,QAAQ,MAAM,QAAQ,OAAO;EAC5D,SAAS,UAAU,KAAK,QAAQ,SAAS,MAAM,QAAQ,QAAQ;EAC/D,MAAM,UAAU,KAAK,QAAQ,MAAM,MAAM,QAAQ,KAAK;EACtD,MAAM,UAAU,KAAK,QAAQ,MAAM,MAAM,QAAQ,KAAK;EACvD;AAGH,QAAO;;AAGT,SAAS,aAAa,GAA0B,GAA0B;AACxE,QACE,EAAE,QAAQ,EAAE,OACZ,EAAE,YAAY,EAAE,WAChB,EAAE,eAAe,EAAE,cACnB,EAAE,WAAW,EAAE,UACf,EAAE,kBAAkB,EAAE,iBACtB,EAAE,OAAO,KAAK,eAAe,EAAE,OAAO,KAAK,cAC1C;EAAC;EAAW;EAAU;EAAW;EAAO,CAAW,OACjD,SACC,EAAE,OAAO,MAAM,QAAQ,EAAE,OAAO,MAAM,OACtC,EAAE,OAAO,MAAM,eAAe,EAAE,OAAO,MAAM,WAChD;;;;;;;;;;;AAaL,SAAS,aAAa,QAA+B;CACnD,MAAM,OAAO,UAAoB,UAAU,SAAY,MAAM;AAE7D,QAAO;EACL,IAAI,OAAO,IAAI;EACf,IAAI,OAAO,QAAQ;EACnB,IAAI,OAAO,WAAW;EACtB,IAAI,OAAO,OAAO;EAClB,IAAI,OAAO,cAAc;EACzB,IAAI,OAAO,QAAQ,MAAM,WAAW;EACpC,GAAI;GAAC;GAAW;GAAU;GAAW;GAAO,CAAW,SAAS,SAAS,CACvE,IAAI,OAAO,SAAS,OAAO,IAAI,EAC/B,IAAI,OAAO,SAAS,OAAO,WAAW,CACvC,CAAC;EACH,CAAC,KAAK,GAAG;;;;;;;;;;;;AAaZ,SAAS,aACP,QACG;CACH,MAAM,SAAS,OAAO;AAEtB,KAAI,QAAQ;AACV,OAAK,MAAM,QAAQ,OAAO,OAAO,OAAO,CACtC,KAAI,KAAM,QAAO,OAAO,KAAK;AAE/B,SAAO,OAAO,OAAO;;AAGvB,QAAO,OAAO,OAAO,OAAO;;;AAI9B,SAAS,eAAe,QAAsC;CAC5D,MAAM,SAAS,OAAO;AAEtB,QAAO,aAAa;EAClB,GAAG;EACH,GAAI,SACA,EACE,QAAQ;GACN,GAAI,OAAO,UAAU,EAAE,SAAS,EAAE,GAAG,OAAO,SAAS,EAAE,GAAG;GAC1D,GAAI,OAAO,SAAS,EAAE,QAAQ,EAAE,GAAG,OAAO,QAAQ,EAAE,GAAG;GACvD,GAAI,OAAO,UAAU,EAAE,SAAS,EAAE,GAAG,OAAO,SAAS,EAAE,GAAG;GAC1D,GAAI,OAAO,OAAO,EAAE,MAAM,EAAE,GAAG,OAAO,MAAM,EAAE,GAAG;GACjD,GAAI,OAAO,OAAO,EAAE,MAAM,EAAE,GAAG,OAAO,MAAM,EAAE,GAAG;GAClD,EACF,GACD;EACL,CAAC;;AAGJ,SAAS,OAAO,WAA0B;CACxC,MAAM,eAAe,cAAc,UAAU;AAK7C,KACE,aAAa,UAAU,aAAa,IACpC,aAAa,MAAM,KAAK,aAAa,UAAU,CAE/C;AAGF,SAAQ,eAAe,UAAU;AACjC,YAAW,aAAa,aAAa;AACrC;AAEA,WAAU,SAAS,aAAa,UAAU,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;AA4B7C,SAAgB,iBACd,QACM;AACN,QAAO,OAAO,WAAW,aAAa,OAAO,MAAM,GAAG,OAAO;;;;;;AAO/D,SAAgB,qBAA2B;AACzC,QAAO,EAAE,CAAC;;;;;;;;;;AAWZ,SAAgB,0BAAgC;AAC9C;AACA,WAAU,SAAS,aAAa,UAAU,CAAC;;;AAI7C,SAAgB,mBAA0C;AACxD,QAAO;;;;;;;;;;;;;;;;;;;AAoBT,SAAgB,wBAAuC;AACrD,QAAO;;;;;;;;;;AAWT,SAAgB,qBACd,QACuB;AACvB,KAAI,CAAC,OAAQ,QAAO;AAEpB,QAAO,cAAc,WAAW,OAAO,OAAO,CAAC;;;;;;;AAQjD,SAAgB,oBAA4B;AAC1C,QAAO;;;AAIT,SAAgB,uBAAuB,UAAkC;AACvE,WAAU,IAAI,SAAS;AAEvB,cAAa;AACX,YAAU,OAAO,SAAS;;;;;;;AAY9B,SAAgB,oBAA4B;AAC1C,QAAO,qBACL,wBACA,mBACA,kBACD;;;;;;;;;;;;;;;;;;;;;;AAuBH,SAAgB,mBAGd;AACA,oBAAmB;AAEnB,QAAO,CAAC,kBAAkB,EAAE,iBAAiB"}
+{"version":3,"file":"palette-config.js","names":[],"sources":["../../src/tokens/palette-config.ts"],"sourcesContent":["import { useSyncExternalStore } from 'react';\n\nimport { colorSeed } from './color-seed';\n\n/**\n * Runtime configuration for the Glaze-generated color palette.\n *\n * The palette recipe itself lives in `./palette.ts`; this module owns only the\n * *seeds* it is built from, plus a version counter the token caches watch. Its only\n * import is the leaf `./color-seed` helper — never the token modules — so there is\n * no import cycle and no ordering hazard. See that file for why reading a colour\n * cannot depend on the global Glaze config `./palette.ts` installs.\n *\n * Reading is free; writing rebuilds the palette on the next token read. See\n * `Getting Started/Theming` in Storybook for the full contract.\n */\n\n// ============================================================================\n// Default seeds\n// ============================================================================\n\n/** Brand hue. Drives the `default`, `primary`, `purple` and `special` themes. */\nexport const DEFAULT_HUE = 280.3;\nexport const DEFAULT_SUCCESS_HUE = 156.9;\nexport const DEFAULT_DANGER_HUE = 23.1;\nexport const DEFAULT_WARNING_HUE = 84.3;\nexport const DEFAULT_NOTE_HUE = 302.3;\n\n/** Seed saturation. Per-color `saturation` in the recipe is a 0–1 factor of it. */\nexport const DEFAULT_SATURATION = 100;\n\n/**\n * Share of {@link DEFAULT_SATURATION} the neutral `surface` carries — the recipe's\n * own `SURFACE_SATURATION` factor, as a fraction.\n *\n * It lives here rather than in the recipe because the dependency runs one way:\n * `./palette.ts` imports the config, not the reverse — and the config needs this\n * number to default `baseSaturation`. It is the anchor of the base zone's own 0–100\n * scale: the share the *accent zone* lends the chrome when no `baseColor` names one\n * outright, so an untouched palette lands on `12`.\n */\nexport const SURFACE_SATURATION_SHARE = 0.12;\n\n/**\n * Ceiling on a base saturation derived from a {@link PaletteConfig.base} color.\n *\n * A named base color lands the chrome near itself rather than at the 12% share the\n * accent lends it, which is the whole reason to name one — but a fully saturated\n * chrome stops being chrome. `50` is well past where the base colors begin to\n * converge (`surface-inverse` tops out around `25`), so the clip costs nothing that\n * was still moving and stops a vivid brand hex from being read as an instruction to\n * paint the page with it.\n *\n * The manual slider in the tuner shares the number, so the two agree on what the top\n * of the range means.\n */\nexport const MAX_BASE_SATURATION = 50;\n\n/**\n * Seed saturation for the `code-*` syntax family, deliberately **not** the same\n * constant as {@link DEFAULT_SATURATION}.\n *\n * The two were one value until the app seed moved to 100 for the pastel palette.\n * Sharing it would have dragged the syntax colors along for the ride — the exact\n * coupling that `PaletteCodeSeed` and the `pastel` opt-out both exist to prevent,\n * and the reason the code family answers to its own saturation and nothing else.\n * Splitting the constant is what lets the app seed move while the code palette\n * stays on the value it was calibrated against.\n */\nexport const DEFAULT_CODE_SATURATION = 80;\n\n// ============================================================================\n// Types\n// ============================================================================\n\n/** The numeric arm of a {@link PaletteSeed}. */\nexport interface PaletteNumericSeed {\n  /** Hue in degrees (0–360). */\n  hue?: number;\n  /** Saturation (0–100). */\n  saturation?: number;\n}\n\n/**\n * One zone's seed: a **color**, or the **numbers**.\n *\n * A string is a color — anything Glaze parses: hex, `rgb()`, `hsl()`, `okhsl()`,\n * `okhst()`, `oklch()`. CSS color keywords (`rebeccapurple`) are not supported, and an\n * unparseable value warns once and falls back to the numeric path with nothing pinned.\n *\n * The union **is** the exclusivity. A zone is seeded one way or the other — never both,\n * never layered — so there is no precedence rule to learn and no contradiction to warn\n * about. It also means a patch that switches form *replaces* rather than merges; layering\n * happens within a path. See {@link resolvePaletteConfig}.\n *\n * What a color supplies differs by zone, and each zone's own field says so:\n * {@link PaletteConfig.accent} keeps the tone but lends the palette none of its chroma,\n * {@link PaletteConfig.base} discards the tone, and a status theme keeps the tone *and*\n * takes the chroma as its seed.\n */\nexport type PaletteSeed = string | PaletteNumericSeed;\n\n/**\n * The `code-*` syntax family takes a saturation and nothing else — and answers to\n * nothing else either. This is the one knob that moves it.\n *\n * Its hues are absolute literals by design, so syntax colors never rotate with the\n * brand — strings would collide with numbers the moment the brand went green, which is\n * also why it is not a {@link PaletteSeed} and cannot take a color. Unlike every other\n * theme, its saturation does **not** inherit the palette-level one: the code palette is\n * calibrated once and stays there, so re-seeding the app cannot quietly wash out a code\n * block. {@link PaletteConfig.pastel} skips it for the same reason.\n */\nexport interface PaletteCodeSeed {\n  /** Saturation (0–100). Defaults to {@link DEFAULT_CODE_SATURATION}, not to the accent's. */\n  saturation?: number;\n}\n\n/**\n * Where the neutral surface ramp sits on the tone scale — see\n * {@link PaletteConfig.surfaceMode}.\n */\nexport type SurfaceMode = 'neutral' | 'tinted';\n\n/** Names of the themes whose seeds can be overridden individually. */\nexport type PaletteThemeName =\n  | 'success'\n  | 'danger'\n  | 'warning'\n  | 'note'\n  | 'code';\n\n/**\n * Palette tuning. Every field is optional; omitted fields keep their default, and\n * per-theme fields left unset inherit the palette-level value.\n *\n * Every zone takes the same {@link PaletteSeed} — a color or the numbers — so the whole\n * config is one idea spelled once, and a settings UI can drive all six zones with one\n * control.\n */\nexport interface PaletteConfig {\n  /**\n   * The **accent** zone — the brand. Drives the `accent-*` family on every theme,\n   * `primary` / `purple` / `special`, and the brand-tinted odds and ends (`focus`, the\n   * loading faces, the disabled chip). Its hue is also the default for\n   * {@link PaletteConfig.base}, and its saturation the default every status theme\n   * inherits.\n   *\n   * **As numbers** — `{ hue, saturation }`. One saturation scale for the whole theme, by\n   * design: every color's own `saturation` is a 0–1 factor of this seed — `surface` at\n   * 0.12, `border` at 0.175, the text ramp at 0.2, the accent family at ~1.0 — so moving\n   * it rescales the palette while keeping those proportions. Unlike hue, which is\n   * configured separately for the brand and for each status theme, saturation is\n   * deliberately not split: the ratio between a subtle surface tint and a saturated\n   * accent is part of the design.\n   *\n   * A `saturation` **belongs to the non-pastel path**, and writing one says so: with no\n   * {@link PaletteConfig.pastel} beside it, it turns pastel off, because tuning a\n   * saturation is the non-pastel path by definition. Pastel is one flat chroma ceiling,\n   * so under it there is exactly one seed and it is the top of the scale. A\n   * `pastel: true` written next to a saturation wins and the saturation is ignored (with\n   * a dev warning) — but it is kept rather than dropped, so turning pastel back off\n   * restores your number.\n   *\n   * **As a color** — the brand, as you have it. Unlike a\n   * {@link PaletteConfig.base} color, which keeps only hue and saturation, this keeps\n   * the **tone** as well — which is the whole point. Without it the brand fill is\n   * authored as a fixed tone step off white, so every accent hue lands at roughly the\n   * same lightness and the color you asked for never actually appears.\n   *\n   * The **light, normal-contrast** variant reproduces the color; dark and high contrast\n   * adapt, as every other color in the palette does. Two things cost exactness even\n   * there: {@link PaletteConfig.pastel} caps chroma (so `#FFD400` softens), and the fill\n   * answers to two APCA floors of deliberately different sizes — **Lc 45 against the\n   * white label** it carries, because a label is text, and only **Lc 25 against\n   * `surface`**, because a fill is a shape. It moves as far as the nearer one requires\n   * and no further.\n   *\n   * Those floors are APCA, not WCAG, and the difference is deliberate: one WCAG ratio\n   * means two very different things by scheme (3:1 measures Lc 56 in light but only\n   * Lc 23 in dark), which crushed light brands while letting dark ones through. A\n   * consequence worth stating plainly — **the emitted fill can sit below WCAG 3:1**.\n   * `#0EA5E9` renders at 2.77:1 against a white page and is correct at that value; the\n   * Lc is the guarantee, not the ratio.\n   *\n   * A color's own chroma is **not** adopted as the zone's seed saturation, which stays at\n   * its default. The accent family gets the chroma through Glaze's `from`, where it is\n   * absolute and seed-independent, and leaving the seed alone is what keeps a saturated\n   * brand out of every status theme that inherits it. A status theme's color behaves the\n   * other way round for the same reason inverted — nothing inherits from a status theme.\n   */\n  accent?: PaletteSeed;\n  /**\n   * The **base** zone: the neutral chrome — `surface` and its ladder, the\n   * `surface-text*` ramp, `border`, `placeholder`.\n   *\n   * **Omit it and the zone follows the accent** — the chrome carries a faint tint of the\n   * brand, at {@link SURFACE_SATURATION_SHARE} of its chroma, unless you say otherwise.\n   * That is the third state, and the reason this field is worth reading back from\n   * {@link getPaletteConfigInput}: absent, an object, or a string are three different\n   * answers to \"does the chrome have a seed of its own\".\n   *\n   * **As numbers** — `{ hue, saturation }`, each independently optional. Splitting the\n   * hue off lets the chrome sit on a different one from the accent — a warm grey UI with\n   * a cool blue brand, say. Only the `default` theme is affected: a colored theme's\n   * tinted `surface` deliberately follows *its own* hue, because a danger banner should\n   * read as red.\n   *\n   * The saturation is on the same 0–100 scale as the accent's, and read the same way.\n   * **The shipped chrome is `12`** — a faint tint is what a neutral surface is — so the\n   * useful range is mostly below a third, and the numbers above it are a deliberately\n   * tinted theme rather than a neutral one. Set it and the base zone stops following the\n   * brand: a vivid accent over near-grey chrome, or a muted accent over visibly warm\n   * chrome, are both one number away and neither is reachable from a single scale.\n   *\n   * The base colors keep their proportions to one another — `border` more than `surface`,\n   * the text ramp more than `border` — until the highest of them hits the top of the\n   * scale, which happens around `25`. Past that they converge.\n   *\n   * Under {@link PaletteConfig.surfaceMode} `'neutral'` it reaches `surface-2`…\n   * `surface-4`, `border`, `placeholder` and the text ramp, but not the page surface: at\n   * the end of the tone scale there is no room for chroma, whatever the seed says.\n   * `'tinted'` is what gives it somewhere to land.\n   *\n   * **As a color** — its **hue and saturation** are read; its **tone is discarded**,\n   * because the chrome's lightness ladder is the design. A base color says which way the\n   * greys lean and how far, not how dark they are.\n   *\n   * The saturation is clipped to {@link MAX_BASE_SATURATION}. Naming a base color says\n   * \"the chrome is this color\", so it lands near it rather than at the share it would\n   * inherit from the accent — but a fully saturated chrome is no longer chrome, so there\n   * is a ceiling on how far \"near\" goes.\n   *\n   * Unlike the accent's, writing a base saturation does *not* turn pastel off: how much\n   * hue the chrome carries says nothing about which chroma space the palette is in.\n   */\n  base?: PaletteSeed;\n  /**\n   * Global. Where the neutral surface ramp sits on the tone scale.\n   *\n   * - `'neutral'` — `surface` is the extreme: pure white in light, the darkest\n   *   step the dark tone window allows in dark. No room for chroma, so the page\n   *   carries no hue however saturated the base zone is.\n   * - `'tinted'` — the whole ramp moves two tones inward, off the extreme.\n   *\n   * Two tones is not a visible lightness change; what it buys is *room*. Chroma\n   * needs distance from white to exist at all, so at the extreme a light page is\n   * white no matter what the base saturation says. Tinted trades two tones of\n   * headroom for a page that actually carries its base hue.\n   *\n   * Everything below `surface` is positioned relative to it, so the ladder, the\n   * borders and the text ramp all follow — and the contrast floors on the text\n   * re-solve against the new background rather than drifting.\n   */\n  surfaceMode?: SurfaceMode;\n  /**\n   * Global. Widens the usable chroma range by relaxing the sRGB-safe limit,\n   * producing a softer, more even palette across hues. Glaze treats `pastel` as\n   * instance-level, so it is threaded into every theme.\n   *\n   * It also **pins the accent's saturation to 100**: the even, hue-independent ceiling\n   * is what pastel is for, and a second saturation scale on top of it would only undo\n   * that. Two paths, then — pastel with no saturation knob, or `pastel: false` with a\n   * free 0–100 one.\n   *\n   * Which is why a lone `accent: { saturation }` picks the second path for you. State\n   * this field only to override that: it is the coarser of the two choices, so it wins\n   * wherever both are set, and a saturation it shadows is ignored with a dev warning.\n   *\n   * The same ceiling is why a color seed cannot render exactly under pastel — `#FFD400`\n   * softens to `#e4d8ad`. Under pastel a color contributes its hue and its tone; turn\n   * pastel off to get its chroma too.\n   *\n   * Every theme except `code`. The syntax family is calibrated on its own saturation and\n   * is deliberately left out — softening it collapses the chroma spread the syntax hues\n   * rely on to stay apart. To soften a code block, lower\n   * {@link PaletteCodeSeed.saturation} instead.\n   */\n  pastel?: boolean;\n  /**\n   * Global. `'auto'` (the default) leaves contrast entirely to the two-tier model:\n   * normal colors plus a high-contrast tier driven by `<html data-contrast=\"high\">`\n   * / `prefers-contrast: more`.\n   *\n   * A number (0–100) additionally positions the **normal** colors on a slider, so\n   * a product can offer its own contrast control. `0` is the shipped palette and\n   * `100` is the high-contrast one, bit for bit.\n   *\n   * The two **compose** rather than replace each other: the high-contrast tier\n   * stays the true high-contrast resolution at every level — identical to what\n   * `'auto'` emits — so a slider raises the baseline while\n   * `prefers-contrast: more` still escalates on top of it. The one exception is\n   * `100`, where the normal colors already *are* the high-contrast ones and a\n   * second tier would only duplicate them.\n   */\n  contrastLevel?: number | 'auto';\n  /**\n   * Per-theme seed overrides. Each status theme takes the same {@link PaletteSeed} the\n   * accent zone does, and inherits the accent's saturation until it sets its own.\n   *\n   * **As numbers** — `{ hue, saturation }`. Status hues have to stay semantically\n   * legible (danger red, warning amber, success green) and far enough apart from each\n   * other and from the brand to read as different things.\n   *\n   * **As a color** — the theme's accent family becomes that color, on the same terms\n   * {@link PaletteConfig.accent} sets: the light/normal-contrast variant reproduces it,\n   * the softened APCA floors apply instead of the white-anchored ladder's WCAG ones, and\n   * the tone is capped so the `#white` label every `type=\"primary\"` item paints on the\n   * fill survives.\n   *\n   * Here the color's chroma **does** become the theme's seed saturation, unlike the\n   * accent's. Nothing inherits from a status theme, so there is nothing to\n   * re-chromatize — and it is what keeps the theme's tinted banner surface, border and\n   * text ramp at their shipped proportions to the fill instead of drifting relative to\n   * it.\n   */\n  themes?: {\n    success?: PaletteSeed;\n    danger?: PaletteSeed;\n    warning?: PaletteSeed;\n    note?: PaletteSeed;\n    code?: PaletteCodeSeed;\n  };\n}\n\n/** {@link PaletteConfig} with every field resolved to a concrete value. */\nexport interface ResolvedPaletteConfig {\n  hue: number;\n  baseHue: number;\n  saturation: number;\n  baseSaturation: number;\n  surfaceMode: SurfaceMode;\n  /**\n   * The accent color as given, handed to Glaze's `from` so the brand family renders\n   * as that literal value rather than as a shade re-derived from the seed.\n   *\n   * `null` — the common case — means no accent color was supplied and the family keeps\n   * its white-anchored derivation, which is the only arrangement that reproduces the\n   * shipped palette bit for bit.\n   */\n  accentColor: string | null;\n  /**\n   * The base color as given, or `null`.\n   *\n   * Nothing renders from it — the hue and the saturation it derives are what reach the\n   * palette. It is resolved anyway so {@link isSameConfig} can compare it, which is the\n   * only way a write that changes the *string* without changing either derived number\n   * still counts as a change. `MAX_BASE_SATURATION` makes that a live case rather than\n   * a theoretical one: every color above the clip on a given hue derives the same pair,\n   * so without this a color picker's whole upper range — and its entire tone axis, which\n   * a base color discards — would drop writes silently and leave the field stale.\n   */\n  baseColor: string | null;\n  /**\n   * The tone of {@link ResolvedPaletteConfig.accentColor}, or `null` alongside it.\n   *\n   * `from` carries the tone itself, so this exists for the one thing that needs the\n   * *number*: the hover brand text sits a fixed tone step past the rest one, and a\n   * step has to be computed.\n   */\n  accentTone: number | null;\n  /**\n   * The saturation of {@link ResolvedPaletteConfig.accentColor}, or `null` beside it.\n   *\n   * On the palette's 0–100 scale, like every other saturation here — and deliberately\n   * *not* the same number as {@link ResolvedPaletteConfig.saturation}, which a color\n   * never raises. The accent family gets this chroma through Glaze's `from`, where it is\n   * absolute; the seed stays where it was so the status themes that inherit it are left\n   * alone.\n   *\n   * Kept as a number because the accent seed is rebuilt from its three components rather\n   * than handed over as the literal: the tone is capped so a white label survives on the\n   * fill, and a capped tone means reconstructing the color anyway.\n   */\n  accentSaturation: number | null;\n  pastel: boolean;\n  contrastLevel: number | 'auto';\n  themes: {\n    success: ResolvedThemeSeed;\n    danger: ResolvedThemeSeed;\n    warning: ResolvedThemeSeed;\n    note: ResolvedThemeSeed;\n    code: { saturation: number };\n  };\n}\n\n/** One status theme's seed, resolved. */\nexport interface ResolvedThemeSeed {\n  hue: number;\n  /**\n   * The theme's Glaze seed, and a ceiling on every color in it.\n   *\n   * On the numeric path this inherits the accent's saturation until the theme pins its\n   * own. On the color path it **is** the color's chroma, which is what keeps the theme's\n   * tinted surface, border and text ramp at their shipped proportions to a fill whose\n   * chroma arrives absolute through `from`. See {@link PaletteConfig.themes} for why the\n   * accent zone does the opposite.\n   */\n  saturation: number;\n  /**\n   * The color as given, handed to Glaze's `from` so this theme's accent family renders\n   * as that literal value rather than as a shade re-derived from the seed.\n   *\n   * `null` — the common case — means the theme is on the numeric path and its accent\n   * family keeps the white-anchored derivation, which is the only arrangement that\n   * reproduces the shipped palette bit for bit.\n   */\n  color: string | null;\n  /**\n   * The tone of {@link ResolvedThemeSeed.color}, or `null` alongside it.\n   *\n   * `from` carries the tone itself, so this exists for the two things that need the\n   * *number*: the hover brand text sits a fixed tone step past the rest one, and the\n   * tone is capped so the `#white` label a `type=\"primary\"` item paints on the fill\n   * survives. Both are arithmetic, and neither can be done to a string.\n   */\n  colorTone: number | null;\n}\n\n// ============================================================================\n// Resolution\n// ============================================================================\n\nconst DEFAULT_THEME_HUES = {\n  success: DEFAULT_SUCCESS_HUE,\n  danger: DEFAULT_DANGER_HUE,\n  warning: DEFAULT_WARNING_HUE,\n  note: DEFAULT_NOTE_HUE,\n} as const;\n\n/**\n * Warned once per process, not once per call.\n *\n * `resolveConfig` runs on every write AND on every `resolvePaletteConfig` preview, so an\n * unguarded warning would fire on every frame of a slider drag.\n */\nlet warnedAboutPastelSaturation = false;\n\n/**\n * One zone's seed, normalized to the four things a resolver can ask for.\n *\n * The single place a {@link PaletteSeed} is taken apart, so the six zones cannot drift\n * in how they read one. A string that {@link colorSeed} cannot parse comes back as the\n * numeric path with nothing pinned, which is exactly the fallback the docs promise: the\n * zone keeps its defaults rather than the render going down over a typo.\n */\nfunction seedOf(seed: PaletteSeed | undefined): {\n  color: string | null;\n  hue: number | undefined;\n  saturation: number | undefined;\n  tone: number | null;\n} {\n  if (typeof seed === 'string') {\n    const parsed = colorSeed(seed);\n\n    return parsed\n      ? {\n          color: seed,\n          hue: parsed.hue,\n          saturation: parsed.saturation,\n          tone: parsed.tone,\n        }\n      : { color: null, hue: undefined, saturation: undefined, tone: null };\n  }\n\n  return {\n    color: null,\n    hue: seed?.hue,\n    saturation: seed?.saturation,\n    tone: null,\n  };\n}\n\n/**\n * Whether a zone pinned a saturation *as a number*.\n *\n * A color's chroma is not a pinned saturation — it reaches the palette through `from`,\n * not through the seed — so it must not answer the question `pastel` asks below.\n */\nfunction pinnedSaturation(seed: PaletteSeed | undefined): number | undefined {\n  return typeof seed === 'string' ? undefined : seed?.saturation;\n}\n\nfunction resolveConfig(input: PaletteConfig): ResolvedPaletteConfig {\n  const themes = input.themes ?? {};\n\n  const accent = seedOf(input.accent);\n  const base = seedOf(input.base);\n\n  // A numeric `saturation` with no `pastel` beside it turns pastel OFF.\n  //\n  // Under pastel there is one saturation and it is the top of the scale, so the two\n  // fields cannot both be honoured — but writing a saturation is only ever a request to\n  // tune it, which is the non-pastel path by definition. Reading it as one keeps\n  // `setPaletteConfig({ accent: { saturation: 55 } })` doing what it always did.\n  //\n  // A COLOR does not answer this question. `accent: '#7a4dbf'` alone still resolves\n  // pastel-on, so the color contributes its hue and its tone but not its chroma — the\n  // documented behaviour, and the reason the tuner writes `pastel: false` explicitly\n  // when it hands a zone a hex.\n  //\n  // An explicit `pastel` wins, both ways: it is the coarser choice of the two, and a\n  // config that states it is choosing a color space rather than a value on one.\n  const accentSaturationPin = pinnedSaturation(input.accent);\n  const pastel = input.pastel ?? accentSaturationPin === undefined;\n\n  // The zone's own seed, or the shipped default. There is no third arm to rank: the\n  // paths are exclusive, so `accent.hue` is the color's on one and the written number on\n  // the other, and never both.\n  const hue = accent.hue ?? DEFAULT_HUE;\n\n  // `base.tone` is never read — that is the whole enforcement of \"a base color says\n  // which way the greys lean and how far, not how dark they are\". Its saturation\n  // *is* read, below.\n  const baseHue = base.hue ?? hue;\n\n  // Only a CONTRADICTION warns — `pastel: true` written next to a saturation it will\n  // ignore. The inference above means a lone saturation is not a contradiction, and a\n  // saturation of exactly 100 is not one either: that is the value pastel pins it to.\n  if (\n    input.pastel === true &&\n    accentSaturationPin !== undefined &&\n    accentSaturationPin !== DEFAULT_SATURATION &&\n    !warnedAboutPastelSaturation\n  ) {\n    warnedAboutPastelSaturation = true;\n    console.warn(\n      `[cube-ui-kit] palette \\`accent.saturation\\` (${accentSaturationPin}) is ignored ` +\n        `because \\`pastel\\` is on — pastel pins it to ${DEFAULT_SATURATION}. Drop ` +\n        `\\`pastel\\`, or set it to \\`false\\`, to tune saturation yourself.`,\n    );\n  }\n\n  // Deliberately the numeric pin only, NOT `accent.saturation`: the accent family\n  // carries a color's own chroma through Glaze's `from`, so the palette-level seed no\n  // longer has to be raised to reach it. Leaving it alone is what keeps a saturated\n  // brand out of every status theme, which all inherit this number.\n  //\n  // The neutral chrome is the one exception, and it is deliberate — `baseSaturation`\n  // below takes its share of the accent's own chroma so a near-grey brand leaves\n  // near-grey chrome. That is scoped to the base zone and capped by this seed; it does\n  // not pass through here.\n  //\n  // A status theme's color is the mirror image, and for the mirror reason: nothing\n  // inherits from a status theme, so its chroma DOES become its seed. See\n  // {@link ResolvedThemeSeed.saturation}.\n  const saturation = pastel\n    ? DEFAULT_SATURATION\n    : accentSaturationPin ?? DEFAULT_SATURATION;\n\n  return {\n    hue,\n    baseHue,\n    saturation,\n    // Three arms, and the middle two are on deliberately different scales.\n    //\n    // A named base COLOR means \"the chrome IS this color\", so it lands near it, clipped\n    // at `MAX_BASE_SATURATION`. Base merely FOLLOWING the accent means \"a faint tint of\n    // the brand\", so it stays the 12% share it has always been — now of the accent's own\n    // chroma, whether that arrived as a number or as a color. Reading `accent.saturation`\n    // here is the one place a brand color reaches the base zone, and it has to: without\n    // it, picking a near-grey brand would leave the chrome carrying 12% of a saturation\n    // nobody asked for.\n    //\n    // BOTH derived arms are also capped by `saturation`, and that is load-bearing rather\n    // than defensive. `baseSaturationScale` divides by the seed, so the chrome's absolute\n    // chroma is a function of this field ALONE — without the cap, an accent color would\n    // cancel the seed out of the base zone entirely and a muted `saturation: 20` would\n    // leave the chrome 4.4x more chromatic than asked for. The seed is a ceiling\n    // everywhere else in the palette; it is one here too.\n    //\n    // A numeric pin is NOT clipped: a number is the more specific instruction, and a\n    // tuner that offers the range is entitled to the top of it.\n    //\n    // Nothing here reaches the status themes, which is what keeps the guarantee that an\n    // accent color cannot re-chromatize them.\n    //\n    // The accent arm sits INSIDE the parentheses on purpose: hoisting it to\n    // `accent.saturation ?? saturation * SHARE` would apply the share to only one of the\n    // two and move the shipped default.\n    baseSaturation:\n      pinnedSaturation(input.base) ??\n      (base.color\n        ? Math.min(base.saturation!, MAX_BASE_SATURATION, saturation)\n        : Math.min(accent.saturation ?? saturation, saturation) *\n          SURFACE_SATURATION_SHARE),\n    surfaceMode: input.surfaceMode ?? 'neutral',\n    accentColor: accent.color,\n    baseColor: base.color,\n    accentTone: accent.tone,\n    accentSaturation: accent.color === null ? null : accent.saturation!,\n    pastel,\n    contrastLevel: input.contrastLevel ?? 'auto',\n    themes: {\n      success: resolveThemeSeed('success', themes.success, saturation),\n      danger: resolveThemeSeed('danger', themes.danger, saturation),\n      warning: resolveThemeSeed('warning', themes.warning, saturation),\n      note: resolveThemeSeed('note', themes.note, saturation),\n      // Deliberately NOT `?? saturation`: the code palette is calibrated once and\n      // does not follow the palette-level seed. See `PaletteCodeSeed`.\n      code: { saturation: themes.code?.saturation ?? DEFAULT_CODE_SATURATION },\n    },\n  };\n}\n\n/**\n * One status theme's seed, on whichever path it is on.\n *\n * The color arm takes all three of the color's components — hue, chroma and tone — where\n * the accent zone deliberately leaves the chroma out of its seed. The asymmetry is the\n * point: this seed is inherited by nothing, so raising it re-chromatizes nothing, and\n * raising it is what holds the theme's tinted surface, border and text ramp in the same\n * proportion to the fill that the shipped derivation gives them.\n */\nfunction resolveThemeSeed(\n  name: keyof typeof DEFAULT_THEME_HUES,\n  seed: PaletteSeed | undefined,\n  saturation: number,\n): ResolvedThemeSeed {\n  const parsed = seedOf(seed);\n\n  if (parsed.color !== null) {\n    return {\n      hue: parsed.hue!,\n      saturation: parsed.saturation!,\n      color: parsed.color,\n      colorTone: parsed.tone,\n    };\n  }\n\n  return {\n    hue: parsed.hue ?? DEFAULT_THEME_HUES[name],\n    saturation: parsed.saturation ?? saturation,\n    color: null,\n    colorTone: null,\n  };\n}\n\n/**\n * The palette as it ships, with no tuning applied. Frozen — it is the baseline\n * every resolution falls back to, so a stray write to it would move the defaults\n * for the whole process.\n */\nexport const DEFAULT_PALETTE_CONFIG: ResolvedPaletteConfig = freezeConfig(\n  resolveConfig({}),\n);\n\n// ============================================================================\n// Store\n// ============================================================================\n\n/**\n * The last config *as written*, sparse — not the resolved one. Keeping the sparse\n * form is what makes inheritance live: a `saturation` with no `themes.danger.\n * saturation` beside it means danger genuinely follows the palette, rather than\n * having been frozen at whatever the palette read when it was set.\n */\nlet input: PaletteConfig = {};\nlet resolved: ResolvedPaletteConfig = DEFAULT_PALETTE_CONFIG;\nlet version = 0;\n\nconst listeners = new Set<() => void>();\n\nfunction mergeSeed(\n  base: PaletteSeed | undefined,\n  patch: PaletteSeed | undefined,\n): PaletteSeed | undefined {\n  // A patch that omits the zone entirely says nothing about it, so the base survives.\n  // Clearing one of its fields is `{ zone: { hue: undefined } }`.\n  if (patch === undefined) return base;\n  if (base === undefined) return patch;\n\n  // Either side being a color makes this a change of PATH, not of value, and a path is\n  // replaced rather than merged — spreading a hex into an object is meaningless in one\n  // direction and would resurrect a discarded color in the other. Layering is a\n  // within-path operation, which is the whole reason `PaletteSeed` is a union.\n  if (typeof base === 'string' || typeof patch === 'string') return patch;\n\n  return { ...base, ...patch };\n}\n\n/** {@link mergeSeed} for the code seed, which is not a {@link PaletteSeed}. */\nfunction mergeCodeSeed(\n  base: PaletteCodeSeed | undefined,\n  patch: PaletteCodeSeed | undefined,\n): PaletteCodeSeed | undefined {\n  if (!base) return patch;\n  if (!patch) return base;\n\n  return { ...base, ...patch };\n}\n\n/**\n * Layer a patch over a base config. Used by {@link resolvePaletteConfig} for\n * previews — *not* by {@link setPaletteConfig}, which replaces.\n */\nfunction mergeInput(base: PaletteConfig, patch: PaletteConfig): PaletteConfig {\n  const next: PaletteConfig = {\n    ...base,\n    ...patch,\n    // Spread alone would replace a zone's whole seed, so a preview of\n    // `{ accent: { hue: 30 } }` over a pinned saturation would silently drop it.\n    ...(base.accent !== undefined || patch.accent !== undefined\n      ? { accent: mergeSeed(base.accent, patch.accent) }\n      : null),\n    ...(base.base !== undefined || patch.base !== undefined\n      ? { base: mergeSeed(base.base, patch.base) }\n      : null),\n  };\n\n  if (base.themes || patch.themes) {\n    next.themes = {\n      success: mergeSeed(base.themes?.success, patch.themes?.success),\n      danger: mergeSeed(base.themes?.danger, patch.themes?.danger),\n      warning: mergeSeed(base.themes?.warning, patch.themes?.warning),\n      note: mergeSeed(base.themes?.note, patch.themes?.note),\n      code: mergeCodeSeed(base.themes?.code, patch.themes?.code),\n    };\n  }\n\n  return next;\n}\n\nfunction isSameConfig(a: ResolvedPaletteConfig, b: ResolvedPaletteConfig) {\n  return (\n    a.hue === b.hue &&\n    a.baseHue === b.baseHue &&\n    a.saturation === b.saturation &&\n    a.baseSaturation === b.baseSaturation &&\n    a.surfaceMode === b.surfaceMode &&\n    // The colors themselves, not just what they derived: a color's chroma no longer\n    // reaches `saturation` (the family gets it through Glaze's `from`), so two brands can\n    // agree on every numeric seed and still render differently. And a base color's\n    // derived pair collapses — everything above `MAX_BASE_SATURATION` on one hue lands\n    // on the same two numbers, and its tone is discarded outright — so comparing the\n    // string is the only thing that lets a color picker's upper range and tone axis\n    // register at all.\n    a.accentColor === b.accentColor &&\n    a.baseColor === b.baseColor &&\n    a.pastel === b.pastel &&\n    a.contrastLevel === b.contrastLevel &&\n    a.themes.code.saturation === b.themes.code.saturation &&\n    (['success', 'danger', 'warning', 'note'] as const).every(\n      (name) =>\n        a.themes[name].hue === b.themes[name].hue &&\n        a.themes[name].saturation === b.themes[name].saturation &&\n        // A status color's hue and chroma DO land in the two numbers above, so this\n        // catches only what they cannot: the tone, and one unparseable string replacing\n        // another.\n        a.themes[name].color === b.themes[name].color,\n    )\n  );\n}\n\n/**\n * Which fields are *explicitly set*, as an order-independent signature.\n *\n * Two configs can resolve to identical values yet differ in which of those values\n * are pinned rather than inherited — pinning a status theme's saturation to the number\n * it already inherited is the obvious case. That difference is invisible to\n * {@link isSameConfig} but visible through {@link getPaletteConfigInput}, so it has\n * to count as a change or a settings UI reading it would never re-render.\n */\nfunction pinSignature(config: PaletteConfig): string {\n  const set = (value: unknown) => (value === undefined ? '0' : '1');\n\n  /**\n   * One zone, in three states — absent, numbers, or a color.\n   *\n   * **Absent is its own state**, not \"numbers with nothing pinned\". `base: {}` and no\n   * `base` at all resolve identically, but they read back differently, and a settings UI\n   * asks exactly that question to decide whether the chrome has a seed of its own or is\n   * still following the accent.\n   *\n   * A color carries its **value**, not just its presence. Presence alone cannot tell one\n   * unparseable string from another: both resolve to `null`, so `isSameConfig` sees no\n   * movement either, and replacing `'bad-one'` with `'bad-two'` returned early — leaving\n   * the field on the first string with no notification that the write was dropped.\n   *\n   * It also means two spellings of the same color (`'#ff0000'` / `'rgb(255 0 0)'`) bump\n   * the version. That is the same argument the presence check was already making: what a\n   * settings UI reads back changed, so it has to re-render. And a zone switching from\n   * `{ hue: 45 }` to a color that happens to derive hue 45 resolves to the same numbers,\n   * so without this the version would never bump and the control would look stuck.\n   */\n  const seed = (value: PaletteSeed | undefined) =>\n    value === undefined\n      ? '-'\n      : typeof value === 'string'\n        ? JSON.stringify(value)\n        : `${set(value.hue)}${set(value.saturation)}`;\n\n  return [\n    seed(config.accent),\n    seed(config.base),\n    set(config.surfaceMode),\n    set(config.pastel),\n    set(config.contrastLevel),\n    set(config.themes?.code?.saturation),\n    ...(['success', 'danger', 'warning', 'note'] as const).map((name) =>\n      seed(config.themes?.[name]),\n    ),\n  ].join('|');\n}\n\n/**\n * Snapshot a config so the store owns it outright.\n *\n * Two hazards this closes. The caller's object stays theirs, so mutating it after\n * the call cannot desync `input` from `resolved`. And what we hand back from\n * {@link getPaletteConfig} / {@link getPaletteConfigInput} is frozen, so a caller\n * who writes to it gets a clear failure rather than silently corrupting the store\n * — the version would not bump, and every token cache would go on serving values\n * that no longer match the config.\n */\nfunction freezeConfig<T extends PaletteConfig | ResolvedPaletteConfig>(\n  config: T,\n): T {\n  const themes = config.themes;\n\n  if (themes) {\n    // A string seed is already immutable, and `Object.freeze` on one is a no-op that\n    // TypeScript would rather we did not ask for.\n    for (const seed of Object.values(themes)) {\n      if (seed && typeof seed === 'object') Object.freeze(seed);\n    }\n    Object.freeze(themes);\n  }\n\n  // Only the sparse INPUT carries zone seeds; the resolved config is flat, so this half\n  // is a no-op for it rather than a branch either caller has to know about.\n  const zones = config as Partial<PaletteConfig>;\n\n  if (typeof zones.accent === 'object') Object.freeze(zones.accent);\n  if (typeof zones.base === 'object') Object.freeze(zones.base);\n\n  return Object.freeze(config);\n}\n\n/** {@link freezeConfig} on a copy, for a config we did not create ourselves. */\nfunction snapshotConfig(config: PaletteConfig): PaletteConfig {\n  const themes = config.themes;\n  // Copy the object arm; a string is already a value.\n  const copy = (seed: PaletteSeed | undefined) =>\n    typeof seed === 'object' ? { ...seed } : seed;\n\n  return freezeConfig({\n    ...config,\n    ...(config.accent !== undefined ? { accent: copy(config.accent) } : null),\n    ...(config.base !== undefined ? { base: copy(config.base) } : null),\n    ...(themes\n      ? {\n          themes: {\n            ...(themes.success !== undefined\n              ? { success: copy(themes.success) }\n              : null),\n            ...(themes.danger !== undefined\n              ? { danger: copy(themes.danger) }\n              : null),\n            ...(themes.warning !== undefined\n              ? { warning: copy(themes.warning) }\n              : null),\n            ...(themes.note !== undefined ? { note: copy(themes.note) } : null),\n            ...(themes.code ? { code: { ...themes.code } } : null),\n          },\n        }\n      : null),\n  });\n}\n\nfunction commit(nextInput: PaletteConfig) {\n  const nextResolved = resolveConfig(nextInput);\n\n  // Bail before bumping the version when nothing observable moved, so re-applying\n  // the same config — an inline `<Root palette={{ … }}>` literal on every\n  // render, a StrictMode double render — costs nothing.\n  if (\n    isSameConfig(resolved, nextResolved) &&\n    pinSignature(input) === pinSignature(nextInput)\n  ) {\n    return;\n  }\n\n  input = snapshotConfig(nextInput);\n  resolved = freezeConfig(nextResolved);\n  version++;\n\n  listeners.forEach((listener) => listener());\n}\n\n/**\n * Set the palette config.\n *\n * **Replaces**, like `useState` — the config you pass *is* the config, resolved\n * against the shipped defaults. Nothing accumulates, so a field you leave out is a\n * field you do not have: dropping a customization means dropping it from the\n * object, and re-applying the same object twice is the same as applying it once.\n *\n * ```ts\n * setPaletteConfig({ accent: { hue: 200 }, base: { hue: 60 } });\n * setPaletteConfig({ accent: { hue: 200 } }); // `base` is gone — follows accent again\n * ```\n *\n * To adjust one field of the config already in place — a slider in a settings UI —\n * pass an updater. It receives the config as written, sparse, so spreading it\n * preserves which fields are pinned and which still inherit:\n *\n * ```ts\n * setPaletteConfig((config) => ({ ...config, accent: { hue: 200 } }));\n * ```\n *\n * The palette is rebuilt lazily on the next token read, and any mounted `<Root>`\n * re-injects the token block — no component re-render is involved, because every\n * color in the kit resolves through a CSS custom property.\n */\nexport function setPaletteConfig(\n  config: PaletteConfig | ((previous: PaletteConfig) => PaletteConfig),\n): void {\n  commit(typeof config === 'function' ? config(input) : config);\n}\n\n/**\n * Drop all tuning and restore the palette the kit ships with. Identical to\n * `setPaletteConfig({})`; it exists to be readable at a call site.\n */\nexport function resetPaletteConfig(): void {\n  commit({});\n}\n\n/**\n * Force every token to re-resolve without changing the palette config.\n *\n * Only needed if you drive Glaze directly — `glaze.configure({ darkTone })` and\n * the like. Glaze invalidates its own caches, but the kit's token maps are\n * memoized against *this* module's version, so they need telling. Calling it\n * before the first paint is unnecessary; nothing has been resolved yet.\n */\nexport function invalidatePaletteTokens(): void {\n  version++;\n  listeners.forEach((listener) => listener());\n}\n\n/** The current config, with every field resolved to a concrete value. */\nexport function getPaletteConfig(): ResolvedPaletteConfig {\n  return resolved;\n}\n\n/**\n * The config **as set**, sparse — omitted fields are the ones still inheriting.\n *\n * {@link getPaletteConfig} resolves everything to concrete values, which loses the\n * distinction between \"explicitly 80\" and \"80 because it follows the brand\". A\n * settings UI needs that distinction to show an inherited value as inherited, and\n * to offer a way back:\n *\n * ```ts\n * const own = getPaletteConfigInput().base !== undefined;\n *\n * // Re-link it to the brand by dropping the field.\n * setPaletteConfig(({ base, ...config }) => config);\n * ```\n *\n * It is also the value handed to a {@link setPaletteConfig} updater.\n */\nexport function getPaletteConfigInput(): PaletteConfig {\n  return input;\n}\n\n/**\n * Resolve a patch **over** the current config, without applying it.\n *\n * This one layers, unlike {@link setPaletteConfig}: a preview wants \"the theme in\n * use, but in dark\", so the fields it does not mention have to come from the live\n * config rather than from the defaults. The store is not touched and no listener\n * fires.\n */\nexport function resolvePaletteConfig(\n  config?: PaletteConfig,\n): ResolvedPaletteConfig {\n  if (!config) return resolved;\n\n  return resolveConfig(mergeInput(input, config));\n}\n\n/**\n * Increments whenever the resolved config changes. The token caches in\n * `./palette.ts`, `./colors.ts` and `./index.ts` compare against it instead of\n * memoizing forever — the same idiom Glaze uses for its own config version.\n */\nexport function getPaletteVersion(): number {\n  return version;\n}\n\n/** Subscribe to palette config changes. Returns an unsubscribe function. */\nexport function subscribePaletteConfig(listener: () => void): () => void {\n  listeners.add(listener);\n\n  return () => {\n    listeners.delete(listener);\n  };\n}\n\n// ============================================================================\n// React bindings\n// ============================================================================\n\n/**\n * Re-render on palette config changes. Returns the version, not the config, so\n * the snapshot is a primitive and React never warns about an uncached snapshot.\n */\nexport function usePaletteVersion(): number {\n  return useSyncExternalStore(\n    subscribePaletteConfig,\n    getPaletteVersion,\n    getPaletteVersion,\n  );\n}\n\n/**\n * Read and tune the palette from React, `useState`-style — including the part\n * where the setter *replaces*. A control that changes one field wants the updater\n * form, or it will drop every other field:\n *\n * ```tsx\n * const [palette, setPalette] = usePaletteConfig();\n *\n * <HueSlider\n *   value={palette.hue}\n *   onChange={(hue) => setPalette((config) => ({ ...config, accent: { hue } }))}\n * />\n * ```\n *\n * The first element is the *resolved* config, so `palette.hue` is always a number — it\n * keeps the flat shape the recipe reads, whichever way the zones were seeded. The\n * updater's argument is the sparse one — see {@link getPaletteConfigInput}.\n *\n * The config is global process state, so every consumer of this hook — and every\n * mounted `<Root>` — sees the same palette.\n */\nexport function usePaletteConfig(): readonly [\n  ResolvedPaletteConfig,\n  typeof setPaletteConfig,\n] {\n  usePaletteVersion();\n\n  return [getPaletteConfig(), setPaletteConfig];\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;AAsBA,MAAa,cAAc;AAC3B,MAAa,sBAAsB;AACnC,MAAa,qBAAqB;AAClC,MAAa,sBAAsB;AACnC,MAAa,mBAAmB;;AAGhC,MAAa,qBAAqB;;;;;;;;;;;AAYlC,MAAa,2BAA2B;;;;;;;;;;;;;;AAexC,MAAa,sBAAsB;;;;;;;;;;;;AAanC,MAAa,0BAA0B;AAkWvC,MAAM,qBAAqB;CACzB,SAAS;CACT,QAAQ;CACR,SAAS;CACT,MAAM;CACP;;;;;;;AAQD,IAAI,8BAA8B;;;;;;;;;AAUlC,SAAS,OAAO,MAKd;AACA,KAAI,OAAO,SAAS,UAAU;EAC5B,MAAM,SAAS,UAAU,KAAK;AAE9B,SAAO,SACH;GACE,OAAO;GACP,KAAK,OAAO;GACZ,YAAY,OAAO;GACnB,MAAM,OAAO;GACd,GACD;GAAE,OAAO;GAAM,KAAK;GAAW,YAAY;GAAW,MAAM;GAAM;;AAGxE,QAAO;EACL,OAAO;EACP,KAAK,MAAM;EACX,YAAY,MAAM;EAClB,MAAM;EACP;;;;;;;;AASH,SAAS,iBAAiB,MAAmD;AAC3E,QAAO,OAAO,SAAS,WAAW,SAAY,MAAM;;AAGtD,SAAS,cAAc,OAA6C;CAClE,MAAM,SAAS,MAAM,UAAU,EAAE;CAEjC,MAAM,SAAS,OAAO,MAAM,OAAO;CACnC,MAAM,OAAO,OAAO,MAAM,KAAK;CAgB/B,MAAM,sBAAsB,iBAAiB,MAAM,OAAO;CAC1D,MAAM,SAAS,MAAM,UAAU,wBAAwB;CAKvD,MAAM,MAAM,OAAO,OAAO;CAK1B,MAAM,UAAU,KAAK,OAAO;AAK5B,KACE,MAAM,WAAW,QACjB,wBAAwB,UACxB,wBAAwB,sBACxB,CAAC,6BACD;AACA,gCAA8B;AAC9B,UAAQ,KACN,gDAAgD,oBAAoB,4DAClB,mBAAmB,yEAEtE;;CAgBH,MAAM,aAAa,SACf,qBACA,uBAAuB;AAE3B,QAAO;EACL;EACA;EACA;EA2BA,gBACE,iBAAiB,MAAM,KAAK,KAC3B,KAAK,QACF,KAAK,IAAI,KAAK,YAAa,qBAAqB,WAAW,GAC3D,KAAK,IAAI,OAAO,cAAc,YAAY,WAAW,GACrD;EACN,aAAa,MAAM,eAAe;EAClC,aAAa,OAAO;EACpB,WAAW,KAAK;EAChB,YAAY,OAAO;EACnB,kBAAkB,OAAO,UAAU,OAAO,OAAO,OAAO;EACxD;EACA,eAAe,MAAM,iBAAiB;EACtC,QAAQ;GACN,SAAS,iBAAiB,WAAW,OAAO,SAAS,WAAW;GAChE,QAAQ,iBAAiB,UAAU,OAAO,QAAQ,WAAW;GAC7D,SAAS,iBAAiB,WAAW,OAAO,SAAS,WAAW;GAChE,MAAM,iBAAiB,QAAQ,OAAO,MAAM,WAAW;GAGvD,MAAM,EAAE,YAAY,OAAO,MAAM,cAAc,yBAAyB;GACzE;EACF;;;;;;;;;;;AAYH,SAAS,iBACP,MACA,MACA,YACmB;CACnB,MAAM,SAAS,OAAO,KAAK;AAE3B,KAAI,OAAO,UAAU,KACnB,QAAO;EACL,KAAK,OAAO;EACZ,YAAY,OAAO;EACnB,OAAO,OAAO;EACd,WAAW,OAAO;EACnB;AAGH,QAAO;EACL,KAAK,OAAO,OAAO,mBAAmB;EACtC,YAAY,OAAO,cAAc;EACjC,OAAO;EACP,WAAW;EACZ;;;;;;;AAQH,MAAa,yBAAgD,aAC3D,cAAc,EAAE,CAAC,CAClB;;;;;;;AAYD,IAAI,QAAuB,EAAE;AAC7B,IAAI,WAAkC;AACtC,IAAI,UAAU;AAEd,MAAM,4BAAY,IAAI,KAAiB;AAEvC,SAAS,UACP,MACA,OACyB;AAGzB,KAAI,UAAU,OAAW,QAAO;AAChC,KAAI,SAAS,OAAW,QAAO;AAM/B,KAAI,OAAO,SAAS,YAAY,OAAO,UAAU,SAAU,QAAO;AAElE,QAAO;EAAE,GAAG;EAAM,GAAG;EAAO;;;AAI9B,SAAS,cACP,MACA,OAC6B;AAC7B,KAAI,CAAC,KAAM,QAAO;AAClB,KAAI,CAAC,MAAO,QAAO;AAEnB,QAAO;EAAE,GAAG;EAAM,GAAG;EAAO;;;;;;AAO9B,SAAS,WAAW,MAAqB,OAAqC;CAC5E,MAAM,OAAsB;EAC1B,GAAG;EACH,GAAG;EAGH,GAAI,KAAK,WAAW,UAAa,MAAM,WAAW,SAC9C,EAAE,QAAQ,UAAU,KAAK,QAAQ,MAAM,OAAO,EAAE,GAChD;EACJ,GAAI,KAAK,SAAS,UAAa,MAAM,SAAS,SAC1C,EAAE,MAAM,UAAU,KAAK,MAAM,MAAM,KAAK,EAAE,GAC1C;EACL;AAED,KAAI,KAAK,UAAU,MAAM,OACvB,MAAK,SAAS;EACZ,SAAS,UAAU,KAAK,QAAQ,SAAS,MAAM,QAAQ,QAAQ;EAC/D,QAAQ,UAAU,KAAK,QAAQ,QAAQ,MAAM,QAAQ,OAAO;EAC5D,SAAS,UAAU,KAAK,QAAQ,SAAS,MAAM,QAAQ,QAAQ;EAC/D,MAAM,UAAU,KAAK,QAAQ,MAAM,MAAM,QAAQ,KAAK;EACtD,MAAM,cAAc,KAAK,QAAQ,MAAM,MAAM,QAAQ,KAAK;EAC3D;AAGH,QAAO;;AAGT,SAAS,aAAa,GAA0B,GAA0B;AACxE,QACE,EAAE,QAAQ,EAAE,OACZ,EAAE,YAAY,EAAE,WAChB,EAAE,eAAe,EAAE,cACnB,EAAE,mBAAmB,EAAE,kBACvB,EAAE,gBAAgB,EAAE,eAQpB,EAAE,gBAAgB,EAAE,eACpB,EAAE,cAAc,EAAE,aAClB,EAAE,WAAW,EAAE,UACf,EAAE,kBAAkB,EAAE,iBACtB,EAAE,OAAO,KAAK,eAAe,EAAE,OAAO,KAAK,cAC1C;EAAC;EAAW;EAAU;EAAW;EAAO,CAAW,OACjD,SACC,EAAE,OAAO,MAAM,QAAQ,EAAE,OAAO,MAAM,OACtC,EAAE,OAAO,MAAM,eAAe,EAAE,OAAO,MAAM,cAI7C,EAAE,OAAO,MAAM,UAAU,EAAE,OAAO,MAAM,MAC3C;;;;;;;;;;;AAaL,SAAS,aAAa,QAA+B;CACnD,MAAM,OAAO,UAAoB,UAAU,SAAY,MAAM;;;;;;;;;;;;;;;;;;;;CAqB7D,MAAM,QAAQ,UACZ,UAAU,SACN,MACA,OAAO,UAAU,WACf,KAAK,UAAU,MAAM,GACrB,GAAG,IAAI,MAAM,IAAI,GAAG,IAAI,MAAM,WAAW;AAEjD,QAAO;EACL,KAAK,OAAO,OAAO;EACnB,KAAK,OAAO,KAAK;EACjB,IAAI,OAAO,YAAY;EACvB,IAAI,OAAO,OAAO;EAClB,IAAI,OAAO,cAAc;EACzB,IAAI,OAAO,QAAQ,MAAM,WAAW;EACpC,GAAI;GAAC;GAAW;GAAU;GAAW;GAAO,CAAW,KAAK,SAC1D,KAAK,OAAO,SAAS,MAAM,CAC5B;EACF,CAAC,KAAK,IAAI;;;;;;;;;;;;AAab,SAAS,aACP,QACG;CACH,MAAM,SAAS,OAAO;AAEtB,KAAI,QAAQ;AAGV,OAAK,MAAM,QAAQ,OAAO,OAAO,OAAO,CACtC,KAAI,QAAQ,OAAO,SAAS,SAAU,QAAO,OAAO,KAAK;AAE3D,SAAO,OAAO,OAAO;;CAKvB,MAAM,QAAQ;AAEd,KAAI,OAAO,MAAM,WAAW,SAAU,QAAO,OAAO,MAAM,OAAO;AACjE,KAAI,OAAO,MAAM,SAAS,SAAU,QAAO,OAAO,MAAM,KAAK;AAE7D,QAAO,OAAO,OAAO,OAAO;;;AAI9B,SAAS,eAAe,QAAsC;CAC5D,MAAM,SAAS,OAAO;CAEtB,MAAM,QAAQ,SACZ,OAAO,SAAS,WAAW,EAAE,GAAG,MAAM,GAAG;AAE3C,QAAO,aAAa;EAClB,GAAG;EACH,GAAI,OAAO,WAAW,SAAY,EAAE,QAAQ,KAAK,OAAO,OAAO,EAAE,GAAG;EACpE,GAAI,OAAO,SAAS,SAAY,EAAE,MAAM,KAAK,OAAO,KAAK,EAAE,GAAG;EAC9D,GAAI,SACA,EACE,QAAQ;GACN,GAAI,OAAO,YAAY,SACnB,EAAE,SAAS,KAAK,OAAO,QAAQ,EAAE,GACjC;GACJ,GAAI,OAAO,WAAW,SAClB,EAAE,QAAQ,KAAK,OAAO,OAAO,EAAE,GAC/B;GACJ,GAAI,OAAO,YAAY,SACnB,EAAE,SAAS,KAAK,OAAO,QAAQ,EAAE,GACjC;GACJ,GAAI,OAAO,SAAS,SAAY,EAAE,MAAM,KAAK,OAAO,KAAK,EAAE,GAAG;GAC9D,GAAI,OAAO,OAAO,EAAE,MAAM,EAAE,GAAG,OAAO,MAAM,EAAE,GAAG;GAClD,EACF,GACD;EACL,CAAC;;AAGJ,SAAS,OAAO,WAA0B;CACxC,MAAM,eAAe,cAAc,UAAU;AAK7C,KACE,aAAa,UAAU,aAAa,IACpC,aAAa,MAAM,KAAK,aAAa,UAAU,CAE/C;AAGF,SAAQ,eAAe,UAAU;AACjC,YAAW,aAAa,aAAa;AACrC;AAEA,WAAU,SAAS,aAAa,UAAU,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;AA4B7C,SAAgB,iBACd,QACM;AACN,QAAO,OAAO,WAAW,aAAa,OAAO,MAAM,GAAG,OAAO;;;;;;AAO/D,SAAgB,qBAA2B;AACzC,QAAO,EAAE,CAAC;;;;;;;;;;AAWZ,SAAgB,0BAAgC;AAC9C;AACA,WAAU,SAAS,aAAa,UAAU,CAAC;;;AAI7C,SAAgB,mBAA0C;AACxD,QAAO;;;;;;;;;;;;;;;;;;;AAoBT,SAAgB,wBAAuC;AACrD,QAAO;;;;;;;;;;AAWT,SAAgB,qBACd,QACuB;AACvB,KAAI,CAAC,OAAQ,QAAO;AAEpB,QAAO,cAAc,WAAW,OAAO,OAAO,CAAC;;;;;;;AAQjD,SAAgB,oBAA4B;AAC1C,QAAO;;;AAIT,SAAgB,uBAAuB,UAAkC;AACvE,WAAU,IAAI,SAAS;AAEvB,cAAa;AACX,YAAU,OAAO,SAAS;;;;;;;AAY9B,SAAgB,oBAA4B;AAC1C,QAAO,qBACL,wBACA,mBACA,kBACD;;;;;;;;;;;;;;;;;;;;;;;AAwBH,SAAgB,mBAGd;AACA,oBAAmB;AAEnB,QAAO,CAAC,kBAAkB,EAAE,iBAAiB"}