@cube-dev/ui-kit 0.0.0-canary-694a764 → 0.0.0-canary-dcbc0fb

package/dist/tokens/palette-config.js

@@ -1,4 +1,5 @@
-/** @license MIT | @cube-dev/ui-kit v0.0.0-canary-694a764 | Cube Dev Team */
+/** @license MIT | @cube-dev/ui-kit v0.0.0-canary-dcbc0fb | 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,32 @@ 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 {@link PaletteConfig.baseSaturation} derived from a
+* {@link PaletteConfig.baseColor}.
+*
+* 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,15 +67,35 @@ 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;
 function resolveConfig(input) {
-	const saturation = input.saturation ?? DEFAULT_SATURATION;
 	const themes = input.themes ?? {};
-	const hue = input.hue ?? DEFAULT_HUE;
+	const accent = input.accentColor ? colorSeed(input.accentColor) : null;
+	const base = input.baseColor ? colorSeed(input.baseColor) : null;
+	const pastel = input.pastel ?? input.saturation === void 0;
+	const hue = input.hue ?? accent?.hue ?? DEFAULT_HUE;
+	const baseHue = input.baseHue ?? base?.hue ?? hue;
+	if (input.pastel === true && input.saturation !== void 0 && input.saturation !== DEFAULT_SATURATION && !warnedAboutPastelSaturation) {
+		warnedAboutPastelSaturation = true;
+		console.warn(`[cube-ui-kit] palette \`saturation\` (${input.saturation}) 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 : input.saturation ?? DEFAULT_SATURATION;
 	return {
 		hue,
-		baseHue: input.baseHue ?? hue,
+		baseHue,
 		saturation,
-		pastel: input.pastel ?? true,
+		baseSaturation: input.baseSaturation ?? (base ? Math.min(base.saturation, MAX_BASE_SATURATION, saturation) : Math.min(accent?.saturation ?? saturation, saturation) * SURFACE_SATURATION_SHARE),
+		surfaceMode: input.surfaceMode ?? "neutral",
+		accentColor: accent ? input.accentColor : null,
+		baseColor: base ? input.baseColor : null,
+		accentTone: accent?.tone ?? null,
+		pastel,
 		contrastLevel: input.contrastLevel ?? "auto",
 		themes: {
 			success: {
@@ -113,7 +161,7 @@ function mergeInput(base, patch) {
 	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",
@@ -132,9 +180,13 @@ function isSameConfig(a, b) {
 function pinSignature(config) {
 	const set = (value) => value === void 0 ? "0" : "1";
 	return [
+		set(config.accentColor),
+		set(config.baseColor),
 		set(config.hue),
 		set(config.baseHue),
 		set(config.saturation),
+		set(config.baseSaturation),
+		set(config.surfaceMode),
 		set(config.pastel),
 		set(config.contrastLevel),
 		set(config.themes?.code?.saturation),
@@ -317,5 +369,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 {@link PaletteConfig.baseSaturation} derived from a\n * {@link PaletteConfig.baseColor}.\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/** 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/**\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,\n * and per-theme fields left unset inherit the palette-level value.\n */\nexport interface PaletteConfig {\n  /**\n   * Accent zone seeded by a **color** rather than a hue — the brand, as you have it.\n   *\n   * Anything Glaze parses: hex, `rgb()`, `hsl()`, `okhsl()`, `okhst()`, `oklch()`.\n   * CSS color keywords (`rebeccapurple`) are not supported. An unparseable value\n   * warns and falls back to the numeric seed.\n   *\n   * Unlike {@link ColorThemeConfig.hue}, which keeps only hue and saturation, this\n   * keeps the **tone** as well — which is the whole point. Without it the brand fill\n   * is authored as a fixed tone step off white, so every accent hue lands at roughly\n   * the same lightness and the color you asked for never actually appears.\n   *\n   * The **light, normal-contrast** variant reproduces the color; dark and high\n   * contrast adapt, as every other color in the palette does. Two things cost\n   * exactness even there: {@link PaletteConfig.pastel} caps chroma (so `#FFD400`\n   * softens), and a color that misses the 3:1 floor against `surface` darkens until\n   * it clears it — and no further.\n   *\n   * {@link PaletteConfig.hue} and {@link PaletteConfig.saturation} still win when\n   * set — the number is the more specific instruction — and the tone keeps coming\n   * from here either way, so a preview can rotate the hue without losing the brand's\n   * lightness.\n   */\n  accentColor?: string;\n  /**\n   * Base zone seeded by a **color** rather than a hue and a saturation.\n   *\n   * Its **hue and saturation** are read; its **tone is discarded**, because the\n   * chrome's lightness ladder is the design — a base color says which way the greys\n   * lean and how far, not how dark they are.\n   *\n   * The saturation is clipped to {@link MAX_BASE_SATURATION}. Naming a base color\n   * says \"the chrome is this color\", so it lands near it rather than at the 12%\n   * share {@link PaletteConfig.baseSaturation} inherits from the accent — but a\n   * fully saturated chrome is no longer chrome, so there is a ceiling on how far\n   * \"near\" goes.\n   *\n   * {@link PaletteConfig.baseHue} and {@link PaletteConfig.baseSaturation} each win\n   * over it when set — the number is the more specific instruction, the same\n   * precedence {@link PaletteConfig.accentColor} sits under.\n   */\n  baseColor?: string;\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   * Saturation seed (0–100) of the **base** zone — the same family\n   * {@link PaletteConfig.baseHue} governs: `surface` and its ladder, the\n   * `surface-text*` ramp, `border`, `placeholder`.\n   *\n   * On the same 0–100 scale as {@link PaletteConfig.saturation}, and read the same\n   * way: `100` is a fully saturated base hue. **The shipped chrome is `12`** — a\n   * faint tint is what a neutral surface is — so the useful range is mostly below\n   * a third, and the numbers above it are a deliberately tinted theme rather than\n   * a neutral one.\n   *\n   * Left unset it is `saturation × 0.12`, which reproduces the recipe's own factor\n   * exactly and keeps a muted palette muting the chrome along with everything\n   * else. Set it and the base zone stops following the brand: a vivid accent over\n   * near-grey chrome, or a muted accent over visibly warm chrome, are both one\n   * number away and neither is reachable from a single scale.\n   *\n   * The base colors keep their proportions to one another — `border` more than\n   * `surface`, the text ramp more than `border` — until the highest of them hits\n   * the top of the scale, which happens around `25`. Past that they converge.\n   *\n   * Under {@link PaletteConfig.surfaceMode} `'neutral'` this reaches\n   * `surface-2`…`surface-4`, `border`, `placeholder` and the text ramp, but not\n   * the page surface: at the end of the tone scale there is no room for chroma,\n   * whatever the seed says. `'tinted'` is what gives it somewhere to land.\n   */\n  baseSaturation?: number;\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 {@link PaletteConfig.baseSaturation} says. Tinted trades\n   * two tones of 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   * Seed saturation (0–100), and the fallback for every theme that does not set\n   * its own.\n   *\n   * **Belongs to the non-pastel path**, and setting it says so: with no\n   * {@link PaletteConfig.pastel} beside it, this 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.\n   *\n   * A `pastel: true` written next to a saturation wins and the saturation is ignored\n   * (with a dev warning) — but it is kept rather than dropped, so turning pastel back\n   * off restores your number.\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   * It also **pins {@link PaletteConfig.saturation} to 100**: the even, hue-independent\n   * ceiling is what pastel is for, and a second saturation scale on top of it would\n   * only undo that. Two paths, then — pastel with no saturation knob, or\n   * `pastel: false` with a free 0–100 one.\n   *\n   * Which is why a lone `saturation` picks the second path for you. State this field\n   * only to override that: it is the coarser of the two choices, so it wins wherever\n   * both are set, and a saturation it shadows is ignored with a dev warning.\n   *\n   * The same ceiling is why an {@link PaletteConfig.accentColor} cannot render\n   * exactly under pastel — `#FFD400` softens to `#e4d8ad`. Under pastel a color\n   * contributes its hue and its tone; turn pastel off to get its chroma too.\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) 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  /** 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  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  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\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\nfunction resolveConfig(input: PaletteConfig): ResolvedPaletteConfig {\n  const themes = input.themes ?? {};\n\n  const accent = input.accentColor ? colorSeed(input.accentColor) : null;\n  const base = input.baseColor ? colorSeed(input.baseColor) : null;\n\n  // A `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({ saturation: 55 })` doing what it always did.\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 pastel = input.pastel ?? input.saturation === undefined;\n\n  // Explicit number > derived from a color > shipped default, for both zones. The\n  // number is the more specific instruction, and keeping it ahead of the color is\n  // what lets `resolvePaletteConfig({ hue: 30 })` rotate a stored `accentColor`\n  // without discarding its tone.\n  const hue = input.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 = input.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    input.saturation !== undefined &&\n    input.saturation !== DEFAULT_SATURATION &&\n    !warnedAboutPastelSaturation\n  ) {\n    warnedAboutPastelSaturation = true;\n    console.warn(\n      `[cube-ui-kit] palette \\`saturation\\` (${input.saturation}) is ignored because ` +\n        `\\`pastel\\` is on — pastel pins it to ${DEFAULT_SATURATION}. Drop \\`pastel\\`, ` +\n        `or set it to \\`false\\`, to tune saturation yourself.`,\n    );\n  }\n\n  // Deliberately NOT `?? accent?.saturation`: the accent family carries the color's\n  // own chroma through Glaze's `from`, so the palette-level seed no longer has to be\n  // raised to reach it. Leaving it alone is what keeps a saturated brand out of every\n  // 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  const saturation = pastel\n    ? DEFAULT_SATURATION\n    : input.saturation ?? 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 `baseColor` means \"the chrome IS this color\", so it lands near it,\n    // clipped at `MAX_BASE_SATURATION`. Base merely FOLLOWING the accent means \"a\n    // faint tint of the brand\", so it stays the 12% share it has always been — now\n    // of the accent's own chroma, whether that arrived as a number or as an\n    // `accentColor`. Reading `accent?.saturation` here is the one place a brand color\n    // reaches the base zone, and it has to: without it, picking a near-grey brand\n    // would leave the chrome carrying 12% of a saturation nobody asked for.\n    //\n    // BOTH arms are also capped by `saturation`, and that is load-bearing rather than\n    // 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\n    // would cancel the seed out of the base zone entirely and a muted\n    // `saturation: 20` would leave the chrome 4.4x more chromatic than asked for.\n    // The seed is a ceiling everywhere else in the palette; it is one here too.\n    //\n    // Nothing here reaches the status themes, which is what keeps the guarantee that\n    // a brand color cannot re-chromatize them.\n    //\n    // Unlike the palette seed, writing this does *not* turn pastel off: how much hue\n    // the chrome carries says nothing about which chroma space the palette is in.\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\n    // the two and move the shipped default.\n    baseSaturation:\n      input.baseSaturation ??\n      (base\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 ? input.accentColor! : null,\n    baseColor: base ? input.baseColor! : null,\n    accentTone: accent?.tone ?? null,\n    pastel,\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.baseSaturation === b.baseSaturation &&\n    a.surfaceMode === b.surfaceMode &&\n    // The colors themselves, not just what they derived: `hue` no longer carries the\n    // accent's chroma (the family gets that 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    )\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    // Both color seeds count, and they have to: a UI switching `{ hue: 45 }` for an\n    // `accentColor` that happens to derive hue 45 resolves to the same numbers, so\n    // without these the version would never bump and the control would look stuck.\n    set(config.accentColor),\n    set(config.baseColor),\n    set(config.hue),\n    set(config.baseHue),\n    set(config.saturation),\n    set(config.baseSaturation),\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).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":";;;;;;;;;;;;;;;;;;AAsBA,MAAa,cAAc;AAC3B,MAAa,sBAAsB;AACnC,MAAa,qBAAqB;AAClC,MAAa,sBAAsB;AACnC,MAAa,mBAAmB;;AAGhC,MAAa,qBAAqB;;;;;;;;;;;AAYlC,MAAa,2BAA2B;;;;;;;;;;;;;;;AAgBxC,MAAa,sBAAsB;;;;;;;;;;;;AAanC,MAAa,0BAA0B;AAuRvC,MAAM,qBAAqB;CACzB,SAAS;CACT,QAAQ;CACR,SAAS;CACT,MAAM;CACP;;;;;;;AAQD,IAAI,8BAA8B;AAElC,SAAS,cAAc,OAA6C;CAClE,MAAM,SAAS,MAAM,UAAU,EAAE;CAEjC,MAAM,SAAS,MAAM,cAAc,UAAU,MAAM,YAAY,GAAG;CAClE,MAAM,OAAO,MAAM,YAAY,UAAU,MAAM,UAAU,GAAG;CAW5D,MAAM,SAAS,MAAM,UAAU,MAAM,eAAe;CAMpD,MAAM,MAAM,MAAM,OAAO,QAAQ,OAAO;CAKxC,MAAM,UAAU,MAAM,WAAW,MAAM,OAAO;AAK9C,KACE,MAAM,WAAW,QACjB,MAAM,eAAe,UACrB,MAAM,eAAe,sBACrB,CAAC,6BACD;AACA,gCAA8B;AAC9B,UAAQ,KACN,yCAAyC,MAAM,WAAW,4DAChB,mBAAmB,yEAE9D;;CAYH,MAAM,aAAa,SACf,qBACA,MAAM,cAAc;AAExB,QAAO;EACL;EACA;EACA;EA2BA,gBACE,MAAM,mBACL,OACG,KAAK,IAAI,KAAK,YAAY,qBAAqB,WAAW,GAC1D,KAAK,IAAI,QAAQ,cAAc,YAAY,WAAW,GACtD;EACN,aAAa,MAAM,eAAe;EAClC,aAAa,SAAS,MAAM,cAAe;EAC3C,WAAW,OAAO,MAAM,YAAa;EACrC,YAAY,QAAQ,QAAQ;EAC5B;EACA,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,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,WAChD;;;;;;;;;;;AAaL,SAAS,aAAa,QAA+B;CACnD,MAAM,OAAO,UAAoB,UAAU,SAAY,MAAM;AAE7D,QAAO;EAIL,IAAI,OAAO,YAAY;EACvB,IAAI,OAAO,UAAU;EACrB,IAAI,OAAO,IAAI;EACf,IAAI,OAAO,QAAQ;EACnB,IAAI,OAAO,WAAW;EACtB,IAAI,OAAO,eAAe;EAC1B,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,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"}