@danxbot/ui 15.33.4 → 15.35.0

package/dist/types/lib/preference-values.d.ts

@@ -0,0 +1,62 @@
+/**
+ * The vocabulary of the document-level display preferences, and the one way a
+ * value is written onto `<html>`.
+ *
+ * DX-4075: REACT-FREE ON PURPOSE. `preferences.ts` holds the hooks, so it imports
+ * React; `@danxbot/ui/pure` may not reach React (`pure-entry.test.ts`). The framed
+ * side of `SandboxedFrame` (`designFrameClient`) has to apply the host's
+ * appearance with the very same write the host used and accept exactly the same
+ * values, so the unions, the value lists and `applyPreference` live here, imported
+ * by both. Two copies would be two chances for the host and the frame to drift.
+ */
+/**
+ * Writes one preference onto `<html>` with document-wide motion suspended for
+ * the duration of the change.
+ *
+ * WHY THIS IS NOT JUST `setAttribute`. Colour transitions are a foundation in
+ * this system: every element has one. That is right for an interaction — a
+ * control easing as you hover it — and wrong for a preference, because
+ * switching theme changes the computed colour of EVERY element at once.
+ * Measured on this demo: 2,360 transitions started simultaneously and the page
+ * took **957ms** to settle, 1,560ms on the chat route, for a token whose
+ * duration is 110ms. A theme switch should be a cut, not a dissolve; what it
+ * actually looked like was the whole document struggling.
+ *
+ * `--motion-scale: 0` is how it is suspended, rather than a blanket
+ * `transition: none !important`. Every duration in the system is already
+ * pre-multiplied by that scalar, so zeroing it turns them all off through the
+ * layer that exists for the purpose, overrides nothing a component declared,
+ * and cannot be forgotten by a component author.
+ *
+ * THE FORCED READ IS LOAD-BEARING. Style is normally recalculated once, after
+ * this function has returned — by which time the attribute is gone and the
+ * durations are back. Reading a computed value flushes the recalculation
+ * synchronously, so the new colours are committed WHILE durations are still
+ * zero, and no transition is ever started. Delete that line and the suspension
+ * silently does nothing at all, which is why `audit:motion` measures the settle
+ * time rather than the presence of the attribute.
+ */
+export declare function applyPreference(attribute: string, value: string): void;
+export type Theme = "light" | "dark";
+export declare const THEMES: readonly ["light", "dark"];
+export type UiScale = "sm" | "md" | "lg";
+export declare const SCALES: readonly ["sm", "md", "lg"];
+/**
+ * `design` is the palette as drawn; `aa` raises every token to the 4.5:1 floor.
+ *
+ * Opt-IN, not enforced, because enforcing the floor everywhere flattens the
+ * hierarchy for everyone: de-emphasised text stops being de-emphasised, and in
+ * this palette light-theme tertiary collapsed onto the same ramp step as
+ * secondary. A floor is a floor — reachable in one click by anyone who needs
+ * it, not a target that drags the whole design up to meet it.
+ */
+export type ContrastPreference = "design" | "aa";
+export declare const CONTRAST: readonly ["design", "aa"];
+/**
+ * `system` is a real third state, not a synonym for "full": it means defer to
+ * the OS, which is what most people want and what the OS-level preference
+ * exists to express. Collapsing it into a boolean would make an app-level
+ * control that says "full" override a user who set reduced motion system-wide.
+ */
+export type MotionPreference = "system" | "full" | "reduced";
+export declare const MOTION: readonly ["system", "full", "reduced"];

package/dist/types/lib/preferences.d.ts

@@ -1,78 +1,19 @@
-/**
- * Document-level display preferences.
- *
- * All three of theme, size scale and motion work the same way: a value lives on
- * `<html data-*>`, CSS reads it, and localStorage remembers it. Writing that
- * three times would be three chances to diverge — so it is written once and
- * specialised below.
- *
- * WHY `<html>` AND NOT REACT CONTEXT: the value has to reach plain CSS, not
- * just components. Portalled content (dialogs, popovers, toasts) renders
- * outside the React tree that would hold the context, and a preference that
- * fails on exactly the overlay layers is worse than no preference at all.
- */
-/**
- * Writes one preference onto `<html>` with document-wide motion suspended for
- * the duration of the change.
- *
- * WHY THIS IS NOT JUST `setAttribute`. Colour transitions are a foundation in
- * this system: every element has one. That is right for an interaction — a
- * control easing as you hover it — and wrong for a preference, because
- * switching theme changes the computed colour of EVERY element at once.
- * Measured on this demo: 2,360 transitions started simultaneously and the page
- * took **957ms** to settle, 1,560ms on the chat route, for a token whose
- * duration is 110ms. A theme switch should be a cut, not a dissolve; what it
- * actually looked like was the whole document struggling.
- *
- * `--motion-scale: 0` is how it is suspended, rather than a blanket
- * `transition: none !important`. Every duration in the system is already
- * pre-multiplied by that scalar, so zeroing it turns them all off through the
- * layer that exists for the purpose, overrides nothing a component declared,
- * and cannot be forgotten by a component author.
- *
- * THE FORCED READ IS LOAD-BEARING. Style is normally recalculated once, after
- * this function has returned — by which time the attribute is gone and the
- * durations are back. Reading a computed value flushes the recalculation
- * synchronously, so the new colours are committed WHILE durations are still
- * zero, and no transition is ever started. Delete that line and the suspension
- * silently does nothing at all, which is why `audit:motion` measures the settle
- * time rather than the presence of the attribute.
- */
-export declare function applyPreference(attribute: string, value: string): void;
-export type Theme = "light" | "dark";
+import { type ContrastPreference, type MotionPreference, type Theme, type UiScale } from "./preference-values";
 export declare function useTheme(): {
     theme: Theme;
     setTheme: import("react").Dispatch<import("react").SetStateAction<Theme>>;
     toggle: () => void;
 };
-export type UiScale = "sm" | "md" | "lg";
 export declare function useUiScale(): {
     scale: UiScale;
     setScale: import("react").Dispatch<import("react").SetStateAction<UiScale>>;
     cycle: () => void;
 };
-/**
- * `design` is the palette as drawn; `aa` raises every token to the 4.5:1 floor.
- *
- * Opt-IN, not enforced, because enforcing the floor everywhere flattens the
- * hierarchy for everyone: de-emphasised text stops being de-emphasised, and in
- * this palette light-theme tertiary collapsed onto the same ramp step as
- * secondary. A floor is a floor — reachable in one click by anyone who needs
- * it, not a target that drags the whole design up to meet it.
- */
-export type ContrastPreference = "design" | "aa";
 export declare function useContrast(): {
     contrast: ContrastPreference;
     setContrast: import("react").Dispatch<import("react").SetStateAction<ContrastPreference>>;
     toggle: () => void;
 };
-/**
- * `system` is a real third state, not a synonym for "full": it means defer to
- * the OS, which is what most people want and what the OS-level preference
- * exists to express. Collapsing it into a boolean would make an app-level
- * control that says "full" override a user who set reduced motion system-wide.
- */
-export type MotionPreference = "system" | "full" | "reduced";
 export declare function useMotionPreference(): {
     motion: MotionPreference;
     setMotion: import("react").Dispatch<import("react").SetStateAction<MotionPreference>>;

package/dist/types/pure.d.ts

@@ -43,3 +43,5 @@ export { formatDate, parseDate, formatDateTime, parseDateTime, type FormatDateTi
 export { confidenceLevel, CONFIDENCE_LEVEL_LABELS, type ConfidenceLevel } from "./lib/confidence";
 export { CHART_SERIES_COUNT, CHART_SERIES_TOKENS, CHART_SEQUENTIAL_TOKEN, CHART_SEQUENTIAL_COLOR, chartSeriesColor, } from "./lib/chart-palette";
 export type { LegalBlock, LegalDocumentValue, LegalSection } from "./lib/legal-document";
+export { designFrameClient } from "./lib/design-frame/client";
+export { DESIGN_FRAME_APPEARANCE, DESIGN_FRAME_READY, DESIGN_FRAME_ERROR, DESIGN_FRAME_ERROR_MAX_LENGTH, type DesignFrameAppearance, type DesignFrameAppearanceMessage, type DesignFrameReadyMessage, type DesignFrameErrorMessage, type DesignFrameInboundMessage, } from "./lib/design-frame/protocol";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@danxbot/ui",
-  "version": "15.33.4",
+  "version": "15.35.0",
   "type": "module",
   "description": "Danxbot — a domain-agnostic React design system with motion as a first-class primitive.",
   "license": "MIT",