@motion-proto/live-tokens 0.49.1 → 0.52.1

package/src/editor/core/store/editorStore.ts

@@ -76,6 +76,7 @@ import {
 } from '../themes/slices/gradients';
 import {
   componentBaseline,
+  getComponentOwnedVarNames,
   loadComponentsFromVars,
   notifyComponentSavedChanged,
   setSavedComponentBaseline,
@@ -510,6 +511,36 @@ export function seedComponentsFromApi(
   schedulePersist();
 }
 
+/**
+ * Replace colors/type and every component slice as one theme transaction.
+ * Theme application used to call `loadFromFile` and `seedComponentsFromApi`
+ * separately, causing two complete renderer passes and briefly exposing a
+ * mixed old-components/new-tokens state. Build the final state first and emit
+ * it once instead.
+ */
+export function loadThemeFromApi(
+  colorsAndType: ColorsAndType,
+  configs: Record<string, ComponentSeed>,
+): void {
+  const next = colorsAndTypeToState(colorsAndType);
+  next.components = {};
+  for (const [comp, cfg] of Object.entries(configs)) {
+    const split = toComponentSlice(comp, cfg.aliases, cfg.config, cfg.schemaVersion ?? 0);
+    next.components[comp] = { aliases: { ...split.aliases }, config: { ...split.config } };
+    setSavedComponentBaseline(comp, componentBaseline(split));
+  }
+  // Defensive legacy cleanup: a colors-and-type payload may still carry
+  // component-owned variables in its catch-all bag. The component slice is
+  // authoritative for a whole-theme load.
+  for (const name of getComponentOwnedVarNames(next)) delete next.cssVars[name];
+
+  resetHistoryForLoad();
+  store.set(next);
+  markColorsAndTypeSaved(next);
+  notifyComponentSavedChanged();
+  schedulePersist();
+}
+
 // ── Colors and type load / save ────────────────────────────────────────────
 
 /**

package/src/editor/core/store/gradientSource.ts

@@ -40,6 +40,9 @@ export interface GradientSourceSnapshot {
 }
 
 export interface GradientSource {
+  /** CSS variable ultimately written by this source. Exposed for editor
+   *  semantics and automated control-to-runtime contract discovery. */
+  targetVariable: string;
   /** Reactive readable of the current gradient value (or undefined if missing). */
   current: Readable<GradientSourceSnapshot | undefined>;
   setAll(next: GradientSourceSnapshot): void;
@@ -67,6 +70,7 @@ export function colorsAndTypeGradientSource(variable: string): GradientSource {
     };
   });
   return {
+    targetVariable: variable,
     current,
     setAll: (next) => setGradient(variable, next),
     setType: (t) => setGradientType(variable, t),
@@ -158,6 +162,7 @@ export function componentGradientSource(component: string, varName: string): Gra
     });
   };
   return {
+    targetVariable: varName,
     current,
     setAll: (next) => writeComponentGradient(component, varName, {
       type: next.type,

package/src/editor/core/themes/colorsAndTypeService.ts

@@ -8,7 +8,6 @@ import {
 import { API_BASE } from '../storage/apiBase';
 import { liveMovedSinceBake } from '../productionPulse';
 import { loadFromFile as loadEditorState, toColorsAndType, markSaved, markColorsAndTypeSaved } from '../store/editorStore';
-import { applyFontSources, applyFontStacks } from '../fonts/fontLoader';
 import { migrateColorsAndTypeFonts } from '../fonts/fontMigration';
 
 // ── API helpers ──────────────────────────────────────────────
@@ -78,18 +77,9 @@ export async function persistColorsAndType(
   markColorsAndTypeSaved(state);
 }
 
-/** Load colors and type into the editor state and re-apply font side-effects
- *  (@font-face rules + `--font-*` CSS vars on :root). */
+/** Load colors and type into the editor state. The store renderer projects
+ *  font sources, stacks, and all other CSS variables in one reactive pass. */
 export function hydrateColorsAndType(colorsAndType: ColorsAndType): void {
   migrateColorsAndTypeFonts(colorsAndType);
   loadEditorState(colorsAndType);
-  // Font data is in state.fonts via loadEditorState; the DOM-side-effect
-  // helpers still need to run so @font-face rules and --font-* CSS vars
-  // land on :root.
-  if (colorsAndType.fontSources && colorsAndType.fontSources.length > 0) {
-    applyFontSources(colorsAndType.fontSources);
-  }
-  if (colorsAndType.fontStacks && colorsAndType.fontStacks.length > 0) {
-    applyFontStacks(colorsAndType.fontStacks, colorsAndType.fontSources ?? []);
-  }
 }

package/src/editor/core/themes/generateColorsAndType.ts

@@ -5,7 +5,7 @@
  * `dist-plugin/generateColorsAndType`, so keep this module Node-safe (no DOM).
  */
 
-import { hexToOklch, type Oklch } from '../palettes/oklch';
+import { hexToOklch, cssColorToOklch, oklchToHexClamped, type Oklch } from '../palettes/oklch';
 import {
   PALETTE_SPECS,
   PALETTE_STEPS,
@@ -201,6 +201,15 @@ function surfaceVars(): string[] {
   ];
 }
 
+/** Derived vars serialize as `oklch()` while the WCAG contrast API is
+ *  sRGB-terminated (decision 7), so project back to hex at this boundary.
+ *  Gradient `--page-bg` parses to null and is skipped, as it was when these
+ *  call sites read hex directly. */
+function varToHex(value: string | undefined): string | null {
+  const parsed = value ? cssColorToOklch(value) : null;
+  return parsed ? oklchToHexClamped(parsed.l, parsed.c, parsed.h) : null;
+}
+
 function worstSurface(
   textHex: string,
   vars: Record<string, string>,
@@ -208,8 +217,8 @@ function worstSurface(
   let against = '';
   let ratio = Infinity;
   for (const surfVar of surfaceVars()) {
-    const surfHex = vars[surfVar];
-    if (!surfHex || !HEX_RE.test(surfHex)) continue;
+    const surfHex = varToHex(vars[surfVar]);
+    if (!surfHex) continue;
     const r = contrastRatio(textHex, surfHex);
     if (r < ratio) {
       ratio = r;
@@ -248,17 +257,18 @@ function runContrastGate(
     const vars = palettesToVars(configs);
     let anyFixed = false;
     for (const def of defs) {
-      const textHex = vars[def.textVar];
-      if (!textHex) continue;
+      const text = cssColorToOklch(vars[def.textVar] ?? '');
+      if (!text) continue;
+      const textHex = oklchToHexClamped(text.l, text.c, text.h);
       const worst = worstSurface(textHex, vars);
       if (worst.ratio >= def.floor) continue;
       const cfg = configs[def.paletteLabel];
       const seed = cfg.baseColor;
       const solved = findLForContrast({
-        against: vars[worst.against],
+        against: varToHex(vars[worst.against]) ?? '#000000',
         ratio: def.target,
         direction,
-        c: hexToOklch(textHex).c,
+        c: text.c,
         h: seed.h,
         lMax: Math.min(1, 2 * seed.l),
       });
@@ -271,7 +281,7 @@ function runContrastGate(
 
   const finalVars = palettesToVars(configs);
   const checks: ContrastCheck[] = defs.map((def) => {
-    const worst = worstSurface(finalVars[def.textVar] ?? '#000000', finalVars);
+    const worst = worstSurface(varToHex(finalVars[def.textVar]) ?? '#000000', finalVars);
     return {
       textVar: def.textVar,
       floor: def.floor,

package/src/editor/core/themes/migrations/2026-05-20-sectiondivider-slim-variants.ts

@@ -28,7 +28,10 @@ const VARIANTS = ['lg', 'md', 'sm'] as const;
 const SUFFIX_RENAMES: Array<[RegExp, string]> = [
   [/-title-border-width$/, '-title-outline-width'],
   [/-title-stroke-color$/, '-title-outline-color'],
-  [/-padding$/, '-spacing'],
+  [
+    /^--sectiondivider-(canvas|neutral|alternate|primary|accent|special)-padding$/,
+    '--sectiondivider-$1-spacing',
+  ],
 ];
 
 function renameKeySuffix(key: string): string {

package/src/editor/core/themes/migrations/2026-05-21-sectiondivider-spacing-to-padding.ts

@@ -16,7 +16,10 @@ export const componentMigration_2026_05_21_sectiondividerSpacingToPadding: Migra
     if (meta.component !== 'sectiondivider') return { ...rawVars };
     const out: Record<string, string> = {};
     for (const [key, value] of Object.entries(rawVars)) {
-      const renamed = key.replace(/-spacing$/, '-padding');
+      const renamed = key.replace(
+        /^--sectiondivider-(lg|md|sm)-spacing$/,
+        '--sectiondivider-$1-padding',
+      );
       out[renamed] = value;
     }
     return out;

package/src/editor/core/themes/migrations/2026-05-25-cornerbadge-flatten-variants.ts

@@ -16,6 +16,7 @@ import type { Migration } from './index';
  */
 const VARIANTS = ['primary', 'accent', 'neutral', 'alternate', 'canvas', 'special', 'success', 'warning', 'danger', 'info'] as const;
 const RE = new RegExp(`^--corner-badge-(${VARIANTS.join('|')})-(.+)$`);
+const CURRENT_COLOR_PROPS = new Set(['surface', 'border', 'text']);
 
 function flattenVariants(rawVars: Record<string, string>, meta: { component?: string }): Record<string, string> {
   if (meta.component !== 'cornerbadge') return rawVars;
@@ -25,6 +26,13 @@ function flattenVariants(rawVars: Record<string, string>, meta: { component?: st
     const m = key.match(RE);
     if (m) {
       const prop = m[2];
+      // The current component composes Badge's per-variant colors under these
+      // same prefixes. They were introduced after this migration and must be
+      // left intact when an otherwise-current unversioned snapshot is loaded.
+      if (CURRENT_COLOR_PROPS.has(prop)) {
+        out[key] = value;
+        continue;
+      }
       if (!collected.has(prop)) collected.set(prop, value);
       continue;
     }

package/src/editor/core/themes/slices/fonts.ts

@@ -1,9 +1,8 @@
 /**
- * Fonts slice — sources + stacks. No derived CSS vars owned by this store
- * (the `--font-*` vars are written by `applyFontStacks` in fontLoader, and
- * @font-face rules by `applyFontSources`). We own the *data* (sources +
- * stacks); callers still invoke the DOM-side-effect helpers themselves
- * after mutating.
+ * Fonts slice — sources + stacks. The editor renderer projects both from the
+ * store: stacks become `--font-*` vars and sources become mirrored
+ * <link>/<style> nodes. Callers only mutate data; undo/redo and hydration then
+ * use the exact same reactive path as the initial edit.
  */
 import type { FontSource, FontStack } from '../themeTypes';
 import { store, mutate, persist } from '../../store/editorCore';

package/src/editor/core/themes/themeDocumentSync.ts

@@ -0,0 +1,66 @@
+import { liveMovedSinceBake } from '../productionPulse';
+import { openThemeSlug } from '../store/editorConfigStore';
+import { loadThemeFromApi } from '../store/editorStore';
+import { migrateColorsAndTypeFonts } from '../fonts/fontMigration';
+import type { ApplyThemeResult } from './themeService';
+
+const CHANNEL_NAME = 'live-tokens:active-theme:v1';
+export const THEME_APPLIED_EVENT = 'live-tokens:theme-applied';
+
+export interface AppliedThemeDetail {
+  fileName: string;
+  result: ApplyThemeResult;
+}
+
+interface AppliedThemeMessage {
+  type: 'theme-applied';
+  fileName: string;
+  result: ApplyThemeResult;
+}
+
+let channel: BroadcastChannel | null = null;
+
+function isAppliedThemeMessage(value: unknown): value is AppliedThemeMessage {
+  if (!value || typeof value !== 'object') return false;
+  const message = value as Partial<AppliedThemeMessage>;
+  return message.type === 'theme-applied'
+    && typeof message.fileName === 'string'
+    && !!message.result
+    && typeof message.result === 'object'
+    && !!message.result.colorsAndType
+    && typeof message.result.componentConfigs === 'object';
+}
+
+/**
+ * Replace this document's editor state with the complete state returned by
+ * the theme apply endpoint. Each same-origin document owns its own Svelte
+ * store, so writing CSS into another document is not enough: the receiving
+ * editor must hydrate the typed palette and component layers as well.
+ */
+export function hydrateAppliedTheme(fileName: string, result: ApplyThemeResult): void {
+  const colorsAndType = structuredClone(result.colorsAndType);
+  migrateColorsAndTypeFonts(colorsAndType);
+  loadThemeFromApi(colorsAndType, structuredClone(result.componentConfigs));
+  openThemeSlug.set(fileName);
+  liveMovedSinceBake.set(false);
+  if (typeof document !== 'undefined') {
+    document.dispatchEvent(new CustomEvent<AppliedThemeDetail>(THEME_APPLIED_EVENT, {
+      detail: { fileName, result },
+    }));
+  }
+}
+
+/** Install the same-origin theme bridge for this window or iframe. */
+export function init(): void {
+  if (channel || typeof BroadcastChannel === 'undefined') return;
+  channel = new BroadcastChannel(CHANNEL_NAME);
+  channel.addEventListener('message', (event: MessageEvent<unknown>) => {
+    if (!isAppliedThemeMessage(event.data)) return;
+    hydrateAppliedTheme(event.data.fileName, event.data.result);
+  });
+}
+
+/** Notify every already-open editor/host document after the server switches. */
+export function broadcastAppliedTheme(fileName: string, result: ApplyThemeResult): void {
+  channel?.postMessage({ type: 'theme-applied', fileName, result } satisfies AppliedThemeMessage);
+}

package/src/editor/core/themes/themeInit.ts

@@ -1,7 +1,6 @@
 import type { AliasDiskValue, ColorsAndType } from './themeTypes';
 import { openThemeSlug } from '../store/editorConfigStore';
 import { migrateColorsAndTypeFonts } from '../fonts/fontMigration';
-import { applyFontSources, applyFontStacks } from '../fonts/fontLoader';
 import { loadFromFile, seedComponentsFromApi } from '../store/editorStore';
 import { getActiveComponentConfig, type ComponentSummary } from '../components/componentConfigService';
 import { safeFetch } from '../storage/storage';
@@ -33,12 +32,6 @@ export async function initializeTheme(): Promise<void> {
   if (colorsAndType) {
     migrateColorsAndTypeFonts(colorsAndType);
     loadFromFile(colorsAndType);
-    if (colorsAndType.fontSources && colorsAndType.fontSources.length > 0) {
-      applyFontSources(colorsAndType.fontSources);
-    }
-    if (colorsAndType.fontStacks && colorsAndType.fontStacks.length > 0) {
-      applyFontStacks(colorsAndType.fontStacks, colorsAndType.fontSources ?? []);
-    }
     openThemeSlug.set(colorsAndType._fileName || 'default');
   }
 
@@ -48,6 +41,7 @@ export async function initializeTheme(): Promise<void> {
       string,
       { aliases: Record<string, AliasDiskValue>; config?: Record<string, unknown>; schemaVersion?: number }
     > = {};
+    let componentReadFailed = false;
     await Promise.all(
       list.components.map(async (c) => {
         const cfg = await getActiveComponentConfig(c.name);
@@ -57,11 +51,14 @@ export async function initializeTheme(): Promise<void> {
             config: cfg.config,
             schemaVersion: cfg.schemaVersion,
           };
+        } else {
+          componentReadFailed = true;
         }
       }),
     );
-    if (Object.keys(configs).length > 0) {
-      seedComponentsFromApi(configs);
-    }
+    // A successful empty list is authoritative. A partial read is not: avoid
+    // replacing the visible design system with a mixture of active configs
+    // and CSS defaults because one request happened to fail during boot.
+    if (!componentReadFailed) seedComponentsFromApi(configs);
   }
 }

package/src/editor/core/themes/themeService.ts

@@ -4,6 +4,7 @@ import { API_BASE } from '../storage/apiBase';
 import { liveMovedSinceBake } from '../productionPulse';
 import { listComponents, getActiveComponentConfig } from '../components/componentConfigService';
 import { getActiveColorsAndType } from './colorsAndTypeService';
+import { broadcastAppliedTheme, hydrateAppliedTheme } from './themeDocumentSync';
 
 /**
  * REST client for theme files, the documents of the editor. A theme carries a
@@ -67,8 +68,11 @@ export interface ApplyThemeResult {
  * `themes/_active.json` at it, and returns the resolved state in one payload.
  * Live reads then fall through to the theme's embedded layers.
  * Production is untouched, so trying a look cannot change what the site ships.
- * Clients follow with a full page reload; opening a theme is a "blow up the
- * world" action.
+ * The resolved response hydrates the caller immediately, then broadcasts the
+ * same typed state to every already-open same-origin host/editor document.
+ * Each store renderer projects that state into its own document, so a theme
+ * loaded from either side keeps the controls, aliases, and visible components
+ * on the same design system without a reload.
  */
 export async function applyTheme(fileName: string): Promise<ApplyThemeResult> {
   const res = await fetch(`${API_BASE}/themes/${encodeURIComponent(fileName)}/apply`, {
@@ -78,7 +82,10 @@ export async function applyTheme(fileName: string): Promise<ApplyThemeResult> {
     const err = await res.json().catch(() => ({ error: 'Apply failed' }));
     throw new Error(err.error || 'Apply failed');
   }
-  return res.json();
+  const result = await res.json() as ApplyThemeResult;
+  hydrateAppliedTheme(fileName, result);
+  broadcastAppliedTheme(fileName, result);
+  return result;
 }
 
 export interface AdoptLookResult {

package/src/editor/core/themes/themeTypes.ts

@@ -16,8 +16,17 @@ export interface PaletteConfig {
   baseColor: Oklch;
   lightnessCurve: CurveAnchor[];
   saturationCurve: CurveAnchor[];
-  scaleCurves: Record<string, { lightness: CurveAnchor[]; saturation: CurveAnchor[] }>;
+  /** Signed hue offset in degrees per step, applied on top of the base hue.
+   *  Absent means flat zero: the palette holds one hue, which is what every
+   *  theme saved before this field did. */
+  hueCurve?: CurveAnchor[];
+  scaleCurves: Record<string, { lightness: CurveAnchor[]; saturation: CurveAnchor[]; hue?: CurveAnchor[] }>;
   curveOffset: Record<string, number>;
+  /** Per curve key: are the tangents derived from the points, or held by hand?
+   *  Only an explicit switch-off is recorded. A missing key means the curve's own
+   *  shape answers (`isAutoSmoothCurve`), which is what every theme saved before
+   *  the flag existed relies on. */
+  curveAutoSmooth?: Record<string, boolean>;
   overrides: Record<string, Oklch>;
   snappedScales: string[];
   emptyMode?: 'solid' | 'gradient';
@@ -30,11 +39,12 @@ export interface PaletteConfig {
   /**
    * Where the base color sits in the ramp while `anchorToBase` is on: the
    * PALETTE_STEPS index whose curve anchors are pinned to the base color
-   * (lightness = base L, saturation = multiplier 100). `displacedL` /
-   * `displacedS` remember the y of a pre-existing anchor (endpoint or
-   * user-authored) the placement overwrote at that x, so moving the
-   * placement or toggling off restores it instead of deleting it.
-   * `priorLightnessEndpoints` / `priorSaturationEndpoints` remember the two
+   * (lightness = base L, saturation = multiplier 100, hue delta = 0 when a
+   * hue curve exists). `displacedL` / `displacedS` / `displacedH` remember
+   * the y of a pre-existing anchor (endpoint or user-authored) the placement
+   * overwrote at that x, so moving the placement or toggling off restores it
+   * instead of deleting it. `priorLightnessEndpoints` /
+   * `priorSaturationEndpoints` / `priorHueEndpoints` remember the two
    * endpoints exactly as they stood before the curve's first-ever placement
    * (a smoothed reshape, not algebraically invertible the way a later
    * scaled-handle re-placement is), so a clear can still restore the true
@@ -44,8 +54,10 @@ export interface PaletteConfig {
     step: number;
     displacedL?: number;
     displacedS?: number;
+    displacedH?: number;
     priorLightnessEndpoints?: [CurveAnchor, CurveAnchor];
     priorSaturationEndpoints?: [CurveAnchor, CurveAnchor];
+    priorHueEndpoints?: [CurveAnchor, CurveAnchor];
   };
   /**
    * Set to true by importers when they overlay `cssVariables[--color-{ns}-*]`

package/src/editor/docs/content/editing-tokens.md

@@ -20,8 +20,12 @@ Success, Warning, Info, Danger, and a few more) has:
 
 - **Base colour.** Pick a hex; the palette derives an 11-step ramp (100 to 950)
   from it.
-- **Curves.** Two curves shape how lightness and saturation fall off across the
-  ramp. Drag the handles to bias it darker, lighter, or more saturated.
+- **Curves.** Three curves shape the ramp, in stack order: Hue, Saturation,
+  Lightness. Drag the handles to bias it warmer or cooler, more or less
+  saturated, darker or lighter. Hue drifts the ramp's temperature without
+  moving contrast, because OKLCH hue rotation is close to lightness-preserving.
+  It holds ±45 degrees; a bigger shift belongs on the base colour or the
+  harmony axis.
 - **Overrides.** Lock a single step to a hand-picked hex when the curve doesn't
   land where you want.
 

package/src/editor/docs/content/themes-workflow.md

@@ -30,7 +30,8 @@ A theme is a document, and the editor works the way any editor does.
   one slot per part of the look. **Save** captures that buffer into the open
   theme.
 - **The production theme** is the one your site ships, named in
-  `themes/_production.json`. Only **Adopt** changes it.
+  `themes/_production.json`. **Adopt** changes it; saving a preset in the Theme
+  Picker performs that Adopt for you.
 
 Absence is the answer for anything untouched: a buffer exists only where the
 live look diverges from the active theme, so a newly opened theme has none.
@@ -43,9 +44,11 @@ In the Theme panel:
   go in as part of it, so there is nothing to save first.
 - **Save As** names a new theme. Use it for your first save and for forking.
 
-Component edits are the exception. Each component editor holds its own unsaved
-state, which this panel cannot write, so save a component in its editor before
-capturing it. The panel says how many are waiting.
+Component editors keep their own unsaved state. If one or more components are
+waiting when you use **Save**, **Save As**, or **Adopt**, the Theme panel offers
+to save all of them before continuing. You can accept once instead of visiting
+each component, or cancel to review them individually. A component editor's
+**Save As** creates a reusable component preset.
 
 Names are tidied to lowercase with hyphens, so "My Brand!" becomes `my-brand`,
 and a leading underscore is dropped: those names are reserved for the buffer.
@@ -54,13 +57,13 @@ to it, and the editor never overwrites it, so start your own with **Save As**.
 
 ## Switching
 
-**Load** lists your saved themes and the seven example looks. Picking one shows
-it on the page as a preview with nothing written to disk, so you can try each
-look and compare. **Save** in that window opens the previewed theme: the active
-pointer changes, the buffers clear, components it does not carry fall through
-to their defaults, and the editor works on it from then on. **Cancel** returns
-you to where you were.
-Trying a look never changes what your site ships.
+**Load**—or clicking the active theme's name—opens the Theme Picker. Picking a
+theme shows it on the page as a preview with nothing written to disk, so you can
+try each look and compare. **Save** in that window opens and adopts the previewed
+theme in one step: the active pointer changes, the buffers clear, components it
+does not carry fall through to their defaults, the editor works on it, and
+production ships it. **Cancel** returns you to where you were. Previewing alone
+never changes what your site ships.
 
 **Colors and type only. Keep my shapes.** narrows the load to the palette and
 the fonts: your component settings stay as they are and the theme you have open

package/src/editor/docs/content/where-themes-live.md

@@ -34,8 +34,8 @@ deleting anything else never breaks it.
 
 - **Editing** changes the page through CSS variables. The editor keeps your
   edits in the browser as you work and writes them to the `_working.json`
-  buffers when you save a component. A buffer exists only where the live layer
-  differs from the active theme's saved layer, so a fresh project has none.
+  buffers when you save a component. When the Theme panel finds several dirty
+  components, **Save all** writes those buffers together.
 - **Save** captures the buffers into the open theme's file. That file is the
   durable copy of your look; matching buffers are then removed.
 - **Load** clears the buffers and points `themes/_active.json` at the theme you

package/src/editor/docs/content.generated.ts

@@ -4,8 +4,8 @@
 export const docContent: Record<string, string> = {
   "01-overview": "# Overview\n\nLive Tokens is a design system for building Svelte microsites quickly. You\nstyle your site by editing tokens and components in a live editor. When it looks right, you save the theme and ship it.\n\n## How it works\n\n- The editor runs in your dev server, on top of your real pages. You style in\n  context, not in a separate sandbox.\n- Every change updates a CSS variable, so the page repaints instantly. No\n  reload, no build step.\n- Saving writes a small JSON file into your project. Shipping bakes your chosen\n  theme into a plain CSS file that the build bundles.\n- The editor is dev-only. Production ships plain CSS variables and the\n  components you used, nothing else.\n\n## What you can edit\n\n- **Tokens**: the design-system primitives, colour palettes, type, spacing,\n  radius, shadow, and gradients, that apply across your whole site.\n- **Components**: the package ships about 25 editable components (Button,\n  IconButton, Card, Dialog, Table, and more). You style components by changing\n  the tokens assigned to each property.\n\n## Where to go next\n\n- **[Getting started](getting-started.md)**: scaffold a project and make your\n  first edit.\n- **[Editing tokens](editing-tokens.md)**: a tour of the editor.\n- **[Themes](themes-workflow.md)**: save, switch, and ship.\n- **[Creating components](creating-components.md)**: make your own components\n  editable.\n",
   "creating-components": "# Creating components\n\nThe package ships about 25 editable components. When you need one it doesn't\nhave, you can make your own Svelte component editable, so anyone using the\neditor can re-point its colours, type, and spacing without touching code.\n\nThe simplest way is to ask Claude. The package bundles a Claude Code skill that\nknows the conventions, writes the files, and checks the result for you.\n\n## Install the skills\n\n```bash\nnpx @motion-proto/live-tokens setup-claude\n```\n\nThis copies the bundled skills into your project's `.claude/skills/`. Once\nthey're there, Claude Code picks them up automatically.\n\n## Ask for a component\n\nDescribe what you want in plain English. Phrases like these trigger the skill:\n\n- \"Add a Toggle component to live-tokens\"\n- \"Make this Svelte component editable in the live-tokens editor\"\n- \"Create a Stat component with a value and a label\"\n\nClaude asks any clarifying questions it needs (which variants, which states,\nwhich parts), then writes the component, registers it with the editor, and runs\nits verification checklist. When it finishes, open `/live-tokens/components` to see your new\ncomponent in the editor and confirm everything works.\n\n## What you get\n\n- A runtime component whose editable properties default to your theme tokens.\n- An editor entry that appears under **Custom** in the `/live-tokens/components` view.\n- The naming and wiring handled for you, so the component fits the system.\n\nAdvanced authors who want to write a component by hand can read the naming and\nstate-model conventions shipped in the package\n(`src/system/styles/CONVENTIONS.md` and the skill's own `SKILL.md`).\n",
-  "editing-tokens": "# Editing tokens\n\nA tour of the editor. The page behind it repaints on every change; saving\nwrites a theme file you can reload later.\n\nThe editor has two views:\n\n- **Tokens**: the design-system primitives (colour, type, spacing, and so on).\n  They apply everywhere your site uses them.\n- **Components**: per-component editors. Re-Assign what tokens a component uses\n  without changing the underlying system.\n\nThis page covers **Tokens**. For components, see\n[Creating components](creating-components.md).\n\n## Palettes\n\nMost colour work happens here. Each palette (Brand, Accent, Neutral, Canvas,\nSuccess, Warning, Info, Danger, and a few more) has:\n\n- **Base colour.** Pick a hex; the palette derives an 11-step ramp (100 to 950)\n  from it.\n- **Curves.** Two curves shape how lightness and saturation fall off across the\n  ramp. Drag the handles to bias it darker, lighter, or more saturated.\n- **Overrides.** Lock a single step to a hand-picked hex when the curve doesn't\n  land where you want.\n\nEditing a palette base ripples through every colour that depends on it, in real\ntime. Colours use OKLCH, so the ramp stays perceptually even across hues\nwithout muddy mid-tones.\n\n## Type\n\n- **Fonts.** Add sources from Google Fonts, Adobe (Typekit), a CSS URL, or an\n  inline `@font-face`. The font loads in the page as soon as you add it.\n- **Stacks.** Named font cascades you reference by token, such as a display\n  stack and a body stack.\n- **Sizes and weights.** A t-shirt scale (xs, sm, md, lg, xl, 2xl…) for size and\n  a numeric scale (100 to 900) for weight.\n\n## Spacing, radius, shadow\n\nNumeric scales with a slider per step.\n\n- **Spacing**: the padding, gap, and margin scale.\n- **Radius**: none through full.\n- **Shadow**: colour, offset, blur, spread, and opacity per step, with stacked\n  shadows supported.\n\nChange a step and every element using it repaints.\n\n## Overlays and gradients\n\n- **Overlays** are translucent tints layered over surfaces, like the subtle\n  tint a card gets on hover. Set a colour and opacity per state.\n- **Gradients** are reusable gradient tokens with a stop list and direction, for\n  hero panels and accent backgrounds.\n\n## Columns\n\nThe page-grid overlay. Set column count, gutter, and outer margin, and toggle\nthe visual guide with `Cmd/Ctrl+G`. Pages built on the column system reflow\nlive.\n\n## Saving\n\nThe editor saves to your browser continuously, so work survives a reload\nmid-edit. Writing a file is a separate step: the **Theme** panel at the foot of\nthe sidebar has **Save**, **Save As**, and **Load**, and each theme is one JSON\nfile under `src/live-tokens/data/themes/`.\n\nThe header gives you undo/redo (`Cmd/Ctrl+Z`, `Cmd/Ctrl+Shift+Z`). You can keep\nmany themes side by side; one is open at a time, and only **Adopt** publishes\none. See [Themes](themes-workflow.md) for the full lifecycle.\n",
+  "editing-tokens": "# Editing tokens\n\nA tour of the editor. The page behind it repaints on every change; saving\nwrites a theme file you can reload later.\n\nThe editor has two views:\n\n- **Tokens**: the design-system primitives (colour, type, spacing, and so on).\n  They apply everywhere your site uses them.\n- **Components**: per-component editors. Re-Assign what tokens a component uses\n  without changing the underlying system.\n\nThis page covers **Tokens**. For components, see\n[Creating components](creating-components.md).\n\n## Palettes\n\nMost colour work happens here. Each palette (Brand, Accent, Neutral, Canvas,\nSuccess, Warning, Info, Danger, and a few more) has:\n\n- **Base colour.** Pick a hex; the palette derives an 11-step ramp (100 to 950)\n  from it.\n- **Curves.** Three curves shape the ramp, in stack order: Hue, Saturation,\n  Lightness. Drag the handles to bias it warmer or cooler, more or less\n  saturated, darker or lighter. Hue drifts the ramp's temperature without\n  moving contrast, because OKLCH hue rotation is close to lightness-preserving.\n  It holds ±45 degrees; a bigger shift belongs on the base colour or the\n  harmony axis.\n- **Overrides.** Lock a single step to a hand-picked hex when the curve doesn't\n  land where you want.\n\nEditing a palette base ripples through every colour that depends on it, in real\ntime. Colours use OKLCH, so the ramp stays perceptually even across hues\nwithout muddy mid-tones.\n\n## Type\n\n- **Fonts.** Add sources from Google Fonts, Adobe (Typekit), a CSS URL, or an\n  inline `@font-face`. The font loads in the page as soon as you add it.\n- **Stacks.** Named font cascades you reference by token, such as a display\n  stack and a body stack.\n- **Sizes and weights.** A t-shirt scale (xs, sm, md, lg, xl, 2xl…) for size and\n  a numeric scale (100 to 900) for weight.\n\n## Spacing, radius, shadow\n\nNumeric scales with a slider per step.\n\n- **Spacing**: the padding, gap, and margin scale.\n- **Radius**: none through full.\n- **Shadow**: colour, offset, blur, spread, and opacity per step, with stacked\n  shadows supported.\n\nChange a step and every element using it repaints.\n\n## Overlays and gradients\n\n- **Overlays** are translucent tints layered over surfaces, like the subtle\n  tint a card gets on hover. Set a colour and opacity per state.\n- **Gradients** are reusable gradient tokens with a stop list and direction, for\n  hero panels and accent backgrounds.\n\n## Columns\n\nThe page-grid overlay. Set column count, gutter, and outer margin, and toggle\nthe visual guide with `Cmd/Ctrl+G`. Pages built on the column system reflow\nlive.\n\n## Saving\n\nThe editor saves to your browser continuously, so work survives a reload\nmid-edit. Writing a file is a separate step: the **Theme** panel at the foot of\nthe sidebar has **Save**, **Save As**, and **Load**, and each theme is one JSON\nfile under `src/live-tokens/data/themes/`.\n\nThe header gives you undo/redo (`Cmd/Ctrl+Z`, `Cmd/Ctrl+Shift+Z`). You can keep\nmany themes side by side; one is open at a time, and only **Adopt** publishes\none. See [Themes](themes-workflow.md) for the full lifecycle.\n",
   "getting-started": "# Getting started\n\nScaffold a live token site in a moments. You need Node 20 or later, a\npackage manager (npm, pnpm, or yarn), and a browser. Open claude code in your repo and start building.\n\n## Scaffold a new app\n\n```bash\nnpm create @motion-proto/live-tokens@latest my-app\ncd my-app\nnpm install\nnpm run dev\n```\n\nOpen the URL Vite prints (usually `http://localhost:5173`). You get a\none-page Svelte + Vite app that depends on the published package, with the\neditor wired up and the full component set ready to import.\n\n`npx @motion-proto/live-tokens create my-app` runs the same scaffold without\nthe initialiser package.\n\n### What the scaffold gives you\n\nEvery editable file lives under `src/` and is committed, so `npm install` and\nversion upgrades never touch your styles. The package code stays in\n`node_modules`.\n\n| Path | What it is |\n|------|------------|\n| `src/pages/Home.svelte` | The starter page. Replace it with your own content. |\n| `src/App.svelte` | Your routes. `<LiveTokensRouter>` adds dev-only routes under a reserved `/live-tokens/*` namespace: `/live-tokens/editor`, `/live-tokens/components`, and `/live-tokens/docs`. |\n| `src/system/styles/tokens.css` | Your base token vocabulary, hand-authored. |\n| `src/styles/site.css` | Themed page typography, yours to edit. |\n\n## Your first edit\n\n1. Run `npm run dev` and open the home page.\n2. Click **Open Token Editor**, or visit `/live-tokens/editor`. The editor opens beside\n   the page.\n3. Open **Palettes**, pick **Brand**, and change the base hex. The page\n   repaints as you type.\n4. In the **Theme** panel at the foot of the sidebar, choose **Save As**. Your\n   theme appears as JSON under `src/live-tokens/data/themes/`.\n5. Reload. The editor reopens on your theme, so the page returns as you left\n   it.\n\n## What you just changed\n\nEvery edit sets a CSS custom property on `:root`. Your components read those\nproperties through `var(--...)`. There is no token build step and no\npreprocessor rewriting your code: the page renders against plain CSS variables\nthe editor swaps live.\n\nTo ship, click **Adopt** in the Theme panel. That saves the open theme and bakes\nit into `src/live-tokens/data/tokens.generated.css`, which your build bundles\nalongside `tokens.css`. Adopt is the only action that changes what your site\nships, so try any look you like first. The editor itself never reaches\nproduction.\n\nAlready have a Svelte 5 + Vite app? The\n[README](https://github.com/motionproto/live-tokens#readme) covers installing\ninto an existing project.\n\n## Where to go next\n\n- **[Editing tokens](editing-tokens.md)**: a tour of the editor.\n- **[Themes](themes-workflow.md)**: save, switch, and ship.\n- **[Creating components](creating-components.md)**: make your own component\n  editable.\n",
-  "themes-workflow": "# Themes\n\nSave your work, switch between looks, and ship one to production.\n\n## The Theme panel\n\nThe **Theme** panel at the foot of the editor sidebar holds the whole look:\ncolors, type, and a setting for every component you changed, in one file. It\ncarries the name the look ships under, whether production is running it, and\n**Adopt**. Two parts sit under it, each a read-out rather than a file to manage.\n\n- **Colors & Type** holds the design tokens. Components read those tokens to\n  define their appearance. It names the two faces the page is showing.\n- **Components** counts how many components run something the theme does not\n  carry, and opens the component editors.\n\nA theme holds its own copy of every part, so one theme can never break another.\n\n## How themes work\n\nA theme is a document, and the editor works the way any editor does.\n\n- **A theme** is a named JSON file in `src/live-tokens/data/themes/`. It carries\n  the whole look: the colors and type plus a setting for every component you\n  changed.\n- **The open theme** is the one the editor is working on, named in\n  `themes/_active.json`. One at a time.\n- **Your unsaved edits** are what the page shows right now. The editor keeps\n  them in your browser as you work and writes them to a buffer, `_working.json`,\n  one slot per part of the look. **Save** captures that buffer into the open\n  theme.\n- **The production theme** is the one your site ships, named in\n  `themes/_production.json`. Only **Adopt** changes it.\n\nAbsence is the answer for anything untouched: a buffer exists only where the\nlive look diverges from the active theme, so a newly opened theme has none.\n\n## Saving\n\nIn the Theme panel:\n\n- **Save** captures the look on screen into the open theme. Your colors and type\n  go in as part of it, so there is nothing to save first.\n- **Save As** names a new theme. Use it for your first save and for forking.\n\nComponent edits are the exception. Each component editor holds its own unsaved\nstate, which this panel cannot write, so save a component in its editor before\ncapturing it. The panel says how many are waiting.\n\nNames are tidied to lowercase with hyphens, so \"My Brand!\" becomes `my-brand`,\nand a leading underscore is dropped: those names are reserved for the buffer.\n**Motion Proto** is the built-in theme and is read-only. You can always return\nto it, and the editor never overwrites it, so start your own with **Save As**.\n\n## Switching\n\n**Load** lists your saved themes and the seven example looks. Picking one shows\nit on the page as a preview with nothing written to disk, so you can try each\nlook and compare. **Save** in that window opens the previewed theme: the active\npointer changes, the buffers clear, components it does not carry fall through\nto their defaults, and the editor works on it from then on. **Cancel** returns\nyou to where you were.\nTrying a look never changes what your site ships.\n\n**Colors and type only. Keep my shapes.** narrows the load to the palette and\nthe fonts: your component settings stay as they are and the theme you have open\nstays open. Saved colors and type files are listed there too, marked *colors &\ntype*, and picking one is always that narrower load.\n\n## Shipping\n\n**Adopt**, in the Theme panel, is the \"ship it\" step, and it ships the whole\nlook. It saves the open theme, then bakes that theme into\n`src/live-tokens/data/tokens.generated.css`, which your build bundles alongside\n`tokens.css`: the colors and type plus every component the theme carries. Fonts\nregenerate to match. The line under the theme name says whether production is\nrunning this theme.\n\nProduction is one saved theme, so nothing else publishes. Trying a look, moving\na token, saving a theme: all of it leaves the generated CSS alone until you\nAdopt. A component editor's Adopt runs the same whole-look step, because a\ncomponent never ships alone. Adopting while Motion Proto is open saves your look\nas a theme of your own first, since the built-in one is read-only.\n\nProduction builds (`npm run build`) ship only that plain CSS and your\ncomponents. No editor, no JSON loading, no runtime indirection.\n\n## Keeping your work safe\n\nEverything under `src/live-tokens/data/` is plain JSON, so commit it. Themes show\nup as readable diffs you can review per branch, and the buffer shows up as the\nwork you have not saved into a theme yet. Nothing is backed up anywhere else:\ngit is your safety net. To experiment freely, **Save As** a new name first, then\nedit.\n\n## Where to go next\n\n- **[Where themes live](where-themes-live.md)**: the files behind all of this,\n  and what writes each one.\n- **[Creating components](creating-components.md)**: make your own components\n  editable in the same editor.\n",
-  "where-themes-live": "# Where themes live\n\nEverything the editor writes is plain JSON and CSS inside your project. There\nis no database and no hidden state: the files are the storage, and git is the\nhistory.\n\n## The data tree\n\n```\nsrc/live-tokens/data/\n  themes/\n    _active.json         names the theme the editor has open\n    _production.json     names the theme your site ships\n    default.json         Motion Proto, the built-in look, rewritten at boot\n    my-brand.json        a saved theme: the whole look in one file\n  colors-and-type/\n    _working.json        unsaved colors and type edits\n  component-configs/\n    button/\n      default.json       Button's shipped settings, derived at boot\n      _working.json      unsaved Button edits\n      my-button.json     a preset you saved from the Button editor\n  tokens.generated.css   the baked CSS your production build ships\nsrc/system/styles/\n  tokens.css             your token vocabulary, hand-authored, never written\n  fonts.css              font imports, rewritten when you Adopt\n```\n\nA saved theme carries the whole look by value: the colors and type plus a\nsetting for every component you changed. It depends on no other file, so\ndeleting anything else never breaks it.\n\n## What writes when\n\n- **Editing** changes the page through CSS variables. The editor keeps your\n  edits in the browser as you work and writes them to the `_working.json`\n  buffers when you save a component. A buffer exists only where the live layer\n  differs from the active theme's saved layer, so a fresh project has none.\n- **Save** captures the buffers into the open theme's file. That file is the\n  durable copy of your look; matching buffers are then removed.\n- **Load** clears the buffers and points `themes/_active.json` at the theme you\n  picked. Live reads fall through to that file. Nothing else changes, so trying\n  looks is free and ordinary switching changes only the pointer.\n- **Adopt** points `themes/_production.json` at the open theme, bakes it into\n  `tokens.generated.css`, and rewrites `fonts.css` to match. It is the only\n  action that changes what your site ships.\n\nThe `default.json` files are the shipped baseline. The editor derives them at\nboot and refreshes them when the package updates; it never saves your work\nover them.\n\nProjects upgraded from 0.48 may initially contain working files copied from the\nactive theme. On the first dev-server boot, exact copies are removed\nautomatically. Any file that differs is kept as unsaved work, so no migration\ncommand is required.\n\n## What to commit\n\nAll of it. The data tree is designed to live in git: themes diff readably, the\ntwo pointers say what is open and what ships, and a `_working.json` in a diff\nis exactly the work you have not yet saved into a theme. Nothing is backed up\nanywhere else.\n\n## Where to go next\n\n- **[Themes](themes-workflow.md)**: the workflow built on these files: saving,\n  loading, and shipping.\n",
+  "themes-workflow": "# Themes\n\nSave your work, switch between looks, and ship one to production.\n\n## The Theme panel\n\nThe **Theme** panel at the foot of the editor sidebar holds the whole look:\ncolors, type, and a setting for every component you changed, in one file. It\ncarries the name the look ships under, whether production is running it, and\n**Adopt**. Two parts sit under it, each a read-out rather than a file to manage.\n\n- **Colors & Type** holds the design tokens. Components read those tokens to\n  define their appearance. It names the two faces the page is showing.\n- **Components** counts how many components run something the theme does not\n  carry, and opens the component editors.\n\nA theme holds its own copy of every part, so one theme can never break another.\n\n## How themes work\n\nA theme is a document, and the editor works the way any editor does.\n\n- **A theme** is a named JSON file in `src/live-tokens/data/themes/`. It carries\n  the whole look: the colors and type plus a setting for every component you\n  changed.\n- **The open theme** is the one the editor is working on, named in\n  `themes/_active.json`. One at a time.\n- **Your unsaved edits** are what the page shows right now. The editor keeps\n  them in your browser as you work and writes them to a buffer, `_working.json`,\n  one slot per part of the look. **Save** captures that buffer into the open\n  theme.\n- **The production theme** is the one your site ships, named in\n  `themes/_production.json`. **Adopt** changes it; saving a preset in the Theme\n  Picker performs that Adopt for you.\n\nAbsence is the answer for anything untouched: a buffer exists only where the\nlive look diverges from the active theme, so a newly opened theme has none.\n\n## Saving\n\nIn the Theme panel:\n\n- **Save** captures the look on screen into the open theme. Your colors and type\n  go in as part of it, so there is nothing to save first.\n- **Save As** names a new theme. Use it for your first save and for forking.\n\nComponent editors keep their own unsaved state. If one or more components are\nwaiting when you use **Save**, **Save As**, or **Adopt**, the Theme panel offers\nto save all of them before continuing. You can accept once instead of visiting\neach component, or cancel to review them individually. A component editor's\n**Save As** creates a reusable component preset.\n\nNames are tidied to lowercase with hyphens, so \"My Brand!\" becomes `my-brand`,\nand a leading underscore is dropped: those names are reserved for the buffer.\n**Motion Proto** is the built-in theme and is read-only. You can always return\nto it, and the editor never overwrites it, so start your own with **Save As**.\n\n## Switching\n\n**Load**—or clicking the active theme's name—opens the Theme Picker. Picking a\ntheme shows it on the page as a preview with nothing written to disk, so you can\ntry each look and compare. **Save** in that window opens and adopts the previewed\ntheme in one step: the active pointer changes, the buffers clear, components it\ndoes not carry fall through to their defaults, the editor works on it, and\nproduction ships it. **Cancel** returns you to where you were. Previewing alone\nnever changes what your site ships.\n\n**Colors and type only. Keep my shapes.** narrows the load to the palette and\nthe fonts: your component settings stay as they are and the theme you have open\nstays open. Saved colors and type files are listed there too, marked *colors &\ntype*, and picking one is always that narrower load.\n\n## Shipping\n\n**Adopt**, in the Theme panel, is the \"ship it\" step, and it ships the whole\nlook. It saves the open theme, then bakes that theme into\n`src/live-tokens/data/tokens.generated.css`, which your build bundles alongside\n`tokens.css`: the colors and type plus every component the theme carries. Fonts\nregenerate to match. The line under the theme name says whether production is\nrunning this theme.\n\nProduction is one saved theme, so nothing else publishes. Trying a look, moving\na token, saving a theme: all of it leaves the generated CSS alone until you\nAdopt. A component editor's Adopt runs the same whole-look step, because a\ncomponent never ships alone. Adopting while Motion Proto is open saves your look\nas a theme of your own first, since the built-in one is read-only.\n\nProduction builds (`npm run build`) ship only that plain CSS and your\ncomponents. No editor, no JSON loading, no runtime indirection.\n\n## Keeping your work safe\n\nEverything under `src/live-tokens/data/` is plain JSON, so commit it. Themes show\nup as readable diffs you can review per branch, and the buffer shows up as the\nwork you have not saved into a theme yet. Nothing is backed up anywhere else:\ngit is your safety net. To experiment freely, **Save As** a new name first, then\nedit.\n\n## Where to go next\n\n- **[Where themes live](where-themes-live.md)**: the files behind all of this,\n  and what writes each one.\n- **[Creating components](creating-components.md)**: make your own components\n  editable in the same editor.\n",
+  "where-themes-live": "# Where themes live\n\nEverything the editor writes is plain JSON and CSS inside your project. There\nis no database and no hidden state: the files are the storage, and git is the\nhistory.\n\n## The data tree\n\n```\nsrc/live-tokens/data/\n  themes/\n    _active.json         names the theme the editor has open\n    _production.json     names the theme your site ships\n    default.json         Motion Proto, the built-in look, rewritten at boot\n    my-brand.json        a saved theme: the whole look in one file\n  colors-and-type/\n    _working.json        unsaved colors and type edits\n  component-configs/\n    button/\n      default.json       Button's shipped settings, derived at boot\n      _working.json      unsaved Button edits\n      my-button.json     a preset you saved from the Button editor\n  tokens.generated.css   the baked CSS your production build ships\nsrc/system/styles/\n  tokens.css             your token vocabulary, hand-authored, never written\n  fonts.css              font imports, rewritten when you Adopt\n```\n\nA saved theme carries the whole look by value: the colors and type plus a\nsetting for every component you changed. It depends on no other file, so\ndeleting anything else never breaks it.\n\n## What writes when\n\n- **Editing** changes the page through CSS variables. The editor keeps your\n  edits in the browser as you work and writes them to the `_working.json`\n  buffers when you save a component. When the Theme panel finds several dirty\n  components, **Save all** writes those buffers together.\n- **Save** captures the buffers into the open theme's file. That file is the\n  durable copy of your look; matching buffers are then removed.\n- **Load** clears the buffers and points `themes/_active.json` at the theme you\n  picked. Live reads fall through to that file. Nothing else changes, so trying\n  looks is free and ordinary switching changes only the pointer.\n- **Adopt** points `themes/_production.json` at the open theme, bakes it into\n  `tokens.generated.css`, and rewrites `fonts.css` to match. It is the only\n  action that changes what your site ships.\n\nThe `default.json` files are the shipped baseline. The editor derives them at\nboot and refreshes them when the package updates; it never saves your work\nover them.\n\nProjects upgraded from 0.48 may initially contain working files copied from the\nactive theme. On the first dev-server boot, exact copies are removed\nautomatically. Any file that differs is kept as unsaved work, so no migration\ncommand is required.\n\n## What to commit\n\nAll of it. The data tree is designed to live in git: themes diff readably, the\ntwo pointers say what is open and what ships, and a `_working.json` in a diff\nis exactly the work you have not yet saved into a theme. Nothing is backed up\nanywhere else.\n\n## Where to go next\n\n- **[Themes](themes-workflow.md)**: the workflow built on these files: saving,\n  loading, and shipping.\n",
 };