@adea-ai/ui 0.128.2 → 0.128.3

package/dist/lib/accent-presets.d.ts

@@ -0,0 +1,26 @@
+/**
+ * The accent axis.
+ *
+ * adea's accent presets, as a selection rather than a constant. `theme` is the
+ * default and means "the variant's own primary" — monochrome in adea's palette —
+ * and each named preset overrides the interactive roles through the
+ * `[data-accent]` blocks in `theme.css`.
+ *
+ * These are the same six presets `accentPresets` exports in adea's own
+ * `appearance.ts`, and the values match. A consumer's appearance picker and the
+ * workshop's theme toolbar read this one list, so the two cannot disagree about
+ * what a preset is called or what colour it is.
+ */
+export type AccentPreset = {
+    /** The `data-accent` value. `theme` is the variant's own primary. */
+    id: string;
+    label: string;
+    /** What the preset is for, in the gallery and in a picker. */
+    description: string;
+    /** The accent as it appears in the light theme. Absent for `theme`. */
+    light?: string;
+    /** The accent as it appears in the dark theme. Absent for `theme`. */
+    dark?: string;
+};
+export declare const accentPresets: readonly AccentPreset[];
+//# sourceMappingURL=accent-presets.d.ts.map

package/dist/lib/accent-presets.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"accent-presets.d.ts","sourceRoot":"","sources":["../../src/lib/accent-presets.ts"],"names":[],"mappings":"AASA;;;;;;;;;;;;GAYG;AACH,MAAM,MAAM,YAAY,GAAG;IACzB,qEAAqE;IACrE,EAAE,EAAE,MAAM,CAAA;IACV,KAAK,EAAE,MAAM,CAAA;IACb,8DAA8D;IAC9D,WAAW,EAAE,MAAM,CAAA;IACnB,uEAAuE;IACvE,KAAK,CAAC,EAAE,MAAM,CAAA;IACd,sEAAsE;IACtE,IAAI,CAAC,EAAE,MAAM,CAAA;CACd,CAAA;AAED,eAAO,MAAM,aAAa,EAAE,SAAS,YAAY,EAQ/C,CAAA"}

package/dist/lib/accent-presets.js

@@ -0,0 +1,11 @@
+import { ACCENTS } from "@adea-ai/themes";
+//#region src/lib/accent-presets.ts
+var accentPresets = Object.freeze([{
+	id: "theme",
+	label: "Theme",
+	description: "The variant's own primary. Neutral in adea's palette, so the interface stays monochrome."
+}, ...ACCENTS]);
+//#endregion
+export { accentPresets };
+
+//# sourceMappingURL=accent-presets.js.map

package/dist/lib/accent-presets.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"accent-presets.js","names":[],"sources":["../../src/lib/accent-presets.ts"],"sourcesContent":["import { ACCENTS } from '@adea-ai/themes'\n\n/*\n * Its own module so the theme provider's start-up path (the stored-preference reader\n * and the boot script both need the preset ids) does not import the token manifest in\n * `tokens.ts`, which is 20 KB of documentation data a provider never reads.\n * `tokens.ts` re-exports both names, so every existing import keeps working.\n */\n\n/**\n * The accent axis.\n *\n * adea's accent presets, as a selection rather than a constant. `theme` is the\n * default and means \"the variant's own primary\" — monochrome in adea's palette —\n * and each named preset overrides the interactive roles through the\n * `[data-accent]` blocks in `theme.css`.\n *\n * These are the same six presets `accentPresets` exports in adea's own\n * `appearance.ts`, and the values match. A consumer's appearance picker and the\n * workshop's theme toolbar read this one list, so the two cannot disagree about\n * what a preset is called or what colour it is.\n */\nexport type AccentPreset = {\n  /** The `data-accent` value. `theme` is the variant's own primary. */\n  id: string\n  label: string\n  /** What the preset is for, in the gallery and in a picker. */\n  description: string\n  /** The accent as it appears in the light theme. Absent for `theme`. */\n  light?: string\n  /** The accent as it appears in the dark theme. Absent for `theme`. */\n  dark?: string\n}\n\nexport const accentPresets: readonly AccentPreset[] = Object.freeze([\n  {\n    id: 'theme',\n    label: 'Theme',\n    description:\n      \"The variant's own primary. Neutral in adea's palette, so the interface stays monochrome.\",\n  },\n  ...ACCENTS,\n])\n"],"mappings":";;AAkCA,IAAa,gBAAyC,OAAO,OAAO,CAClE;CACE,IAAI;CACJ,OAAO;CACP,aACE;AACJ,GACA,GAAG,OACL,CAAC"}

package/dist/lib/theme-catalogue.d.ts

@@ -0,0 +1,3 @@
+import type { ThemeEngine } from './theme-engine';
+export declare const catalogueThemeEngine: ThemeEngine;
+//# sourceMappingURL=theme-catalogue.d.ts.map

package/dist/lib/theme-catalogue.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"theme-catalogue.d.ts","sourceRoot":"","sources":["../../src/lib/theme-catalogue.ts"],"names":[],"mappings":"AAgBA,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,gBAAgB,CAAA;AAEjD,eAAO,MAAM,oBAAoB,EAAE,WAOlC,CAAA"}

package/dist/lib/theme-catalogue.js

@@ -0,0 +1,22 @@
+import { accentRolesForSelection, accentVariables, builtinThemes, isCatalogueVariant, themeAccentsFor, themeCssVariables } from "./themes.js";
+//#region src/lib/theme-catalogue.ts
+/**
+* The full theme engine, backed by the whole catalogue.
+*
+* This is the module a provider loads when it needs more than the default pair — and,
+* for `ThemeProvider`, always. It imports `lib/themes` (which imports the catalogue)
+* and nothing imports it statically except the eager provider, so a bundler can put
+* it, and the catalogue behind it, in a chunk of its own for the lazy provider.
+*/
+var catalogueThemeEngine = {
+	builtinThemes,
+	isCatalogueVariant,
+	themeCssVariables,
+	accentVariables,
+	accentRolesForSelection,
+	themeAccentsFor
+};
+//#endregion
+export { catalogueThemeEngine };
+
+//# sourceMappingURL=theme-catalogue.js.map

package/dist/lib/theme-catalogue.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"theme-catalogue.js","names":[],"sources":["../../src/lib/theme-catalogue.ts"],"sourcesContent":["/**\n * The full theme engine, backed by the whole catalogue.\n *\n * This is the module a provider loads when it needs more than the default pair — and,\n * for `ThemeProvider`, always. It imports `lib/themes` (which imports the catalogue)\n * and nothing imports it statically except the eager provider, so a bundler can put\n * it, and the catalogue behind it, in a chunk of its own for the lazy provider.\n */\nimport {\n  accentRolesForSelection,\n  accentVariables,\n  builtinThemes,\n  isCatalogueVariant,\n  themeAccentsFor,\n  themeCssVariables,\n} from './themes'\nimport type { ThemeEngine } from './theme-engine'\n\nexport const catalogueThemeEngine: ThemeEngine = {\n  builtinThemes,\n  isCatalogueVariant,\n  themeCssVariables,\n  accentVariables,\n  accentRolesForSelection,\n  themeAccentsFor,\n}\n"],"mappings":";;;;;;;;;;AAkBA,IAAa,uBAAoC;CAC/C;CACA;CACA;CACA;CACA;CACA;AACF"}

package/dist/lib/theme-css.d.ts

@@ -0,0 +1,43 @@
+import type { EditorRolesMode, ThemeCssVariableOptions, ThemeEditorPalette, ThemeVariant } from './themes';
+/** What a variant's custom properties need that depends on the catalogue. */
+export type ThemeCssHooks = {
+    /** The `--primary-subtle` expression of a variant. */
+    primarySubtle(theme: Pick<ThemeVariant, 'id' | 'appearance'>): string;
+    /** The editor ramp of a variant under a projection. */
+    editor(theme: ThemeVariant, mode: EditorRolesMode): ThemeEditorPalette;
+};
+/**
+ * The roles a variant sets, as CSS custom properties.
+ *
+ * The one place that knows the mapping from a theme's roles to this system's variable
+ * names. A provider applies this; nothing else repeats it. The `--terminal-*` and
+ * `--editor-*` ramps are presentations of the catalogue's ANSI and syntax data rather
+ * than separate roles, which is why they are built here and not in the catalogue.
+ *
+ * `options.editor` picks the `--editor-*` projection ({@link EditorRolesMode}).
+ * Absent it, the result is what it has always been; the generated `theme-variants.css`
+ * and the design-system artifact are built without it.
+ */
+export declare function themeCssVariablesWith(hooks: ThemeCssHooks, theme: ThemeVariant, options?: ThemeCssVariableOptions): Record<string, string>;
+/**
+ * The `--terminal-*` properties of a variant: the palette a terminal paints.
+ *
+ * What a pinned terminal theme writes over the interface variant's own. The names
+ * are the ones {@link themeCssVariablesWith} writes, and a custom variant's verbatim
+ * `tokens` still win, so they can never drift from what the interface variant would
+ * have written for the same palette. Built from the terminal palette alone: it needs
+ * neither the catalogue nor the rest of the variant's roles.
+ */
+export declare function terminalCssVariables(theme: ThemeVariant): Record<string, string>;
+/**
+ * Token values with every `oklch()` colour written as `#rrggbb`.
+ *
+ * For a host whose stylesheet, tests or native shell speak hex: the catalogue's
+ * roles are `oklch()` strings, and this is the one conversion, gamut-mapped by the
+ * catalogue's own `oklchToHex`. A value that is already hex, carries alpha
+ * (`rgba()`), or is not a plain colour (`color-mix()`, `var()`) is left byte for
+ * byte, because converting would either lose the alpha or be a guess. Suitable as
+ * `ThemeProvider`'s `transformTokens`.
+ */
+export declare function tokensAsHex(tokens: Readonly<Record<string, string>>): Record<string, string>;
+//# sourceMappingURL=theme-css.d.ts.map

package/dist/lib/theme-css.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"theme-css.d.ts","sourceRoot":"","sources":["../../src/lib/theme-css.ts"],"names":[],"mappings":"AAaA,OAAO,KAAK,EACV,eAAe,EACf,uBAAuB,EACvB,kBAAkB,EAClB,YAAY,EACb,MAAM,UAAU,CAAA;AAEjB,6EAA6E;AAC7E,MAAM,MAAM,aAAa,GAAG;IAC1B,sDAAsD;IACtD,aAAa,CAAC,KAAK,EAAE,IAAI,CAAC,YAAY,EAAE,IAAI,GAAG,YAAY,CAAC,GAAG,MAAM,CAAA;IACrE,uDAAuD;IACvD,MAAM,CAAC,KAAK,EAAE,YAAY,EAAE,IAAI,EAAE,eAAe,GAAG,kBAAkB,CAAA;CACvE,CAAA;AAED;;;;;;;;;;;GAWG;AACH,wBAAgB,qBAAqB,CACnC,KAAK,EAAE,aAAa,EACpB,KAAK,EAAE,YAAY,EACnB,OAAO,GAAE,uBAA4B,GACpC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CA2FxB;AA2BD;;;;;;;;GAQG;AACH,wBAAgB,oBAAoB,CAAC,KAAK,EAAE,YAAY,GAAG,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAOhF;AAED;;;;;;;;;GASG;AACH,wBAAgB,WAAW,CAAC,MAAM,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,GAAG,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAU5F"}

package/dist/lib/theme-css.js

@@ -0,0 +1,167 @@
+import { primaryHover } from "@adea-ai/themes";
+import { oklchToHex, parseColor } from "@adea-ai/themes/oklch";
+//#region src/lib/theme-css.ts
+/**
+* The mapping from a variant's roles to this system's custom properties, without the
+* catalogue.
+*
+* `themeCssVariables` needs two things only the catalogue can measure for a theme:
+* the strength of its `--primary-subtle` tint and its floor-projected editor ramp.
+* Those are the `hooks`, so this module imports no catalogue data and a host that
+* never loads the catalogue can still paint a variant it already holds. `lib/themes`
+* binds the hooks to the catalogue and keeps exporting the same
+* `themeCssVariables`; `lib/theme-engine` binds them to the precomputed default pair.
+*/
+/**
+* The roles a variant sets, as CSS custom properties.
+*
+* The one place that knows the mapping from a theme's roles to this system's variable
+* names. A provider applies this; nothing else repeats it. The `--terminal-*` and
+* `--editor-*` ramps are presentations of the catalogue's ANSI and syntax data rather
+* than separate roles, which is why they are built here and not in the catalogue.
+*
+* `options.editor` picks the `--editor-*` projection ({@link EditorRolesMode}).
+* Absent it, the result is what it has always been; the generated `theme-variants.css`
+* and the design-system artifact are built without it.
+*/
+function themeCssVariablesWith(hooks, theme, options = {}) {
+	const c = theme.colors;
+	const t = theme.terminal;
+	const e = hooks.editor(theme, options.editor ?? "syntax");
+	const derived = {
+		"--background": c.background,
+		"--foreground": c.foreground,
+		"--card": c.card,
+		"--card-foreground": c.cardForeground,
+		"--popover": c.popover,
+		"--popover-foreground": c.popoverForeground,
+		"--primary": c.primary,
+		"--primary-foreground": c.primaryForeground,
+		"--primary-hover": primaryHover(c.primary, theme.appearance),
+		"--primary-subtle": hooks.primarySubtle(theme),
+		"--secondary": c.secondary,
+		"--secondary-foreground": c.secondaryForeground,
+		"--muted": c.muted,
+		"--muted-foreground": c.mutedForeground,
+		"--accent": c.accent,
+		"--accent-foreground": c.accentForeground,
+		"--destructive": c.destructive,
+		"--destructive-foreground": c.destructiveForeground,
+		"--destructive-subtle": c.destructiveSubtle,
+		"--destructive-action": c.destructiveAction,
+		"--destructive-action-foreground": c.destructiveActionForeground,
+		"--success": c.success,
+		"--success-foreground": c.successForeground,
+		"--success-subtle": c.successSubtle,
+		"--warning": c.warning,
+		"--warning-foreground": c.warningForeground,
+		"--warning-subtle": c.warningSubtle,
+		"--info": c.info,
+		"--info-foreground": c.infoForeground,
+		"--info-subtle": c.infoSubtle,
+		"--border": c.border,
+		"--input": c.input,
+		"--ring": c.ring,
+		"--sidebar": c.sidebar,
+		"--sidebar-foreground": c.sidebarForeground,
+		"--sidebar-accent": c.sidebarAccent,
+		"--sidebar-border": c.sidebarBorder,
+		"--sidebar-primary": c.primary,
+		"--sidebar-primary-foreground": c.primaryForeground,
+		"--sidebar-ring": c.ring,
+		"--sidebar-muted-foreground": c.sidebarMutedForeground,
+		"--surface-sunken": c.muted,
+		"--surface-hover": c.accent,
+		"--surface-active": c.border,
+		"--chrome": c.background,
+		...terminalVariables(t),
+		"--editor-keyword": e.keyword,
+		"--editor-string": e.string,
+		"--editor-number": e.number,
+		"--editor-comment": e.comment,
+		"--editor-function": e.function,
+		"--editor-variable": e.variable,
+		"--editor-type": e.type,
+		"--editor-tag": e.tag,
+		"--editor-attribute": e.attribute,
+		"--editor-operator": e.operator,
+		"--editor-heading": e.heading,
+		"--editor-link": e.link,
+		"--editor-diff-add": e.diffAdd,
+		"--editor-diff-delete": e.diffDelete,
+		"--editor-diff-hunk": e.diffHunk,
+		"--editor-search-match": e.searchMatch,
+		"--chart-1": theme.chart[0] ?? c.primary,
+		"--chart-2": theme.chart[1] ?? c.info,
+		"--chart-3": theme.chart[2] ?? c.success,
+		"--chart-4": theme.chart[3] ?? c.warning,
+		"--chart-5": theme.chart[4] ?? c.destructive,
+		"--chart-6": theme.chart[5] ?? c.mutedForeground
+	};
+	return theme.tokens ? {
+		...derived,
+		...theme.tokens
+	} : derived;
+}
+function terminalVariables(t) {
+	return {
+		"--terminal-background": t.background,
+		"--terminal-foreground": t.foreground,
+		"--terminal-cursor": t.cursor,
+		"--terminal-selection": t.selection,
+		"--terminal-ansi-black": t.black,
+		"--terminal-ansi-red": t.red,
+		"--terminal-ansi-green": t.green,
+		"--terminal-ansi-yellow": t.yellow,
+		"--terminal-ansi-blue": t.blue,
+		"--terminal-ansi-magenta": t.magenta,
+		"--terminal-ansi-cyan": t.cyan,
+		"--terminal-ansi-white": t.white,
+		"--terminal-ansi-bright-black": t.brightBlack,
+		"--terminal-ansi-bright-red": t.brightRed,
+		"--terminal-ansi-bright-green": t.brightGreen,
+		"--terminal-ansi-bright-yellow": t.brightYellow,
+		"--terminal-ansi-bright-blue": t.brightBlue,
+		"--terminal-ansi-bright-magenta": t.brightMagenta,
+		"--terminal-ansi-bright-cyan": t.brightCyan,
+		"--terminal-ansi-bright-white": t.brightWhite
+	};
+}
+/**
+* The `--terminal-*` properties of a variant: the palette a terminal paints.
+*
+* What a pinned terminal theme writes over the interface variant's own. The names
+* are the ones {@link themeCssVariablesWith} writes, and a custom variant's verbatim
+* `tokens` still win, so they can never drift from what the interface variant would
+* have written for the same palette. Built from the terminal palette alone: it needs
+* neither the catalogue nor the rest of the variant's roles.
+*/
+function terminalCssVariables(theme) {
+	const properties = terminalVariables(theme.terminal);
+	if (!theme.tokens) return properties;
+	for (const [name, value] of Object.entries(theme.tokens)) if (name.startsWith("--terminal-")) properties[name] = value;
+	return properties;
+}
+/**
+* Token values with every `oklch()` colour written as `#rrggbb`.
+*
+* For a host whose stylesheet, tests or native shell speak hex: the catalogue's
+* roles are `oklch()` strings, and this is the one conversion, gamut-mapped by the
+* catalogue's own `oklchToHex`. A value that is already hex, carries alpha
+* (`rgba()`), or is not a plain colour (`color-mix()`, `var()`) is left byte for
+* byte, because converting would either lose the alpha or be a guess. Suitable as
+* `ThemeProvider`'s `transformTokens`.
+*/
+function tokensAsHex(tokens) {
+	const converted = {};
+	for (const [name, value] of Object.entries(tokens)) {
+		const trimmed = value.trim();
+		const parsed = trimmed.startsWith("oklch(") && !trimmed.includes("/") ? parseColor(trimmed) : void 0;
+		converted[name] = parsed ? oklchToHex(parsed) : value;
+	}
+	return converted;
+}
+//#endregion
+export { terminalCssVariables, themeCssVariablesWith, tokensAsHex };
+
+//# sourceMappingURL=theme-css.js.map

package/dist/lib/theme-css.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"theme-css.js","names":[],"sources":["../../src/lib/theme-css.ts"],"sourcesContent":["/**\n * The mapping from a variant's roles to this system's custom properties, without the\n * catalogue.\n *\n * `themeCssVariables` needs two things only the catalogue can measure for a theme:\n * the strength of its `--primary-subtle` tint and its floor-projected editor ramp.\n * Those are the `hooks`, so this module imports no catalogue data and a host that\n * never loads the catalogue can still paint a variant it already holds. `lib/themes`\n * binds the hooks to the catalogue and keeps exporting the same\n * `themeCssVariables`; `lib/theme-engine` binds them to the precomputed default pair.\n */\nimport { primaryHover } from '@adea-ai/themes'\nimport { oklchToHex, parseColor } from '@adea-ai/themes/oklch'\nimport type {\n  EditorRolesMode,\n  ThemeCssVariableOptions,\n  ThemeEditorPalette,\n  ThemeVariant,\n} from './themes'\n\n/** What a variant's custom properties need that depends on the catalogue. */\nexport type ThemeCssHooks = {\n  /** The `--primary-subtle` expression of a variant. */\n  primarySubtle(theme: Pick<ThemeVariant, 'id' | 'appearance'>): string\n  /** The editor ramp of a variant under a projection. */\n  editor(theme: ThemeVariant, mode: EditorRolesMode): ThemeEditorPalette\n}\n\n/**\n * The roles a variant sets, as CSS custom properties.\n *\n * The one place that knows the mapping from a theme's roles to this system's variable\n * names. A provider applies this; nothing else repeats it. The `--terminal-*` and\n * `--editor-*` ramps are presentations of the catalogue's ANSI and syntax data rather\n * than separate roles, which is why they are built here and not in the catalogue.\n *\n * `options.editor` picks the `--editor-*` projection ({@link EditorRolesMode}).\n * Absent it, the result is what it has always been; the generated `theme-variants.css`\n * and the design-system artifact are built without it.\n */\nexport function themeCssVariablesWith(\n  hooks: ThemeCssHooks,\n  theme: ThemeVariant,\n  options: ThemeCssVariableOptions = {}\n): Record<string, string> {\n  const c = theme.colors\n  const t = theme.terminal\n  const e = hooks.editor(theme, options.editor ?? 'syntax')\n  const derived = {\n    '--background': c.background,\n    '--foreground': c.foreground,\n    '--card': c.card,\n    '--card-foreground': c.cardForeground,\n    '--popover': c.popover,\n    '--popover-foreground': c.popoverForeground,\n    '--primary': c.primary,\n    '--primary-foreground': c.primaryForeground,\n    /*\n     * The two tokens derived from the primary, and they are here rather than left to\n     * `theme.css` because they must follow `--primary` — which this function writes\n     * for *any* theme in the catalogue, not just the two defaults `theme.css` carries.\n     *\n     * `--primary-hover` is a resolved colour, not a `color-mix()`: a uniform hover\n     * step cannot be expressed as a mix (see `primaryHover`). Left out, a theme switch\n     * would keep the previous theme's hover on the new theme's primary.\n     *\n     * `--primary-subtle` is a mix over `--primary`, so it follows an accent on its\n     * own, but its *strength* is per theme: `primarySubtleCss(record)` lowers the\n     * appearance ceiling only as far as this theme needs for body text to clear 4.5:1\n     * on the tint, over every surface, for every accent it offers. It has to be\n     * written per theme for that reason — the appearance-wide value is not legible on\n     * every palette.\n     */\n    '--primary-hover': primaryHover(c.primary, theme.appearance),\n    '--primary-subtle': hooks.primarySubtle(theme),\n    '--secondary': c.secondary,\n    '--secondary-foreground': c.secondaryForeground,\n    '--muted': c.muted,\n    '--muted-foreground': c.mutedForeground,\n    '--accent': c.accent,\n    '--accent-foreground': c.accentForeground,\n    '--destructive': c.destructive,\n    '--destructive-foreground': c.destructiveForeground,\n    '--destructive-subtle': c.destructiveSubtle,\n    '--destructive-action': c.destructiveAction,\n    '--destructive-action-foreground': c.destructiveActionForeground,\n    '--success': c.success,\n    '--success-foreground': c.successForeground,\n    '--success-subtle': c.successSubtle,\n    '--warning': c.warning,\n    '--warning-foreground': c.warningForeground,\n    '--warning-subtle': c.warningSubtle,\n    '--info': c.info,\n    '--info-foreground': c.infoForeground,\n    '--info-subtle': c.infoSubtle,\n    '--border': c.border,\n    '--input': c.input,\n    '--ring': c.ring,\n    '--sidebar': c.sidebar,\n    '--sidebar-foreground': c.sidebarForeground,\n    '--sidebar-accent': c.sidebarAccent,\n    '--sidebar-border': c.sidebarBorder,\n    '--sidebar-primary': c.primary,\n    '--sidebar-primary-foreground': c.primaryForeground,\n    '--sidebar-ring': c.ring,\n    '--sidebar-muted-foreground': c.sidebarMutedForeground,\n    '--surface-sunken': c.muted,\n    '--surface-hover': c.accent,\n    '--surface-active': c.border,\n    '--chrome': c.background,\n    ...terminalVariables(t),\n    '--editor-keyword': e.keyword,\n    '--editor-string': e.string,\n    '--editor-number': e.number,\n    '--editor-comment': e.comment,\n    '--editor-function': e.function,\n    '--editor-variable': e.variable,\n    '--editor-type': e.type,\n    '--editor-tag': e.tag,\n    '--editor-attribute': e.attribute,\n    '--editor-operator': e.operator,\n    '--editor-heading': e.heading,\n    '--editor-link': e.link,\n    '--editor-diff-add': e.diffAdd,\n    '--editor-diff-delete': e.diffDelete,\n    '--editor-diff-hunk': e.diffHunk,\n    '--editor-search-match': e.searchMatch,\n    '--chart-1': theme.chart[0] ?? c.primary,\n    '--chart-2': theme.chart[1] ?? c.info,\n    '--chart-3': theme.chart[2] ?? c.success,\n    '--chart-4': theme.chart[3] ?? c.warning,\n    '--chart-5': theme.chart[4] ?? c.destructive,\n    '--chart-6': theme.chart[5] ?? c.mutedForeground,\n  }\n  return theme.tokens ? { ...derived, ...theme.tokens } : derived\n}\n\nfunction terminalVariables(t: ThemeVariant['terminal']): Record<string, string> {\n  return {\n    '--terminal-background': t.background,\n    '--terminal-foreground': t.foreground,\n    '--terminal-cursor': t.cursor,\n    '--terminal-selection': t.selection,\n    '--terminal-ansi-black': t.black,\n    '--terminal-ansi-red': t.red,\n    '--terminal-ansi-green': t.green,\n    '--terminal-ansi-yellow': t.yellow,\n    '--terminal-ansi-blue': t.blue,\n    '--terminal-ansi-magenta': t.magenta,\n    '--terminal-ansi-cyan': t.cyan,\n    '--terminal-ansi-white': t.white,\n    '--terminal-ansi-bright-black': t.brightBlack,\n    '--terminal-ansi-bright-red': t.brightRed,\n    '--terminal-ansi-bright-green': t.brightGreen,\n    '--terminal-ansi-bright-yellow': t.brightYellow,\n    '--terminal-ansi-bright-blue': t.brightBlue,\n    '--terminal-ansi-bright-magenta': t.brightMagenta,\n    '--terminal-ansi-bright-cyan': t.brightCyan,\n    '--terminal-ansi-bright-white': t.brightWhite,\n  }\n}\n\n/**\n * The `--terminal-*` properties of a variant: the palette a terminal paints.\n *\n * What a pinned terminal theme writes over the interface variant's own. The names\n * are the ones {@link themeCssVariablesWith} writes, and a custom variant's verbatim\n * `tokens` still win, so they can never drift from what the interface variant would\n * have written for the same palette. Built from the terminal palette alone: it needs\n * neither the catalogue nor the rest of the variant's roles.\n */\nexport function terminalCssVariables(theme: ThemeVariant): Record<string, string> {\n  const properties = terminalVariables(theme.terminal)\n  if (!theme.tokens) return properties\n  for (const [name, value] of Object.entries(theme.tokens)) {\n    if (name.startsWith('--terminal-')) properties[name] = value\n  }\n  return properties\n}\n\n/**\n * Token values with every `oklch()` colour written as `#rrggbb`.\n *\n * For a host whose stylesheet, tests or native shell speak hex: the catalogue's\n * roles are `oklch()` strings, and this is the one conversion, gamut-mapped by the\n * catalogue's own `oklchToHex`. A value that is already hex, carries alpha\n * (`rgba()`), or is not a plain colour (`color-mix()`, `var()`) is left byte for\n * byte, because converting would either lose the alpha or be a guess. Suitable as\n * `ThemeProvider`'s `transformTokens`.\n */\nexport function tokensAsHex(tokens: Readonly<Record<string, string>>): Record<string, string> {\n  const converted: Record<string, string> = {}\n  for (const [name, value] of Object.entries(tokens)) {\n    const trimmed = value.trim()\n    // `parseOklch` discards alpha, so a translucent oklch() stays as written.\n    const opaque = trimmed.startsWith('oklch(') && !trimmed.includes('/')\n    const parsed = opaque ? parseColor(trimmed) : undefined\n    converted[name] = parsed ? oklchToHex(parsed) : value\n  }\n  return converted\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;AAwCA,SAAgB,sBACd,OACA,OACA,UAAmC,CAAC,GACZ;CACxB,MAAM,IAAI,MAAM;CAChB,MAAM,IAAI,MAAM;CAChB,MAAM,IAAI,MAAM,OAAO,OAAO,QAAQ,UAAU,QAAQ;CACxD,MAAM,UAAU;EACd,gBAAgB,EAAE;EAClB,gBAAgB,EAAE;EAClB,UAAU,EAAE;EACZ,qBAAqB,EAAE;EACvB,aAAa,EAAE;EACf,wBAAwB,EAAE;EAC1B,aAAa,EAAE;EACf,wBAAwB,EAAE;EAiB1B,mBAAmB,aAAa,EAAE,SAAS,MAAM,UAAU;EAC3D,oBAAoB,MAAM,cAAc,KAAK;EAC7C,eAAe,EAAE;EACjB,0BAA0B,EAAE;EAC5B,WAAW,EAAE;EACb,sBAAsB,EAAE;EACxB,YAAY,EAAE;EACd,uBAAuB,EAAE;EACzB,iBAAiB,EAAE;EACnB,4BAA4B,EAAE;EAC9B,wBAAwB,EAAE;EAC1B,wBAAwB,EAAE;EAC1B,mCAAmC,EAAE;EACrC,aAAa,EAAE;EACf,wBAAwB,EAAE;EAC1B,oBAAoB,EAAE;EACtB,aAAa,EAAE;EACf,wBAAwB,EAAE;EAC1B,oBAAoB,EAAE;EACtB,UAAU,EAAE;EACZ,qBAAqB,EAAE;EACvB,iBAAiB,EAAE;EACnB,YAAY,EAAE;EACd,WAAW,EAAE;EACb,UAAU,EAAE;EACZ,aAAa,EAAE;EACf,wBAAwB,EAAE;EAC1B,oBAAoB,EAAE;EACtB,oBAAoB,EAAE;EACtB,qBAAqB,EAAE;EACvB,gCAAgC,EAAE;EAClC,kBAAkB,EAAE;EACpB,8BAA8B,EAAE;EAChC,oBAAoB,EAAE;EACtB,mBAAmB,EAAE;EACrB,oBAAoB,EAAE;EACtB,YAAY,EAAE;EACd,GAAG,kBAAkB,CAAC;EACtB,oBAAoB,EAAE;EACtB,mBAAmB,EAAE;EACrB,mBAAmB,EAAE;EACrB,oBAAoB,EAAE;EACtB,qBAAqB,EAAE;EACvB,qBAAqB,EAAE;EACvB,iBAAiB,EAAE;EACnB,gBAAgB,EAAE;EAClB,sBAAsB,EAAE;EACxB,qBAAqB,EAAE;EACvB,oBAAoB,EAAE;EACtB,iBAAiB,EAAE;EACnB,qBAAqB,EAAE;EACvB,wBAAwB,EAAE;EAC1B,sBAAsB,EAAE;EACxB,yBAAyB,EAAE;EAC3B,aAAa,MAAM,MAAM,MAAM,EAAE;EACjC,aAAa,MAAM,MAAM,MAAM,EAAE;EACjC,aAAa,MAAM,MAAM,MAAM,EAAE;EACjC,aAAa,MAAM,MAAM,MAAM,EAAE;EACjC,aAAa,MAAM,MAAM,MAAM,EAAE;EACjC,aAAa,MAAM,MAAM,MAAM,EAAE;CACnC;CACA,OAAO,MAAM,SAAS;EAAE,GAAG;EAAS,GAAG,MAAM;CAAO,IAAI;AAC1D;AAEA,SAAS,kBAAkB,GAAqD;CAC9E,OAAO;EACL,yBAAyB,EAAE;EAC3B,yBAAyB,EAAE;EAC3B,qBAAqB,EAAE;EACvB,wBAAwB,EAAE;EAC1B,yBAAyB,EAAE;EAC3B,uBAAuB,EAAE;EACzB,yBAAyB,EAAE;EAC3B,0BAA0B,EAAE;EAC5B,wBAAwB,EAAE;EAC1B,2BAA2B,EAAE;EAC7B,wBAAwB,EAAE;EAC1B,yBAAyB,EAAE;EAC3B,gCAAgC,EAAE;EAClC,8BAA8B,EAAE;EAChC,gCAAgC,EAAE;EAClC,iCAAiC,EAAE;EACnC,+BAA+B,EAAE;EACjC,kCAAkC,EAAE;EACpC,+BAA+B,EAAE;EACjC,gCAAgC,EAAE;CACpC;AACF;;;;;;;;;;AAWA,SAAgB,qBAAqB,OAA6C;CAChF,MAAM,aAAa,kBAAkB,MAAM,QAAQ;CACnD,IAAI,CAAC,MAAM,QAAQ,OAAO;CAC1B,KAAK,MAAM,CAAC,MAAM,UAAU,OAAO,QAAQ,MAAM,MAAM,GACrD,IAAI,KAAK,WAAW,aAAa,GAAG,WAAW,QAAQ;CAEzD,OAAO;AACT;;;;;;;;;;;AAYA,SAAgB,YAAY,QAAkE;CAC5F,MAAM,YAAoC,CAAC;CAC3C,KAAK,MAAM,CAAC,MAAM,UAAU,OAAO,QAAQ,MAAM,GAAG;EAClD,MAAM,UAAU,MAAM,KAAK;EAG3B,MAAM,SADS,QAAQ,WAAW,QAAQ,KAAK,CAAC,QAAQ,SAAS,GAAG,IAC5C,WAAW,OAAO,IAAI,KAAA;EAC9C,UAAU,QAAQ,SAAS,WAAW,MAAM,IAAI;CAClD;CACA,OAAO;AACT"}

package/dist/lib/theme-defaults.d.ts

@@ -0,0 +1,46 @@
+/**
+ * What a provider knows about the catalogue without loading it.
+ *
+ * The catalogue (`@adea-ai/themes`, 34 themes) is the heavy part of the theme
+ * system. Most hosts start on the default pair, paint a catalogue theme from a
+ * stylesheet, and open a picker rarely, so this module holds the few facts needed
+ * to start without it: the default ids, every catalogue id with its appearance (to
+ * recognise a stored preference), and the default pair as complete variants.
+ *
+ * It imports no catalogue code and no catalogue data. The facts themselves are in
+ * `theme-defaults.generated.ts`, copied from the catalogue by
+ * `scripts/build-theme-defaults.ts` and checked against it by
+ * `tests/theme-defaults.test.ts`.
+ */
+import type { ThemeAppearance, ThemeVariant } from './themes';
+import { DEFAULT_VARIANTS } from './theme-defaults.generated';
+export { DEFAULT_FLOOR_EDITOR, DEFAULT_PRIMARY_SUBTLE, DEFAULT_THEME_ACCENTS, DEFAULT_VARIANTS, THEME_INDEX, } from './theme-defaults.generated';
+export declare const defaultLightThemeId = "adea-light";
+export declare const defaultDarkThemeId = "adea-dark";
+/** The appearance of a catalogue theme id, or `undefined` for an id the catalogue lacks. */
+export declare function catalogueThemeAppearance(id: string): ThemeAppearance | undefined;
+/** Whether the catalogue holds a theme with this id (loaded or not). */
+export declare function isCatalogueThemeId(id: string): boolean;
+/** Whether an id is one of the two default themes, whose data ships with the provider. */
+export declare function isDefaultThemeId(id: string): id is keyof typeof DEFAULT_VARIANTS;
+/** The default variant of an appearance. */
+export declare function defaultVariantFor(appearance: ThemeAppearance): ThemeVariant;
+/**
+ * The variant a stored id means, or the default of the same appearance.
+ *
+ * An id the registry does not hold — an imported theme that was deleted, a
+ * catalogue entry that was renamed — must still paint *something of the appearance
+ * being shown*. Falling back to whichever variant happens to be first in the
+ * registry painted a dark palette under a light `color-scheme` for a light id, so
+ * the fallback is the appearance's own default, then any variant of that
+ * appearance, then the registry's first entry only when it holds nothing else.
+ *
+ * `registry` is the builtin catalogue plus whatever extras the host supplies; the
+ * stored id is never rewritten, only resolved, so a host that keeps an unknown id
+ * keeps resolving it if the theme comes back.
+ *
+ * The fallback order is translated from Zeron's `ThemeRegistry::resolve` (MIT,
+ * Copyright (c) 2026 Wing); see NOTICE.
+ */
+export declare function resolveVariant(registry: readonly ThemeVariant[], id: string, appearance: ThemeAppearance): ThemeVariant;
+//# sourceMappingURL=theme-defaults.d.ts.map

package/dist/lib/theme-defaults.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"theme-defaults.d.ts","sourceRoot":"","sources":["../../src/lib/theme-defaults.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AACH,OAAO,KAAK,EAAE,eAAe,EAAE,YAAY,EAAE,MAAM,UAAU,CAAA;AAC7D,OAAO,EAAE,gBAAgB,EAAe,MAAM,4BAA4B,CAAA;AAE1E,OAAO,EACL,oBAAoB,EACpB,sBAAsB,EACtB,qBAAqB,EACrB,gBAAgB,EAChB,WAAW,GACZ,MAAM,4BAA4B,CAAA;AAEnC,eAAO,MAAM,mBAAmB,eAAe,CAAA;AAC/C,eAAO,MAAM,kBAAkB,cAAc,CAAA;AAE7C,4FAA4F;AAC5F,wBAAgB,wBAAwB,CAAC,EAAE,EAAE,MAAM,GAAG,eAAe,GAAG,SAAS,CAEhF;AAED,wEAAwE;AACxE,wBAAgB,kBAAkB,CAAC,EAAE,EAAE,MAAM,GAAG,OAAO,CAEtD;AAED,0FAA0F;AAC1F,wBAAgB,gBAAgB,CAAC,EAAE,EAAE,MAAM,GAAG,EAAE,IAAI,MAAM,OAAO,gBAAgB,CAEhF;AAED,4CAA4C;AAC5C,wBAAgB,iBAAiB,CAAC,UAAU,EAAE,eAAe,GAAG,YAAY,CAE3E;AAED;;;;;;;;;;;;;;;;GAgBG;AACH,wBAAgB,cAAc,CAC5B,QAAQ,EAAE,SAAS,YAAY,EAAE,EACjC,EAAE,EAAE,MAAM,EACV,UAAU,EAAE,eAAe,GAC1B,YAAY,CASd"}

package/dist/lib/theme-defaults.generated.d.ts

@@ -0,0 +1,13 @@
+import type { AccentPreset } from '@adea-ai/themes';
+import type { ThemeEditorPalette, ThemeVariant } from './themes';
+/** Every catalogue theme id and its appearance, in catalogue order. */
+export declare const THEME_INDEX: readonly (readonly [id: string, appearance: 'light' | 'dark'])[];
+/** The default light and dark themes, complete. */
+export declare const DEFAULT_VARIANTS: Readonly<Record<'adea-light' | 'adea-dark', ThemeVariant>>;
+/** The accents the default light/dark pair offers beside the presets. */
+export declare const DEFAULT_THEME_ACCENTS: readonly AccentPreset[];
+/** Each default's measured `--primary-subtle` expression. */
+export declare const DEFAULT_PRIMARY_SUBTLE: Readonly<Record<string, string>>;
+/** Each default's `--editor-*` ramp held to 4.5:1 on its canvas (`editorRoles: 'floor'`). */
+export declare const DEFAULT_FLOOR_EDITOR: Readonly<Record<string, ThemeEditorPalette>>;
+//# sourceMappingURL=theme-defaults.generated.d.ts.map

package/dist/lib/theme-defaults.generated.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"theme-defaults.generated.d.ts","sourceRoot":"","sources":["../../src/lib/theme-defaults.generated.ts"],"names":[],"mappings":"AAKA,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,iBAAiB,CAAA;AACnD,OAAO,KAAK,EAAE,kBAAkB,EAAE,YAAY,EAAE,MAAM,UAAU,CAAA;AAEhE,uEAAuE;AACvE,eAAO,MAAM,WAAW,EAAE,SAAS,CAAC,SAAS,CAAC,EAAE,EAAE,MAAM,EAAE,UAAU,EAAE,OAAO,GAAG,MAAM,CAAC,CAAC,EAmCvF,CAAA;AAED,mDAAmD;AACnD,eAAO,MAAM,gBAAgB,EAAE,QAAQ,CAAC,MAAM,CAAC,YAAY,GAAG,WAAW,EAAE,YAAY,CAAC,CAiMvF,CAAA;AAED,yEAAyE;AACzE,eAAO,MAAM,qBAAqB,EAAE,SAAS,YAAY,EA6BxD,CAAA;AAED,6DAA6D;AAC7D,eAAO,MAAM,sBAAsB,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAGnE,CAAA;AAED,6FAA6F;AAC7F,eAAO,MAAM,oBAAoB,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,kBAAkB,CAAC,CAqC7E,CAAA"}