@cueplusplus/ui 0.18.1 → 0.19.0

package/dist/layout/sidebar.js

@@ -51,6 +51,91 @@ const LANDMARK_ELEMENTS = {
 	complementary: "aside"
 };
 /**
+* The navigation column: a `<nav>` on a hairline, with a collapse valve and a
+* scroller of its own.
+*
+* Width is an inline length rather than a class, because it is the one piece of
+* console geometry a user is expected to change and persist; the transition
+* between the two widths is CSS and switches off under `prefers-reduced-motion`.
+*
+* **The column scrolls, the rail does not.** Thirty rows of navigation is an
+* ordinary amount for a documentation site or a settings screen, and a column
+* that cannot scroll simply loses the last of them off the bottom of the frame.
+* So the sections go in an inner scroller and the root keeps the height — which
+* is also what saves {@link SidebarRail}: it is `absolute inset-y-0`, its
+* containing block is the root rather than the scroller, and an absolutely
+* positioned box whose containing block is outside a scroll container neither
+* scrolls with it nor is clipped by it. Put the scroller on the root instead
+* and the collapse rail slides away with the third screenful.
+*
+* @example
+* <Sidebar.Root aria-label="Main">
+*   <Sidebar.Section label="Console">
+*     <Sidebar.Item icon={Sliders} active>Patch</Sidebar.Item>
+*     <Sidebar.Item icon={List}>Cues</Sidebar.Item>
+*   </Sidebar.Section>
+*   <Sidebar.Rail />
+* </Sidebar.Root>
+*/
+const SidebarRoot = React.forwardRef(function SidebarRoot({ className, landmark = "navigation", collapsed: collapsedProp, defaultCollapsed = false, onCollapsedChange, width = "14rem", collapsedWidth = "3rem", style, children, ...elementProps }, ref) {
+	const Element = LANDMARK_ELEMENTS[landmark];
+	const [uncontrolled, setUncontrolled] = React.useState(defaultCollapsed);
+	const collapsed = collapsedProp ?? uncontrolled;
+	const toggle = React.useCallback(() => {
+		const next = !(collapsedProp ?? uncontrolled);
+		if (collapsedProp === void 0) setUncontrolled(next);
+		onCollapsedChange?.(next);
+	}, [
+		collapsedProp,
+		uncontrolled,
+		onCollapsedChange
+	]);
+	const context = React.useMemo(() => ({
+		collapsed,
+		toggle
+	}), [collapsed, toggle]);
+	return /* @__PURE__ */ jsx(SidebarContext.Provider, {
+		value: context,
+		children: /* @__PURE__ */ jsx(Element, {
+			ref,
+			"data-slot": "sidebar",
+			"data-collapsed": collapsed ? "" : void 0,
+			className: cn("group/sidebar relative flex h-full min-h-0 shrink-0 flex-col border-r border-border bg-surface-1 transition-[width] duration-150 ease-out motion-reduce:transition-none", "[counter-reset:cue-rail]", className),
+			style: {
+				width: collapsed ? collapsedWidth : width,
+				...style
+			},
+			...elementProps,
+			children: /* @__PURE__ */ jsx("div", {
+				"data-slot": "sidebar-scroller",
+				className: "flex min-h-0 flex-1 flex-col gap-(--cue-space-4) overflow-y-auto py-(--cue-space-4)",
+				children
+			})
+		})
+	});
+});
+/** One group of items, under an optional caption. */
+const SidebarSection = React.forwardRef(function SidebarSection({ className, label, children, ...elementProps }, ref) {
+	const { collapsed } = useSidebar();
+	return /* @__PURE__ */ jsxs("div", {
+		ref,
+		"data-slot": "sidebar-section",
+		className: cn("flex flex-col gap-(--cue-space-1) px-(--cue-space-2)", className),
+		...elementProps,
+		children: [label === void 0 || collapsed ? null : /* @__PURE__ */ jsx("div", {
+			"data-slot": "sidebar-section-label",
+			className: cn("flex h-control-sm items-center px-(--cue-space-2)", LABEL_SIZE, LABEL_INK_SUBTLE, LABEL_WEIGHT, LABEL_FACE, LABEL_TRACKING, LABEL_CASE),
+			children: label
+		}), children]
+	});
+});
+/**
+* A style set's numbered rail (structural Looks, spec 2026-10-02 §3.5): every item
+* counts, and draws its number before the icon only when the set derives
+* `style-rail-counter-content` — `none` unset, which generates no box at all.
+*/
+const RAIL_COUNTER = "[counter-increment:cue-rail] before:content-[var(--cue-style-rail-counter-content,none)] before:shrink-0 before:font-mono before:text-(length:--cue-text-label) before:text-fg-subtle";
+/**
 * The console's navigation column: sections of items, a scroller of its own,
 * and a rail that collapses the whole thing to icons.
 *
@@ -63,57 +148,8 @@ const LANDMARK_ELEMENTS = {
 * </Sidebar.Root>
 */
 const Sidebar = {
-	Root: React.forwardRef(function SidebarRoot({ className, landmark = "navigation", collapsed: collapsedProp, defaultCollapsed = false, onCollapsedChange, width = "14rem", collapsedWidth = "3rem", style, children, ...elementProps }, ref) {
-		const Element = LANDMARK_ELEMENTS[landmark];
-		const [uncontrolled, setUncontrolled] = React.useState(defaultCollapsed);
-		const collapsed = collapsedProp ?? uncontrolled;
-		const toggle = React.useCallback(() => {
-			const next = !(collapsedProp ?? uncontrolled);
-			if (collapsedProp === void 0) setUncontrolled(next);
-			onCollapsedChange?.(next);
-		}, [
-			collapsedProp,
-			uncontrolled,
-			onCollapsedChange
-		]);
-		const context = React.useMemo(() => ({
-			collapsed,
-			toggle
-		}), [collapsed, toggle]);
-		return /* @__PURE__ */ jsx(SidebarContext.Provider, {
-			value: context,
-			children: /* @__PURE__ */ jsx(Element, {
-				ref,
-				"data-slot": "sidebar",
-				"data-collapsed": collapsed ? "" : void 0,
-				className: cn("group/sidebar relative flex h-full min-h-0 shrink-0 flex-col border-r border-border bg-surface-1 transition-[width] duration-150 ease-out motion-reduce:transition-none", className),
-				style: {
-					width: collapsed ? collapsedWidth : width,
-					...style
-				},
-				...elementProps,
-				children: /* @__PURE__ */ jsx("div", {
-					"data-slot": "sidebar-scroller",
-					className: "flex min-h-0 flex-1 flex-col gap-(--cue-space-4) overflow-y-auto py-(--cue-space-4)",
-					children
-				})
-			})
-		});
-	}),
-	Section: React.forwardRef(function SidebarSection({ className, label, children, ...elementProps }, ref) {
-		const { collapsed } = useSidebar();
-		return /* @__PURE__ */ jsxs("div", {
-			ref,
-			"data-slot": "sidebar-section",
-			className: cn("flex flex-col gap-(--cue-space-1) px-(--cue-space-2)", className),
-			...elementProps,
-			children: [label === void 0 || collapsed ? null : /* @__PURE__ */ jsx("div", {
-				"data-slot": "sidebar-section-label",
-				className: cn("flex h-control-sm items-center px-(--cue-space-2)", LABEL_SIZE, LABEL_INK_SUBTLE, LABEL_WEIGHT, LABEL_FACE, LABEL_TRACKING, LABEL_CASE),
-				children: label
-			}), children]
-		});
-	}),
+	Root: SidebarRoot,
+	Section: SidebarSection,
 	Item: React.forwardRef(function SidebarItem({ className, icon: Icon, active = false, badge, render, type, children, ...elementProps }, ref) {
 		return useRender({
 			render,
@@ -125,7 +161,7 @@ const Sidebar = {
 				"data-slot": "sidebar-item",
 				"data-active": active ? "" : void 0,
 				"aria-current": active ? "page" : void 0,
-				className: cn(`relative flex h-control-md w-full cursor-pointer items-center gap-(--cue-space-3) rounded-control border-0 bg-transparent px-(--cue-space-3) text-left font-mono text-(length:--cue-text-ui) no-underline transition-colors duration-150 outline-none select-none hover:bg-surface-2 hover:text-fg ${FOCUS_RING_INSET} ${NAV_ITEM} disabled:pointer-events-none disabled:opacity-40`, className),
+				className: cn(`relative flex h-control-md w-full cursor-pointer items-center gap-(--cue-space-3) rounded-control border-0 bg-transparent px-(--cue-space-3) text-left font-mono text-(length:--cue-text-ui) no-underline transition-colors duration-150 outline-none select-none hover:bg-surface-2 hover:text-fg ${FOCUS_RING_INSET} ${NAV_ITEM} ${RAIL_COUNTER} disabled:pointer-events-none disabled:opacity-40`, className),
 				children: /* @__PURE__ */ jsxs(Fragment, { children: [
 					Icon === void 0 ? null : /* @__PURE__ */ jsx(Icon, {
 						"aria-hidden": "true",

package/dist/overlays/_surface.d.ts

@@ -117,9 +117,9 @@ declare const overlayFooterClasses = "flex items-center justify-end gap-(--cue-s
  * and the highlight are the style set's, with those as their defaults
  * (`_style-menu.ts`).
  */
-declare const menuItemClasses = "flex h-control-sm cursor-default items-center gap-(--cue-space-2) rounded-[var(--cue-style-menu-item-radius,calc(var(--cue-radius-control)*var(--cue-radius-scale)))] px-(--cue-space-3) font-[family-name:var(--cue-style-control-face,var(--cue-font-mono))] text-(length:--cue-text-ui) text-[color:var(--cue-style-quiet-ink,var(--cue-fg-muted))] data-[highlighted]:bg-[color:var(--cue-style-menu-highlight,var(--cue-accent-soft))] outline-none select-none data-[highlighted]:text-fg data-[disabled]:pointer-events-none data-[disabled]:opacity-[var(--cue-style-row-disabled-opacity,0.4)]";
+declare const menuItemClasses = "flex h-control-sm cursor-default items-center gap-(--cue-space-2) rounded-[var(--cue-style-menu-item-radius,calc(var(--cue-style-control-radius,var(--cue-radius-control))*var(--cue-radius-scale)))] px-(--cue-space-3) font-[family-name:var(--cue-style-control-face,var(--cue-font-mono))] text-(length:--cue-text-ui) text-[color:var(--cue-style-quiet-ink,var(--cue-fg-muted))] data-[highlighted]:bg-[color:var(--cue-style-menu-highlight,var(--cue-accent-soft))] outline-none select-none data-[highlighted]:text-fg data-[disabled]:pointer-events-none data-[disabled]:opacity-[var(--cue-style-row-disabled-opacity,0.4)]";
 /** The uppercase mono caption over a group of menu rows — by default. */
-declare const menuLabelClasses = "flex h-control-sm items-center px-(--cue-space-3) py-[var(--cue-style-group-label-pad,0px)] font-[family-name:var(--cue-style-label-face,var(--cue-font-mono))] text-[length:var(--cue-style-group-label-size,var(--cue-style-label-size,var(--cue-text-label)))] tracking-[var(--cue-style-label-tracking,var(--cue-tracking-caps))] text-[color:var(--cue-style-group-label-ink,var(--cue-style-label-ink,var(--cue-fg-subtle)))] font-[number:var(--cue-style-label-weight,inherit)] [text-transform:var(--cue-style-label-case,uppercase)] select-none";
+declare const menuLabelClasses = "flex h-control-sm items-center px-(--cue-space-3) py-[var(--cue-style-group-label-pad,0px)] font-[family-name:var(--cue-style-label-face,var(--cue-font-mono))] text-[length:var(--cue-style-group-label-size,var(--cue-style-label-size,var(--cue-text-label)))] tracking-[var(--cue-style-label-tracking,var(--cue-tracking-caps))] text-[color:var(--cue-style-group-label-ink,var(--cue-style-label-ink,var(--cue-fg-muted)))] font-[number:var(--cue-style-label-weight,inherit)] [text-transform:var(--cue-style-label-case,uppercase)] select-none";
 /** The hairline between menu groups. */
 declare const menuSeparatorClasses = "my-(--cue-space-1) mx-[var(--cue-style-menu-separator-inset,0px)] h-px bg-border";
 /** Padding of a menu popup — a single space unit so rows reach the rim. */

package/dist/primitives/button.d.ts

@@ -10,7 +10,7 @@ import { useRender } from "@base-ui/react/use-render";
  * A class concatenated onto it — by a template string, `clsx`, or that option —
  * does not replace the recipe's own; the two compete by the order Tailwind
  * emits them in, which is not a contract. The inline padding in particular is
- * a `px-[calc(…)]` reader of the style set's `style-control-pad`, and Tailwind
+ * a `px-[ calc(…) ]` reader of the style set's `style-control-pad`, and Tailwind
  * emits it after every numeric `px-*`, so a concatenated `px-2` no longer wins
  * the way it did over the `px-(--cue-space-*)` rung it replaced. To override a
  * class of the recipe, pass `className` to `Button` itself, which merges, or

package/dist/primitives/button.js

@@ -40,6 +40,25 @@ import { useRender } from "@base-ui/react/use-render";
 */
 const buttonChassis = `inline-flex select-none items-center justify-center ${CONTROL_GAP} whitespace-nowrap rounded-control ${CONTROL_FACE} ${CONTROL_WEIGHT} ${CONTROL_TRACKING} ${CONTROL_TRIM} ${CONTROL_CASE} transition-colors duration-150 outline-none ${FOCUS_RING_PAINT} focus-visible:outline-offset-[var(--cue-style-focus-offset,1px)] disabled:pointer-events-none ${DISABLED_OPACITY}`;
 /**
+* A style set's chevron cut (structural Looks, spec 2026-10-02 §3.3), for the tones
+* that are a filled shape: primary and danger always, secondary only where the set
+* fills its ground (the build derives `--cue-style-secondary-cut` as `none` for a set
+* whose secondary ground is `transparent`). Outline, ghost and danger-outline are
+* drawn by their edge or their ink, and a hollow cut is geometry this chassis does
+* not take on, so they keep the rectangle.
+*
+* The cut is a `clip-path` on the element: a filled tone's border is transparent,
+* so nothing is cut but fill and exterior glow. Two things give way, on purpose:
+* the glow outside a cut button is clipped (a set with a cut is worn with a pack
+* that has none), and under `:focus-visible` and in forced colours the clip is
+* removed, so the focus ring and the system border are never cut. The element stays
+* a rectangle throughout: hit area, ring, `render`, refs, sizing and keyboard.
+* Unset, the clip is `none` and the button renders exactly as before. The rules
+* live in `styles.css` (`.cue-cut`, `.cue-cut-secondary`): as arbitrary utilities
+* they were ~105 characters on every button a page renders.
+*/
+const CUT_FILLED = "cue-cut";
+/**
 * The shared colour vocabulary. `accent` is theme-controlled, so `primary`
 * reads as white-on-black in `cue` and cyan-on-near-black in `terminal` with no
 * per-theme branching here.
@@ -57,11 +76,11 @@ const buttonChassis = `inline-flex select-none items-center justify-center ${CON
 * @internal Not part of the public API; imported by `icon-button.tsx`.
 */
 const buttonTones = {
-	primary: `bg-accent-fill text-accent-fill-fg hover:bg-accent-fill-hover border border-transparent ${GLOW_CLASSES} ${DISABLED_TONES.primary}`,
-	secondary: `border ${SECONDARY_EDGE} ${SECONDARY_INK} hover:text-[color:var(--cue-style-secondary-hover-ink,var(--cue-fg))] hover:border-[color:var(--cue-style-secondary-hover-edge,var(--cue-border-strong))] ${SECONDARY_GROUND} hover:bg-[color:var(--cue-style-secondary-hover-ground,var(--cue-style-secondary-ground,var(--cue-surface-2)))] ${DISABLED_TONES.secondary}`,
+	primary: `bg-accent-fill [background-image:var(--cue-style-primary-fill,none)] text-accent-fill-fg hover:bg-accent-fill-hover hover:[background-image:none] disabled:[background-image:none] border border-transparent ${GLOW_CLASSES} ${CUT_FILLED} ${DISABLED_TONES.primary}`,
+	secondary: `border ${SECONDARY_EDGE} ${SECONDARY_INK} hover:text-[color:var(--cue-style-secondary-hover-ink,var(--cue-fg))] hover:border-[color:var(--cue-style-secondary-hover-edge,var(--cue-border-strong))] ${SECONDARY_GROUND} hover:bg-[color:var(--cue-style-secondary-hover-ground,var(--cue-style-secondary-ground,var(--cue-surface-2)))] cue-cut-secondary ${DISABLED_TONES.secondary}`,
 	ghost: `${GHOST_INK} hover:text-fg hover:bg-surface-2 border border-transparent ${DISABLED_TONES.ghost}`,
 	outline: `border ${OUTLINE_EDGE} ${OUTLINE_INK} ${OUTLINE_HOVER_EDGE} hover:text-accent bg-transparent ${OUTLINE_HOVER_GROUND} ${REST_SHADE_CLASS} ${DISABLED_TONES.outline}`,
-	danger: `bg-danger text-danger-fg hover:opacity-90 border border-transparent ${GLOW_DANGER_CLASSES} ${DISABLED_TONES.danger}`,
+	danger: `bg-danger text-danger-fg hover:opacity-90 border border-transparent ${GLOW_DANGER_CLASSES} ${CUT_FILLED} ${DISABLED_TONES.danger}`,
 	"danger-outline": `border text-danger bg-transparent hover:bg-danger/10 border-danger/40 ${DISABLED_TONES["danger-outline"]}`
 };
 /**
@@ -72,7 +91,7 @@ const buttonTones = {
 * A class concatenated onto it — by a template string, `clsx`, or that option —
 * does not replace the recipe's own; the two compete by the order Tailwind
 * emits them in, which is not a contract. The inline padding in particular is
-* a `px-[calc(…)]` reader of the style set's `style-control-pad`, and Tailwind
+* a `px-[ calc(…) ]` reader of the style set's `style-control-pad`, and Tailwind
 * emits it after every numeric `px-*`, so a concatenated `px-2` no longer wins
 * the way it did over the `px-(--cue-space-*)` rung it replaced. To override a
 * class of the recipe, pass `className` to `Button` itself, which merges, or

package/dist/primitives/chip.d.ts

@@ -2,7 +2,7 @@ import { ClassProp, VariantProps } from "../lib/cva.js";
 import * as React from "react";
 //#region src/primitives/chip.d.ts
 declare const chipVariants: (props?: ({
-  tone?: "info" | "warn" | "danger" | "accent" | "ok" | "busy" | "neutral" | null | undefined;
+  tone?: "danger" | "info" | "warn" | "accent" | "ok" | "busy" | "neutral" | null | undefined;
   variant?: "outline" | "tinted" | "tag" | null | undefined;
   interactive?: boolean | null | undefined;
 } & ClassProp) | undefined) => string;

package/dist/primitives/chip.js

@@ -7,16 +7,72 @@ import { LABEL_FACE } from "../system/_style-label-face.js";
 import { LABEL_WEIGHT } from "../system/_style-label-weight.js";
 import * as React from "react";
 import { jsx } from "react/jsx-runtime";
+//#region src/primitives/chip.tsx
+/**
+* The tinted-chip recipe: `bg-<tone>/10 border-<tone>/35` and the tone's ink
+* (mixed toward `fg`, see `CHIP_TONE_INK`), and the
+* two quieter readings of it — `outline`, which drops the fill, and `tag`,
+* which drops the fill and the voice with it.
+*
+* Every property that varies is emitted from exactly one place: one rim, one
+* ink, one fill, one gutter, one type size, always. Emitting `bg-<tone>/10`
+* from the tone map and then cancelling it with `bg-transparent` would leave
+* two competing utilities in the class string, and `chipVariants` is exported —
+* a caller who uses it without `cn` gets a raw string where the winner is
+* decided by stylesheet order rather than by which utility was written last.
+* `h-chip h-4` proves the point at the other end: `tailwind-merge` cannot even
+* see that as a conflict, because `chip` is a token name and not a scale step.
+* So nothing here cancels anything. What varies moves into `variants` or
+* `compoundVariants` until only one of it is ever emitted.
+*
+* That is why `neutral` carries no rim of its own. The other six tones rim
+* themselves at `/35` in all three variants, but the neutral line has two
+* weights in this system: `--cue-border` is a box edge, and a chip is a box;
+* `--cue-hair-strong` is the rule between things, and a tag is a mark on the
+* page rather than a container. The rim is therefore a compound of tone and
+* variant, exactly as the fill is.
+*
+* **The recipe reads the style set** (spec 2026-09-26-looks-fidelity §3.6,
+* `system/_style-chip.ts`): the six tones' fill and rim are
+* `color-mix(in oklab, var(--cue-<tone>) var(--cue-style-chip-fill, 10%), transparent)`
+* and the same with `--cue-style-chip-edge` at `35%` — exactly `bg-<tone>/10`
+* and `border-<tone>/35` under no set, and a set's own shares inside one. The
+* case, tracking, radius, size and weight read `--cue-style-chip-case`,
+* `-tracking`, `-radius`, `-size` and `--cue-style-label-weight` the same way.
+*
+* @example
+* <span className={chipVariants({ tone: "danger", variant: "outline" })}>fault</span>
+* @example
+* <span className={chipVariants({ variant: "tag" })}>mcp</span>
+*/
+/**
+* A toned chip's ink: its tone, mixed 30% toward the page's own `fg`.
+*
+* A status ink is cut to be seen as a dot or a rim (3:1), and a chip sets it
+* as text: small, uppercase and on its own 10% tint, where the bare tone fell
+* to 4.2–4.4:1 in light under most themes and 3.6:1 under Kiln (structural
+* Looks §4.1's rendered sweep, phase 5). Mixing toward `fg` raises it in both
+* modes, because `fg` is the ink furthest from the ground in either, and
+* keeps the hue a reader reads the tone by.
+*/
+const CHIP_TONE_INK = {
+	accent: "text-[color:color-mix(in_oklch,var(--cue-accent)_70%,var(--cue-fg))]",
+	ok: "text-[color:color-mix(in_oklch,var(--cue-ok)_70%,var(--cue-fg))]",
+	busy: "text-[color:color-mix(in_oklch,var(--cue-busy)_70%,var(--cue-fg))]",
+	warn: "text-[color:color-mix(in_oklch,var(--cue-warn)_70%,var(--cue-fg))]",
+	danger: "text-[color:color-mix(in_oklch,var(--cue-danger)_70%,var(--cue-fg))]",
+	info: "text-[color:color-mix(in_oklch,var(--cue-info)_70%,var(--cue-fg))]"
+};
 const chipVariants = cva(`inline-flex ${CHIP_HEIGHT} select-none items-center justify-center ${CHIP_GAP} whitespace-nowrap ${CHIP_RADIUS} border ${LABEL_FACE} ${LABEL_WEIGHT} ${CHIP_CASE} outline-none ${FOCUS_RING}`, {
 	variants: {
 		tone: {
 			neutral: CHIP_INK_NEUTRAL,
-			accent: `${CHIP_EDGE.accent} text-accent`,
-			ok: `${CHIP_EDGE.ok} text-ok`,
-			busy: `${CHIP_EDGE.busy} text-busy`,
-			warn: `${CHIP_EDGE.warn} text-warn`,
-			danger: `${CHIP_EDGE.danger} text-danger`,
-			info: `${CHIP_EDGE.info} text-info`
+			accent: `${CHIP_EDGE.accent} ${CHIP_TONE_INK.accent}`,
+			ok: `${CHIP_EDGE.ok} ${CHIP_TONE_INK.ok}`,
+			busy: `${CHIP_EDGE.busy} ${CHIP_TONE_INK.busy}`,
+			warn: `${CHIP_EDGE.warn} ${CHIP_TONE_INK.warn}`,
+			danger: `${CHIP_EDGE.danger} ${CHIP_TONE_INK.danger}`,
+			info: `${CHIP_EDGE.info} ${CHIP_TONE_INK.info}`
 		},
 		variant: {
 			tinted: `${CHIP_PAD} ${CHIP_SIZE} ${CHIP_LEADING} ${CHIP_TRACKING}`,

package/dist/styles.css

@@ -95,3 +95,29 @@
     animation: none;
   }
 }
+
+/* A style set's chevron cut on filled buttons (structural Looks, spec 2026-10-02
+ * §3.3), as two bespoke classes for the plussie's reason and one more: written as
+ * Tailwind arbitrary properties it was some 105 characters on every button a page
+ * renders, and `/kitchen-sink`'s document grew 1.5% for it. Unset, the clip is
+ * `none` and nothing changes. Focus and forced colours drop the clip, so the ring
+ * and the system border are never cut; unlayered, so a utility cannot undo it. */
+.cue-cut {
+  clip-path: var(--cue-style-control-cut-clip, none);
+}
+
+.cue-cut-secondary {
+  clip-path: var(--cue-style-secondary-cut, none);
+}
+
+.cue-cut:focus-visible,
+.cue-cut-secondary:focus-visible {
+  clip-path: none;
+}
+
+@media (forced-colors: active) {
+  .cue-cut,
+  .cue-cut-secondary {
+    clip-path: none;
+  }
+}

package/dist/system/_paint-glass.js

@@ -5,7 +5,7 @@
 * **Why this writes `--tw-backdrop-blur` instead of `backdrop-filter`.** Spec
 * §13.5, decided on measurements. Tailwind composes every backdrop utility into
 * ONE declaration — `backdrop-filter: var(--tw-backdrop-blur,)
-* var(--tw-backdrop-brightness,) …` — so a raw `[backdrop-filter:var(…)]` here
+* var(--tw-backdrop-brightness,) …` — so a raw `[backdrop-filter: var(…)]` here
 * is a second, competing declaration. Measured: a consumer passing
 * `backdrop-brightness-50` through `className` then computes
 * `brightness(0.5)` and **no blur at all**. The glass does not narrow, it

package/dist/system/_paint-glow.js

@@ -27,7 +27,7 @@
 * adoption additive. The `outline` tone does carry one — `REST_SHADE_CLASS`,
 * the resting shade (fidelity plan R3) — so it must not also take
 * `GLOW_CLASSES`: one of the two would be dropped in silence. A halo there
-* would compose both into one `shadow-[…]` list instead.
+* would compose both into one `shadow-[ … ]` list instead.
 *
 * @internal Not part of the public API.
 */

package/dist/system/_scoped-pairing.js

@@ -0,0 +1,18 @@
+import * as React from "react";
+//#region src/system/_scoped-pairing.ts
+/**
+* Whether the subtree's pairing is a scope's own rather than the root's.
+*
+* A portal mounts on `<body>`, whose `font-family` was computed from the root's
+* pairing, and a computed family does not follow a token. So a portal opened
+* under a scope that names a pairing asks for the family again
+* (`portal.tsx`), and one opened anywhere else leaves it alone. Set by
+* `StageScope` (`_stage-scope.tsx`) for `Preview` and `FontScope`. Its own
+* module, with nothing but React behind it, so the portal can read it without
+* importing the provider it is stamped from.
+*
+* @internal Not part of the public API.
+*/
+const ScopedPairingContext = React.createContext(false);
+//#endregion
+export { ScopedPairingContext };

package/dist/system/_stage-scope.js

@@ -0,0 +1,199 @@
+"use client";
+import { usePublish, useRead } from "./published.js";
+import { AmbientThemeContext, DensityContext, PaintContext, RootAxesContext, StyleSetContext, rootAxes } from "./density.js";
+import { OverridesContext } from "./overrides.js";
+import { ScopedPairingContext } from "./_scoped-pairing.js";
+import { NO_PAIRING_SEED, PairingSeedContext, ThemeContext } from "./theme-provider.js";
+import * as React from "react";
+import { jsx } from "react/jsx-runtime";
+//#region src/system/_stage-scope.tsx
+/**
+* The attributes the stage carries — and, when nothing is asked, none at all.
+*
+* Inheriting is the *absence* of attributes, which is why every branch below
+* is conditional. Three branches add a second attribute, each for a reason in
+* the stylesheets rather than in taste.
+*
+* A theme's light block is the compound selector
+* `[data-theme="t"][data-mode="light"]`, so a mode with no theme restates the
+* page's theme on the same element. Read the other way, a theme with no mode
+* repeats the page's mode. Otherwise the stage would match the theme's dark
+* block under a light page, while every popup opened on it came up light:
+* popups are stamped from the context `StageScope` publishes, which carries
+* the page's mode.
+*
+* A theme's density overrides are addressed through `data-cue-theme`, the
+* stamp `<Density>` writes, so a density names the nearest theme the same way.
+*
+* A stage that ends up naming a theme and no rung — its own theme, or the
+* page's restated beside a mode (`scoped`, below) — restates the rung in force
+* around it, as `data-density` with the theme as `data-cue-theme` (spec
+* 2026-09-26-looks-fidelity §4.1.1). A theme's rung retunes are keyed on the
+* theme and the rung on one element, or a rung below the theme, so a stage that
+* re-themes with no `data-density` of its own inherits the rung already
+* resolved against the PAGE's theme, and its own theme's retune of that rung
+* never applies. `/looks` opens every stage this way: a theme and no rung. It
+* is what a nested `ThemeProvider` that names a theme already does — theme,
+* rung and mode together. The rung is the one `DensityContext` carries: `null`
+* outside every provider, where nothing is restated, and never `useDensity()`'s
+* `compact` fallback, which would invent one.
+*
+* The style set adds no second attribute, and that is the difference worth
+* writing down beside the three that do: a `[data-style]` block is a single
+* attribute selector naming no other axis, so a set stamped alone matches on
+* its own.
+*
+* But a stage that re-themes, re-modes or re-faces restates the set and the pack
+* in force around it (`around`), for a reason in custom properties rather than
+* in selectors. Their blocks declare names whose values read those axes — a
+* pack's stroke stops are the theme's borders, a set's band rule and ground are
+* the theme's border and surface — and a custom property's `var()`s are
+* substituted where it is declared. Declared only on the page, they arrive at
+* the stage already resolved against the page's theme and pairing; restated on
+* the stage, beside its own `data-theme` or `data-font`, they resolve against
+* those. A rung alone changes no ink and restates nothing. `around` is `null`
+* until the stage may restate: under a root that persists, not before the stage
+* has mounted, when the set and pack in force are the root's props rather than
+* the visitor's (see `useRestateReady`).
+*
+* The page's mode and rung, restated beside a stage theme — and the page's
+* theme, restated beside a stage mode or as a stage rung's `data-cue-theme` —
+* wait for the same mount on the same terms (tracking plan F13): under a
+* persisting root each is the root's, whose value on the server is its prop
+* while `<html>` carries the visitor's. So until then `followed` holds it back,
+* and `data-cue-follows` names it instead — the theme stylesheets' blocks each
+* have a twin keyed on `<html>`'s value and that marker (a followed rung
+* included: the base rung's twin in `axes.css`, and each theme's retune of it
+* keyed on the stage's own `data-theme`), and a rung node with no
+* `data-cue-theme` is reached by the rung rules' structural form, so the stage
+* paints the visitor's theme, mode and rung from the first frame (see
+* `useFollowedAxes`). A theme, mode or rung the stage names, or one named
+* between it and the root, is stamped as it always was. A followed rung takes
+* its `data-cue-theme` with it: the stamp addresses a `data-density` on the
+* same element, and there is none to address until the rung is stamped.
+*/
+function stageAttributes(asked, page, around, aroundDensity, followed) {
+	const attributes = {};
+	const scoped = asked.theme ?? (asked.mode === void 0 ? null : page?.theme ?? null);
+	if (scoped !== null && (asked.theme !== void 0 || !followed.theme)) attributes["data-theme"] = scoped;
+	const moded = asked.mode ?? (asked.theme === void 0 ? void 0 : page?.mode);
+	if (moded !== void 0 && !followed.mode) attributes["data-mode"] = moded;
+	if (asked.density !== void 0) {
+		attributes["data-density"] = asked.density;
+		const nearest = asked.theme ?? page?.theme ?? null;
+		if (nearest !== null && (asked.theme !== void 0 || !followed.theme)) attributes["data-cue-theme"] = nearest;
+	} else if (scoped !== null && aroundDensity !== null && !followed.density) {
+		attributes["data-density"] = aroundDensity;
+		if (asked.theme !== void 0 || !followed.theme) attributes["data-cue-theme"] = scoped;
+	}
+	if (followed.marker !== null) attributes["data-cue-follows"] = followed.marker;
+	if (asked.font !== void 0) attributes["data-font"] = asked.font;
+	if (asked.styleSet !== void 0) attributes["data-style"] = asked.styleSet;
+	if (asked.paint !== void 0) attributes["data-paint"] = asked.paint;
+	const restates = around !== null && (scoped !== null || moded !== void 0 || asked.font !== void 0);
+	if (restates && asked.styleSet === void 0 && around.styleSet !== null) attributes["data-style"] = around.styleSet;
+	if (restates && asked.paint === void 0 && around.paint !== null) attributes["data-paint"] = around.paint;
+	return attributes;
+}
+/**
+* The contexts the stage republishes, so an overlay opened on it follows it.
+*
+* `useCuePortalProps()` stamps a portal container from `ThemeContext` and
+* `DensityContext`; a popup mounts on `<body>` and inherits nothing from the
+* stage's DOM. So the stage's subtree reads a theme context with the stage's
+* theme and mode, and a density context with the stage's rung. The tools and
+* footer are outside this subtree, so what they open follows the page. A theme
+* the provider did not register leaves `manifest` null, which is what
+* `useTheme()` already reports for a name nobody registered.
+*
+* The style set travels with the density for the same reason and by the same
+* route: `useCuePortalProps()` stamps a portal container from `StyleSetContext`,
+* and a popup opened on the stage inherits nothing from the stage's DOM.
+*
+* And the pairing travels in the theme context, because that is where the
+* portal stamp reads `data-font` from (`theme?.font`). It used not to: the
+* stage stamped `data-font` on its own element and republished nothing, so a
+* popover opened on a `plex` stage came up in the root's pairing — a limit the
+* `font` prop's docblock stated rather than a rule anybody chose. A pairing on
+* the stage is the stage's, exactly as its theme is; `setFont` read here still
+* drives the root, because the pairing's setter has no island form.
+*/
+function StageScope({ theme, mode, density, font, styleSet, paint, children }) {
+	const outer = useRead(ThemeContext);
+	const outerOverrides = useRead(OverridesContext);
+	const outerDensity = useRead(DensityContext);
+	const outerAmbient = useRead(AmbientThemeContext);
+	const outerStyleSet = useRead(StyleSetContext);
+	const outerPaint = useRead(PaintContext);
+	const value = React.useMemo(() => {
+		if (outer === null || theme === void 0 && mode === void 0 && font === void 0) return outer;
+		const scoped = theme ?? outer.theme;
+		return {
+			...outer,
+			theme: scoped,
+			manifest: scoped === outer.theme ? outer.manifest : null,
+			mode: mode ?? outer.mode,
+			font: font ?? outer.font,
+			resolvedMode: mode === "dark" || mode === "light" ? mode : outer.resolvedMode
+		};
+	}, [
+		outer,
+		theme,
+		mode,
+		font
+	]);
+	const stamped = theme !== void 0 || mode !== void 0;
+	const inputs = [
+		theme,
+		mode,
+		density,
+		font,
+		styleSet,
+		paint,
+		React.useContext(ThemeContext),
+		React.useContext(OverridesContext),
+		React.useContext(DensityContext),
+		React.useContext(AmbientThemeContext),
+		React.useContext(StyleSetContext),
+		React.useContext(PaintContext)
+	];
+	const publishedAmbient = usePublish(theme ?? outerAmbient, inputs);
+	const publishedDensity = usePublish(density ?? outerDensity, inputs);
+	const publishedStyleSet = usePublish(styleSet ?? outerStyleSet, inputs);
+	const publishedPaint = usePublish(paint ?? outerPaint, inputs);
+	const publishedOverrides = usePublish(stamped ? null : outerOverrides, inputs);
+	const publishedValue = usePublish(value, inputs);
+	const outerPairingSeed = React.useContext(PairingSeedContext);
+	const outerScopedPairing = React.useContext(ScopedPairingContext);
+	const outerRootAxes = React.useContext(RootAxesContext);
+	return /* @__PURE__ */ jsx(RootAxesContext.Provider, {
+		value: rootAxes(outerRootAxes.theme && theme === void 0, outerRootAxes.mode && mode === void 0, outerRootAxes.density && density === void 0),
+		children: /* @__PURE__ */ jsx(AmbientThemeContext.Provider, {
+			value: publishedAmbient,
+			children: /* @__PURE__ */ jsx(DensityContext.Provider, {
+				value: publishedDensity,
+				children: /* @__PURE__ */ jsx(StyleSetContext.Provider, {
+					value: publishedStyleSet,
+					children: /* @__PURE__ */ jsx(PaintContext.Provider, {
+						value: publishedPaint,
+						children: /* @__PURE__ */ jsx(OverridesContext.Provider, {
+							value: publishedOverrides,
+							children: /* @__PURE__ */ jsx(PairingSeedContext.Provider, {
+								value: font === void 0 ? outerPairingSeed : NO_PAIRING_SEED,
+								children: /* @__PURE__ */ jsx(ScopedPairingContext.Provider, {
+									value: font !== void 0 || outerScopedPairing,
+									children: /* @__PURE__ */ jsx(ThemeContext.Provider, {
+										value: publishedValue,
+										children
+									})
+								})
+							})
+						})
+					})
+				})
+			})
+		})
+	});
+}
+//#endregion
+export { StageScope, stageAttributes };

package/dist/system/_storage.js

@@ -0,0 +1,25 @@
+//#region src/system/_storage.ts
+/**
+* The page's `localStorage`, or `null` where there is none this code may use.
+*
+* `typeof localStorage === "undefined"` is not a safe probe. In a document with
+* an opaque origin — a frame sandboxed without `allow-same-origin`, which is
+* what the studio's canvas is — the accessor on `window` throws a
+* `SecurityError` instead of answering `undefined`, and a `typeof` written
+* outside a `try` throws with it, before the `try` meant to absorb storage
+* failures is ever entered. The probe is taken inside one here, so every reader
+* and writer of a preference degrades to "nothing stored", the way a private
+* window's full quota already did.
+*
+* @returns The storage, or `null` on a server, under an opaque origin, or
+*   anywhere else reading the accessor throws.
+*/
+function localStore() {
+	try {
+		return typeof localStorage === "undefined" ? null : localStorage;
+	} catch {
+		return null;
+	}
+}
+//#endregion
+export { localStore };

package/dist/system/_style-accordion-rule.js

@@ -6,7 +6,7 @@
 * `Accordion.Item` draws the rule with `border-t`, which writes
 * `border-top-style: var(--tw-border-style)`, a slot Tailwind registers with
 * `inherits: false` and `initial-value: solid`, so the section fills that slot
-* rather than a raw `[border-top-style:…]` — the footer's reason
+* rather than a raw `[border-top-style: …]` — the footer's reason
 * (`_style-footer-rule.ts`): a caller's own `border-dotted` still wins. The
 * fallback is the slot's `solid`. stripe.com's accordion draws its rules 1px
 * dashed in the quiet border ink (`:where(.hds-accordion) .hds-details`), so

package/dist/system/_style-app-bar.js

@@ -27,7 +27,7 @@
 * **The hover ground yields to a caller's own ground.** It is the one
 * declaration here the link never had: `Link` sets no background in any state,
 * so `<AppBar.Link className="bg-surface-2">` kept its ground under the pointer.
-* A plain `hover:bg-[…]` is `(0,2,0)` and would paint over it; this is written
+* A plain `hover:bg-[ … ]` is `(0,2,0)` and would paint over it; this is written
 * `[@media(hover:hover)]:[:where(&:hover)]:`, which is `hover:` — the same
 * media query, the same state — at zero specificity, so any class a caller
 * passes for the ground still wins, hovered or not. The hover INK replaced
@@ -43,7 +43,7 @@
 * `@property` with `inherits: false` and `initial-value: solid` — which is the
 * solid rule the bar always drew. Filling that slot keeps the one declaration,
 * for the reason `_paint-glass.ts` fills `--tw-backdrop-blur`: a raw
-* `[border-bottom-style:…]` would be a second, competing declaration, and
+* `[border-bottom-style: …]` would be a second, competing declaration, and
 * Tailwind emits it after `border-dashed`, so it would beat a caller's own
 * `border-dotted`. Through the slot a caller's style class still wins, because
 * it writes `border-style` itself, after `border-b`. The fallback is the