@cueplusplus/ui 0.16.0 → 0.17.0

package/dist/system/_style-help-ink.js

@@ -0,0 +1,14 @@
+//#region src/system/_style-help-ink.ts
+/**
+* The help ink, for a site that reads it without the help size: a table's
+* caption and the breadcrumb's separator (plan V.2, P122, P128) —
+* `style-help-ink`, falling back to the `fg-subtle` both drew. The same class
+* `_style-help.ts`'s `HELP_INK` spells for a field's description, restated in
+* a module of its own so docgen does not publish `style-help-size` as a
+* token of a table or a breadcrumb.
+*
+* @internal Not part of the public API.
+*/
+const HELP_INK = "text-[color:var(--cue-style-help-ink,var(--cue-fg-subtle))]";
+//#endregion
+export { HELP_INK };

package/dist/system/_style-help.js

@@ -0,0 +1,29 @@
+//#region src/system/_style-help.ts
+/**
+* The size and ink of a field's helper text: the micro rung in `fg-subtle`,
+* until a style set says otherwise.
+*
+* Spec 2026-09-26-looks-fidelity §3.5, plan R1. `FieldDescription` and
+* `FieldError` each spelt `font-mono text-(length:--cue-text-micro)`, the
+* description in `fg-subtle` and the error in `danger`. Tender and Porcelain set
+* helper text a rung larger and a step darker (T55, P48), in the Look's label
+* face — so both lines now wear `LABEL_FACE` and read the size here, and the
+* description reads the ink. The error keeps `danger`: a Look's helper ink is
+* not a reason to quieten a validation message.
+*
+* | property  | reads             | fallback                  |
+* |-----------|-------------------|---------------------------|
+* | font-size | `style-help-size` | `var(--cue-text-micro)`   |
+* | color     | `style-help-ink`  | `var(--cue-fg-subtle)`    |
+*
+* **Both names are optional** (spec §3.0), declared on no `:root` and left at the
+* shared `[data-style]` reset by every shipped set, so each reader computes the
+* old class's value at the element.
+*
+* @internal Not part of the public API.
+*/
+const HELP_SIZE = "text-[length:var(--cue-style-help-size,var(--cue-text-micro))]";
+/** @see HELP_SIZE — the description's ink; `FieldError` keeps `text-danger`. */
+const HELP_INK = "text-[color:var(--cue-style-help-ink,var(--cue-fg-subtle))]";
+//#endregion
+export { HELP_INK, HELP_SIZE };

package/dist/system/_style-input-face.js

@@ -0,0 +1,34 @@
+//#region src/system/_style-input-face.ts
+/**
+* The face a typing surface wears: mono by default, the style set's choice
+* inside one.
+*
+* Spec 2026-09-26 (the label-voice brief). `forms/_chassis.ts`'s
+* `controlSurface` and `bareControlClasses` — the shared recessed-control
+* chassis a text field, a textarea, a number field, a combobox, a select
+* trigger and everything else a person types into all ride — spoke
+* `font-mono` before this existed, the same fact `_style-control-face.ts`
+* records for `Button`. What was missing was a way for a sans-voiced Look to
+* change the ONE surface that is neither a control nor a caption: text a
+* person types, which a face chosen per call site would not follow. So the
+* style set says it, through `--cue-style-input-face`, and this reads it.
+*
+* **The fallback is the old class, spelt out**, for the identical reason
+* `_style-control-face.ts` gives: `font-mono` compiles to
+* `font-family: var(--cue-font-mono)`, and `--cue-style-input-face` is
+* declared on no `:root`, so under no set this resolves to exactly what
+* `font-mono` resolved to, at the control itself. A call site that
+* deliberately keeps a typed value in mono regardless of the set — a hex
+* colour code, a DMX value, anything code-shaped rather than prose — restates
+* `font-mono` directly instead of importing this, exactly as `color-picker.tsx`
+* already did for its hex field before this axis existed.
+*
+* **Its own module**, for the reason `_style-control-face.ts` gives: one
+* reader per file, so `@repo/docgen` attributes exactly this token to exactly
+* the components that import it.
+*
+* @internal Not part of the public API.
+*/
+const INPUT_FACE = "font-[family-name:var(--cue-style-input-face,var(--cue-font-mono))]";
+//#endregion
+export { INPUT_FACE };

package/dist/system/_style-kbd.js

@@ -0,0 +1,46 @@
+//#region src/system/_style-kbd.ts
+/**
+* A key cap's rim and size: the box edge and the micro rung by default, the
+* style set's choice inside one.
+*
+* Spec 2026-09-26-looks-fidelity §3.6 (R2), F-16. `Kbd` spent `border-border`
+* and `text-(length:--cue-text-micro)`. Porcelain's `MenuShortcut` key caps
+* have no rim at all and sit at 0.75rem (coss.md, P55), which a set says as
+* `--cue-style-kbd-edge: transparent` and `--cue-style-chip-size: 0.75rem` —
+* the chip's size name, because `Kbd` is sized off `h-chip` to sit on a chip's
+* row, and a Look that retunes one retunes both. The border's width stays, so
+* a key cap keeps its box and its baseline in every Look.
+*
+* Both names are optional (spec §3.0, F-3): under no set, `console` and every
+* set that declines them each reader resolves to exactly what the class it
+* replaced resolved to, at the key cap itself.
+*
+* **Put {@link KBD_SIZE} before `leading-none` in the same `cn()`**, as
+* `_style-label-size.ts` explains: `tailwind-merge` drops a `leading-*` that a
+* later font-size follows.
+*
+* **Its own module**, apart from `_style-chip.ts` though it reads one of the
+* chip's names, because `@repo/docgen` credits every importer with every token
+* in a file, and `Kbd` reads none of the chip's other names.
+*
+* @internal Not part of the public API.
+*/
+const KBD_EDGE = "border-[color:var(--cue-style-kbd-edge,var(--cue-border))]";
+/** @see KBD_EDGE — the key cap's size: the chip's size name, the micro rung by default. */
+const KBD_SIZE = "text-[length:var(--cue-style-kbd-size,var(--cue-style-chip-size,var(--cue-text-micro)))]";
+/**
+* The key cap's own box (plan V.2, P55, P111): its height and minimum width
+* (`style-kbd-height`, the `chip-h` it shared with the chip), its inline
+* padding (`style-kbd-pad`, `space-2`) and its corner (`style-kbd-radius`, the
+* `rounded-control` corner). Porcelain's key caps are 20px, 4px in and
+* rounded at 0.4 of its control corner, while its chips are a phone-to-desktop
+* clamp — so the cap stopped riding the chip's `h-chip`.
+*
+* The size above reads `style-kbd-size` first for the same reason (P14):
+* Porcelain's chip text ramps from 14px on a phone to 12px on a desktop,
+* where its key caps stay 12px. It falls back through the chip's size, so a
+* Look that names only the chip's keeps its key caps beside it.
+*/
+const KBD_BOX = "h-[var(--cue-style-kbd-height,var(--cue-chip-h))] min-w-[var(--cue-style-kbd-height,var(--cue-chip-h))] px-[var(--cue-style-kbd-pad,var(--cue-space-2))] rounded-[var(--cue-style-kbd-radius,calc(var(--cue-radius-control)*var(--cue-radius-scale)))]";
+//#endregion
+export { KBD_BOX, KBD_EDGE, KBD_SIZE };

package/dist/system/_style-label-case.js

@@ -0,0 +1,36 @@
+//#region src/system/_style-label-case.ts
+/**
+* The `text-transform` a chassis caption wears: `uppercase` by default, the
+* style set's choice inside one.
+*
+* Spec 2026-09-26 (the label-voice brief). Every mono-uppercase chassis
+* caption spent a literal `uppercase` utility before this existed, and a face
+* changed to sans through {@link LABEL_FACE} alone still shouts — a sentence-
+* case label rendered in a sans face and still transformed to caps is a sans
+* label wearing the console's voice, not the source site's. So the two travel
+* together at every call site.
+*
+* **The fallback is the old class, spelt out.** `uppercase` compiles to
+* `text-transform: uppercase`, and `--cue-style-label-case` is declared on no
+* `:root` — deliberately, for the identical reason `_style-control-face.ts`
+* gives for its own name: a `:root` declaration would freeze the page's
+* choice into every nested font or theme island. So under no set this
+* resolves to exactly what `uppercase` resolved to, at the label itself; and
+* every shipped set but a sans-voiced one restates `uppercase`, which
+* `@cueplusplus/tokens` refuses to build otherwise for `console`.
+*
+* Written as a bare arbitrary property (`[text-transform:…]`) rather than a
+* named Tailwind utility because none of Tailwind's `uppercase` / `lowercase`
+* / `capitalize` / `normal-case` utilities take a dynamic value — the same
+* reason `_paint-*` readers reach for `[mask-image:…]` and `[background-*:…]`
+* instead of a utility that does not exist for a `var()`-driven keyword.
+*
+* **Its own module**, for the reason `_style-control-face.ts` gives: one
+* reader per file, so `@repo/docgen` attributes exactly this token to exactly
+* the components that import it.
+*
+* @internal Not part of the public API.
+*/
+const LABEL_CASE = "[text-transform:var(--cue-style-label-case,uppercase)]";
+//#endregion
+export { LABEL_CASE };

package/dist/system/_style-label-face.js

@@ -0,0 +1,32 @@
+//#region src/system/_style-label-face.ts
+/**
+* The face a chassis caption wears: mono by default, the style set's choice inside one.
+*
+* Spec 2026-09-26 (the label-voice brief). `FieldLabel`, `Eyebrow`, a table head,
+* a `Stat` label, a group or section heading and a dozen more chassis sites all
+* spoke `font-mono … uppercase` before this existed — the same fact
+* `_style-control-face.ts` records for `Button` and the `Tabs` trigger, one
+* layer over. What was missing was a way for a sans-voiced Look (stripe's,
+* replit's, coss's) to change a LABEL's face rather than only a control's, and
+* a face chosen per call site would not follow the Look. So the style set says
+* it, through `--cue-style-label-face`, and this reads it.
+*
+* Always paired with {@link LABEL_CASE}: a sans face still shouting in caps is
+* still the console's voice, not the source site's, so the two travel
+* together at every call site.
+*
+* **The fallback is the old class, spelt out**, for the identical reason
+* `_style-control-face.ts` gives: `font-mono` compiles to
+* `font-family: var(--cue-font-mono)`, and `--cue-style-label-face` is
+* declared on no `:root`, so under no set this resolves to exactly what
+* `font-mono` resolved to, at the label itself.
+*
+* **Its own module**, because `@repo/docgen` attributes a token to a component
+* by the file its class string lives in, following only `_`-prefixed imports.
+* One reader per file — see `_style-control-face.ts`'s note.
+*
+* @internal Not part of the public API.
+*/
+const LABEL_FACE = "font-[family-name:var(--cue-style-label-face,var(--cue-font-mono))]";
+//#endregion
+export { LABEL_FACE };

package/dist/system/_style-label-ink.js

@@ -0,0 +1,29 @@
+//#region src/system/_style-label-ink.ts
+/**
+* A chassis caption's ink: its own historic role by default, one shared ink
+* inside a style set that declares `--cue-style-label-ink`.
+*
+* Spec 2026-09-26-looks-fidelity §3.6 (R2). Two inks, both already on the
+* page: `FieldLabel`, a `SectionHeader` label and the `Checkbox` and `Switch`
+* labels spent `text-fg-muted`; a table head and a group row, a
+* `Sidebar.Section` label, a `Stat` label and a menu group label spent the
+* quieter `text-fg-subtle`. Tender and porcelain draw every caption in the
+* body ink (`var(--cue-fg)`), kiln in the muted one — one value a set says
+* once, which is why the name exists.
+*
+* **Optional, so each reader keeps its own fallback** (spec §3.0, F-3): under
+* no set, `console` and every set that declines the name this resolves to
+* exactly what `text-fg-muted` or `text-fg-subtle` resolved to, at the label
+* itself — so a nested theme island still repaints it.
+*
+* **Its own module**, for the reason `_style-control-face.ts` gives: one
+* token per file, so `@repo/docgen` credits exactly the components that read
+* the label ink with it.
+*
+* @internal Not part of the public API.
+*/
+const LABEL_INK = "text-[color:var(--cue-style-label-ink,var(--cue-fg-muted))]";
+/** @see LABEL_INK — for a reader that spent `text-fg-subtle` before this existed. */
+const LABEL_INK_SUBTLE = "text-[color:var(--cue-style-label-ink,var(--cue-fg-subtle))]";
+//#endregion
+export { LABEL_INK, LABEL_INK_SUBTLE };

package/dist/system/_style-label-leading.js

@@ -0,0 +1,14 @@
+//#region src/system/_style-label-leading.ts
+/**
+* A field label's leading (plan V.2, P10): `style-label-leading`, falling back
+* to the `leading-none` (`1`) the label drew. Porcelain's field label is 16px
+* on 14px type, a 1.143 leading.
+*
+* **Optional** (spec §3.0). Its own module because docgen attributes a token
+* to a component by the file its class string lives in.
+*
+* @internal Not part of the public API.
+*/
+const LABEL_LEADING = "leading-[var(--cue-style-label-leading,1)]";
+//#endregion
+export { LABEL_LEADING };

package/dist/system/_style-label-size.js

@@ -0,0 +1,36 @@
+//#region src/system/_style-label-size.ts
+/**
+* A chassis caption's size: its own historic rung by default, one shared size
+* inside a style set that declares `--cue-style-label-size`.
+*
+* Spec 2026-09-26-looks-fidelity §3.6 (R2). `FieldLabel`, a `SectionHeader`
+* label, a table head and a group row, a `Sidebar.Section` label and a menu
+* group label all spent `text-(length:--cue-text-label)`; the `Stat` label
+* alone spent `text-(length:--cue-text-micro)`. The four measured Looks set
+* their captions at one size (tender and porcelain 0.875rem, zine and kiln
+* 0.75rem), and a size chosen per call site would not follow the Look.
+*
+* **Optional, so each reader keeps its own fallback** (spec §3.0, F-3): the
+* name is emitted as `initial` on the shared `[data-style]` reset, so under no
+* set, `console` and every set that declines it this resolves to exactly what
+* the class it replaced resolved to, at the label itself — which is also what
+* keeps a `<Density>` island's rung reaching it.
+*
+* **Put it before any `leading-*` class in the same `cn()`.** `tailwind-merge`
+* reads a font-size utility as overriding an earlier line-height one (Tailwind's
+* named sizes carry a line-height), so `cn("leading-none", LABEL_SIZE)` drops
+* the `leading-none`. The class this replaced had the same rule; the order at
+* each call site is the order it already had.
+*
+* **Its own module**, for the reason `_style-control-face.ts` gives:
+* `@repo/docgen` attributes a token to a component by the file its class
+* string lives in, so a component that reads the label ink but not the label
+* size (`Checkbox`, `Switch`) is not credited with this one.
+*
+* @internal Not part of the public API.
+*/
+const LABEL_SIZE = "text-[length:var(--cue-style-label-size,var(--cue-text-label))]";
+/** @see LABEL_SIZE — for the `Stat` label, which read the micro rung before this existed. */
+const LABEL_SIZE_MICRO = "text-[length:var(--cue-style-label-size,var(--cue-text-micro))]";
+//#endregion
+export { LABEL_SIZE, LABEL_SIZE_MICRO };

package/dist/system/_style-label-tracking.js

@@ -0,0 +1,45 @@
+//#region src/system/_style-label-tracking.ts
+/**
+* A label's tracking: its own historic rung of the caps ladder by default, one
+* shared tracking inside a style set that declares it.
+*
+* Spec 2026-09-26 (the label-voice brief). Unlike {@link LABEL_FACE} and the
+* case reader beside it, this name is **optional**
+* (`@cueplusplus/tokens`' `STYLE_SET_OPTIONAL`), because its readers do not
+* share one fallback. `FieldLabel`, `Slider`, a calendar weekday and the
+* stepper trail all read `tracking-caps-tight`; `Eyebrow` alone reads
+* `tracking-caps-loose`; a table head, a `Stat` label, a group heading and
+* most of the rest read plain `tracking-caps` — three different values, each
+* already what that component renders today. A set that declines the name (as
+* every mono set does) leaves every reader at its own historic tier, which is
+* the no-op this axis promises; a set that declares one real value (`normal`,
+* for `tender`, `kiln` and `porcelain`) overrides every reader to that SAME
+* tracking at once, regardless of which tier it used to read — which is the
+* point under a sans, sentence-case voice: there is no caps rung left to
+* space out.
+*
+* Three exports, one token: each pairs `--cue-style-label-tracking` with the
+* one ladder rung that call site read before this existed, so a component
+* that switches to one of these keeps rendering its own historic value under
+* every set that declines the name — which today is every set but the three
+* sans ones.
+*
+* **Its own module**, for the reason `_style-control-face.ts` gives: one
+* reader per file, so `@repo/docgen` attributes exactly this token to exactly
+* the components that import it, regardless of which of the three exports a
+* given file reaches for.
+*
+* @internal Not part of the public API.
+*/
+const LABEL_TRACKING = "tracking-[var(--cue-style-label-tracking,var(--cue-tracking-caps))]";
+/** @see LABEL_TRACKING — for a reader that read `tracking-caps-tight` before this existed. */
+const LABEL_TRACKING_TIGHT = "tracking-[var(--cue-style-label-tracking,var(--cue-tracking-caps-tight))]";
+/** @see LABEL_TRACKING — for a reader that read `tracking-caps-loose` before this existed. */
+const LABEL_TRACKING_LOOSE = "tracking-[var(--cue-style-label-tracking,var(--cue-tracking-caps-loose))]";
+/**
+* {@link LABEL_TRACKING} for a caption that declared no tracking of its own
+* (plan V.2, K131): the label tracking, falling back to `inherit`.
+*/
+const LABEL_TRACKING_INHERIT = "tracking-[var(--cue-style-label-tracking,inherit)]";
+//#endregion
+export { LABEL_TRACKING, LABEL_TRACKING_INHERIT, LABEL_TRACKING_LOOSE, LABEL_TRACKING_TIGHT };

package/dist/system/_style-label-weight.js

@@ -0,0 +1,40 @@
+//#region src/system/_style-label-weight.ts
+/**
+* A chassis caption's weight: what it rendered before by default, one shared
+* weight inside a style set that declares `--cue-style-label-weight`.
+*
+* Spec 2026-09-26-looks-fidelity §3.6 (R2). Porcelain's captions, table heads,
+* group labels, tags and key caps are `font-medium` (coss.md §4); every other
+* Look's are regular. The label readers, `Chip` and `Kbd` read it.
+*
+* **Two fallbacks, because the sites declared two different things.** The
+* table head and the table group row are `<th>` cells, whose user-agent weight
+* is bold, and they spent `font-normal` to undo it: their reader falls back to
+* `400`, {@link LABEL_WEIGHT_NORMAL}. Every other reader declared no weight at
+* all and inherited its parent's, so its fallback is `inherit`,
+* {@link LABEL_WEIGHT} — the spec's `400` is what each of them computes on a
+* page, but a literal `400` would override the weight a `Kbd` or a `Chip`
+* inherits from a heavier parent today, which a fallback may not do (the R
+* lanes' rule: the fallback is the site's current value).
+*
+* **Written `font-[number:…]`, not as a bare `[font-weight:…]` property.** The
+* `number:` hint is what makes Tailwind emit `font-weight` (and not a family)
+* for a `var()`, and it is also what `tailwind-merge` reads as a font weight: a
+* caller's `className="font-medium"` replaces this class, as it replaced
+* `font-normal`. A bare `[font-weight:…]` would not merge, and Tailwind sorts
+* it AFTER every named `font-*` utility (measured: a named weight declares
+* `--tw-font-weight` too, and a rule with more declarations sorts first), so
+* the caller's weight would silently lose — against every `className` prop's
+* "merged over the defaults" contract.
+*
+* **Its own module**, for the reason `_style-control-face.ts` gives: one
+* token per file, so `@repo/docgen` credits `Chip` and `Kbd` with the label
+* weight and not with the label size or ink they do not read.
+*
+* @internal Not part of the public API.
+*/
+const LABEL_WEIGHT = "font-[number:var(--cue-style-label-weight,inherit)]";
+/** @see LABEL_WEIGHT — for a `<th>` reader that spent `font-normal` before this existed. */
+const LABEL_WEIGHT_NORMAL = "font-[number:var(--cue-style-label-weight,400)]";
+//#endregion
+export { LABEL_WEIGHT, LABEL_WEIGHT_NORMAL };

package/dist/system/_style-lede.js

@@ -0,0 +1,49 @@
+//#region src/system/_style-lede.ts
+/**
+* The `PageShell` subtitle's size and ink: the lede under a page title.
+*
+* Spec 2026-09-26-looks-fidelity §3.5 and §10.4, plan R1 and its Graphite
+* addition. The subtitle spelt `text-(length:--cue-text-ui) … text-fg-muted`.
+* It is a lede — the one sentence under a title, which three Looks set a rung
+* above their body copy (T2, Z43, P1) — so it reads `style-lede-size`; and a
+* lede's ink is `style-lede-ink`, which falls back to the prose ink, which falls
+* back to the old class. Two names for one colour because Graphite's docs body
+* reads in `fg` while its ledes stay muted (G5 against G74), and Kiln's ledes
+* read in `fg` with its prose (K49): so a set that names only the prose ink
+* moves the ledes with it, and one that also names the lede ink parts them.
+*
+* | property  | reads                                      | fallback               |
+* |-----------|--------------------------------------------|------------------------|
+* | font-size | `style-lede-size`                          | `var(--cue-text-ui)`   |
+* | color     | `style-lede-ink`, then `style-prose-ink`   | `var(--cue-fg-muted)`  |
+*
+* `style-lede-ink` enters the contract with Graphite's round (plan L5.1); until
+* it does, nothing declares it and the chain reads the prose ink, and nothing
+* declares that either — so under every shipped set the subtitle computes
+* `fg-muted`, as it did. The docs site's ledes size from `--docs-text-body`
+* instead and are the docs site's own readers (spec §5.2), not this constant.
+*
+* Two constants, not one, because the subtitle's `leading-*` sits between them:
+* `tailwind-merge` drops a `leading-*` that precedes a font size in one list.
+*
+* @internal Not part of the public API.
+*/
+const LEDE_SIZE = "text-[length:var(--cue-style-lede-size,var(--cue-text-ui))]";
+/** @see LEDE_SIZE — the lede's ink, through the prose ink to `fg-muted`. */
+const LEDE_INK = "text-[color:var(--cue-style-lede-ink,var(--cue-style-prose-ink,var(--cue-fg-muted)))]";
+/**
+* The lede's leading (plan V.2, T110, Z95, Z96, P1): `style-lede-leading`,
+* falling back to the `leading-ui` the subtitle drew. Three Looks set their
+* ledes on a leading of their own — Tender 1.4, Porcelain 1.5 and Zine a clamp
+* from 1.4 on a phone to 1.3333 on a desktop — none of which is their body's.
+*/
+const LEDE_LEADING = "leading-[var(--cue-style-lede-leading,var(--cue-leading-ui))]";
+/**
+* The lede's tracking (plan V.2, Z96): the prose tracking, which spec §3.5
+* already gives "the prose readers and ledes", falling back to `inherit` — the
+* subtitle declared none. Kiln (-0.02em) and Zine (-0.01em) declare it, so
+* their `PageShell` subtitles take their prose's tracking with this.
+*/
+const LEDE_TRACKING = "tracking-[var(--cue-style-prose-tracking,inherit)]";
+//#endregion
+export { LEDE_INK, LEDE_LEADING, LEDE_SIZE, LEDE_TRACKING };

package/dist/system/_style-link.js

@@ -0,0 +1,46 @@
+//#region src/system/_style-link.ts
+/**
+* `Link`'s ink, rule, offset, weight and hover ink, each a style-set name read
+* with the class it replaced as its fallback.
+*
+* Fidelity spec 2026-09-26 §3.7 (plan R3). Tender inks its links in the
+* accent, kiln its prose links in the focus colour; four Looks rule the
+* underline in the text's own colour rather than a hairline, tender draws it
+* 2px under rather than 4px, porcelain sets its links at 500, and kiln and
+* zine hover to an ink other than the accent. Each is the set's to say.
+*
+* **Every fallback is what the site rendered before this existed**, so under
+* no set, and under every set that declines a name, the reader is a no-op:
+* `fg` for the ink, `border` for the rule, `4px` for the offset, the
+* accent on hover, and `inherit` for the weight — the link set no weight, and
+* took its parent's.
+*
+* `INLINE_LINK_INK` falls back through `style-link-ink`, so a set that inks
+* every link (tender) inks the prose link too without saying so twice, and a
+* set that inks only prose links (kiln) leaves the plain link alone.
+*
+* **Its own module**, for the reason `_style-control-face.ts` gives:
+* `@repo/docgen` attributes every token a file spells to each component that
+* imports it. Only `layout/link.tsx` imports this.
+*
+* @internal Not part of the public API.
+*/
+/** Every link's ink: `fg`, or the set's `style-link-ink`. */
+const LINK_INK = "text-[color:var(--cue-style-link-ink,var(--cue-fg))]";
+/** The `underline` variant's ink: the set's `style-inline-link-ink`, else {@link LINK_INK}'s chain. */
+const INLINE_LINK_INK = "text-[color:var(--cue-style-inline-link-ink,var(--cue-style-link-ink,var(--cue-fg)))]";
+/** The underline's colour: `border`, or the set's `style-link-rule`. */
+const LINK_RULE = "decoration-[color:var(--cue-style-link-rule,var(--cue-border))]";
+/** The underline's offset: 4px, or the set's `style-link-offset`. */
+const LINK_OFFSET = "underline-offset-[var(--cue-style-link-offset,4px)]";
+/**
+* Every link's weight: its parent's, or the set's `style-link-weight`.
+* `font-[number:…]` rather than an arbitrary `[font-weight:…]`, so a caller's
+* `font-*` weight still replaces it through `twMerge` — `_style-control.ts`'s
+* `CONTROL_WEIGHT` says why.
+*/
+const LINK_WEIGHT = "font-[number:var(--cue-style-link-weight,inherit)]";
+/** Every link's hover ink: the accent, or the set's `style-hover-ink`. */
+const HOVER_INK = "hover:text-[color:var(--cue-style-hover-ink,var(--cue-accent))]";
+//#endregion
+export { HOVER_INK, INLINE_LINK_INK, LINK_INK, LINK_OFFSET, LINK_RULE, LINK_WEIGHT };

package/dist/system/_style-menu.js

@@ -0,0 +1,30 @@
+//#region src/system/_style-menu.ts
+/**
+* A menu row's resting ink and its highlight.
+*
+* Spec 2026-09-26-looks-fidelity §3.7 and §3.8 (plan R4). `menuItemClasses`
+* said `text-fg-muted` and `data-[highlighted]:bg-accent-soft`. A Look whose
+* menu rows are full-contrast (tender, porcelain) or whose highlight is a
+* faint neutral or none (porcelain, kiln) reads these names instead.
+*
+* **The fallbacks are the classes they replace**: `var(--cue-fg-muted)` —
+* spec §3.7 gives `style-quiet-ink` that fallback for a menu row — and
+* `var(--cue-accent-soft)`.
+*
+* **Its own module**, for the docgen reason `_style-nav-voice.ts` gives. It is
+* reached through `overlays/_surface.ts`, whose every importer docgen already
+* credits with the whole overlay recipe.
+*
+* @internal Not part of the public API.
+*/
+const MENU_ITEM_INK = "text-[color:var(--cue-style-quiet-ink,var(--cue-fg-muted))] data-[highlighted]:bg-[color:var(--cue-style-menu-highlight,var(--cue-accent-soft))]";
+/**
+* A menu row's corner (plan V.2, P112): `style-menu-item-radius`, falling back
+* to the `rounded-control` corner the row drew. Porcelain rounds its menu and
+* select rows at 0.6 of its control corner. A select's and a filterable list's
+* rows read the same name with a `0px` fallback (`_style-option.ts`), since
+* they drew no corner.
+*/
+const MENU_ITEM_RADIUS = "rounded-[var(--cue-style-menu-item-radius,calc(var(--cue-radius-control)*var(--cue-radius-scale)))]";
+//#endregion
+export { MENU_ITEM_INK, MENU_ITEM_RADIUS };

package/dist/system/_style-nav-item.js

@@ -0,0 +1,41 @@
+//#region src/system/_style-nav-item.ts
+/**
+* What a `Sidebar.Item` reads from the style set: its resting ink, and the
+* ground, ink and weight of the item that is the current page.
+*
+* Spec 2026-09-26-looks-fidelity §3.8 and §10.4 (plan R4 and its Graphite
+* addition). The item said `text-fg-muted` at rest and, as the current page, an
+* `accent-soft` ground under an `accent` ink. A Look whose sidebar is a softer
+* ink (porcelain), whose current page is inverted (kiln), tinted and medium
+* (porcelain) or marked by ink alone (graphite) reads these names instead.
+*
+* **Every fallback is the class it replaced**, for the reason
+* `_style-control-face.ts` gives: `var(--cue-fg-muted)`, `var(--cue-accent-soft)`
+* and `var(--cue-accent)`, and `400` for the weight, which the item inherited
+* and computed under every shipped set.
+*
+* **The active weight yields to a caller's own weight.** The item set no
+* weight in any state, so `<Sidebar.Item className="font-medium">` was 500
+* whether current or not. A `data-[active]:` weight is `(0,2,0)` and would
+* beat that class on the current item alone, so it is written
+* `[:where(&[data-active])]:` — the same state at zero specificity — and a
+* caller's weight class wins in both states again. The active ground and ink
+* replaced `data-[active]:` classes and keep their standing, as those did.
+*
+* **The active ground reads two names, the sidebar's own first.**
+* `style-selected-ground` is also the selected table row's ground
+* (`_style-selected.ts`), where `transparent` would leave a selection with no
+* mark at all; graphite's sidebar has no fill (G57). So the item reads
+* `style-nav-active-ground` and falls back through `style-selected-ground`,
+* which keeps kiln's and porcelain's values here, and the table reads
+* `style-selected-ground` alone (spec §10.4). `style-nav-active-ground`
+* entered the contract in the fidelity plan's L5.1, and `graphite` declares it
+* `transparent` (G57).
+*
+* **Its own module**, for the docgen reason `_style-nav-voice.ts` gives.
+*
+* @internal Not part of the public API.
+*/
+const NAV_ITEM = "text-[color:var(--cue-style-nav-ink,var(--cue-fg-muted))] data-[active]:bg-[color:var(--cue-style-nav-active-ground,var(--cue-style-selected-ground,var(--cue-accent-soft)))] data-[active]:text-[color:var(--cue-style-selected-ink,var(--cue-accent))] [:where(&[data-active])]:font-[number:var(--cue-style-selected-weight,400)]";
+//#endregion
+export { NAV_ITEM };

package/dist/system/_style-nav-voice.js

@@ -0,0 +1,43 @@
+//#region src/system/_style-nav-voice.ts
+/**
+* The voice a navigation link speaks in — face, case, tracking, size and
+* weight — each the style set's choice, each falling back to what its reader
+* rendered before this existed.
+*
+* Spec 2026-09-26-looks-fidelity §3.8 (plan R4). `AppBar.Link` and `Footer`'s
+* column both said `font-mono text-(length:--cue-text-ui)` and nothing more,
+* so a Look whose header links are sans (tender, kiln, porcelain), uppercase
+* and tracked (zine) or medium (porcelain) could only say so with a class at
+* every call site, which a Look does not follow.
+*
+* **The fallbacks are the old classes, spelt out**, for the reason
+* `_style-control-face.ts` gives: none of these names is declared on `:root`,
+* and every set that declines one resets it to `initial` on the shared
+* `[data-style]` block (spec §3.0), so a reader resolves its own fallback at
+* itself. `font-mono` compiled to `var(--cue-font-mono)` and
+* `text-(length:--cue-text-ui)` to `var(--cue-text-ui)`. Case, tracking and
+* weight were inherited, and computed `none`, `normal` and `400` at both
+* readers under every shipped set — spec §3.8's three fallbacks.
+*
+* **Weight is written `font-[number:…]`.** A bare `font-[var(…)]` is read as a
+* family (plan §R1), and the `number` label makes it a weight to Tailwind —
+* which emits exactly what `font-medium` emits, `--tw-font-weight` included —
+* and to `tailwind-merge`, so a caller's `className="font-medium"` replaces it
+* through `cn()`. Spelt as an arbitrary `[font-weight:…]` property it survived
+* the merge beside the caller's class and won the cascade, because Tailwind
+* emits it after `font-medium`: `<AppBar.Link className="font-medium">` drew
+* 400. Case is an arbitrary property for the reason `_style-label-case.ts`
+* gives — no case utility takes a value — and nothing merges it with a
+* caller's `uppercase`, but Tailwind emits it before `uppercase`,
+* `normal-case` and the rest, so the caller's case still wins the cascade.
+*
+* **Its own module**, because `@repo/docgen` credits a component with every
+* `--cue-*` in each `_`-prefixed file it imports (`_style-control-face.ts`'s
+* note). `Footer` reads this voice and none of `AppBar.Link`'s own names, which
+* live in `_style-app-bar.ts`.
+*
+* @internal Not part of the public API.
+*/
+const NAV_VOICE = "font-[family-name:var(--cue-style-nav-face,var(--cue-font-mono))] [text-transform:var(--cue-style-nav-case,none)] tracking-[var(--cue-style-nav-tracking,normal)] text-[length:var(--cue-style-nav-size,var(--cue-text-ui))] font-[number:var(--cue-style-nav-weight,400)]";
+//#endregion
+export { NAV_VOICE };

package/dist/system/_style-option.js

@@ -0,0 +1,42 @@
+//#region src/system/_style-option.ts
+/**
+* One row of a list a control opens: `Select`'s items and the filterable
+* lists' (`Combobox`, `Autocomplete`, `MultiSelect`, `TagsInput`).
+*
+* Plan V.2 (T112, P112, P127). The two shared one class string —
+* `text-fg-muted … data-[highlighted]:bg-accent-soft … data-[selected]:text-accent`
+* — which no Look could reach, so a select under Tender drew a lilac selected
+* row on a lilac highlight where the source draws navy on a 5% wash, and under
+* Porcelain a square muted row where the source draws a rounded `fg` one.
+*
+* | part            | reads                                         | fallback                     |
+* |-----------------|-----------------------------------------------|------------------------------|
+* | idle ink        | `style-option-ink`                            | `var(--cue-fg-muted)`        |
+* | highlight       | `style-menu-highlight`, as a menu row's does  | `var(--cue-accent-soft)`     |
+* | selected ink    | `style-option-selected-ink`                   | `var(--cue-accent)`          |
+* | idle weight     | `style-body-weight`, on an unselected row     | `inherit`                    |
+* | corner          | `style-menu-item-radius`                      | `0px`                        |
+*
+* **Its own two inks**, not `style-quiet-ink` and `style-selected-ink`. The
+* quiet ink is a ghost button's and a menu row's; Tender's is `fg`, and its
+* select rows measure a 55% share of `fg` into `fg-muted`. The selected ink is
+* the sidebar's active item's and a table's selected row's; Tender's option
+* ink is navy where its sidebar keeps the lilac accent. Porcelain's rows,
+* which do measure `fg`, declare the option ink as `var(--cue-fg)`.
+*
+* **The weight goes on the unselected row only**, at zero specificity
+* (`[:where(&:not([data-selected]))]:`): Tender's body copy is 300 and its
+* selected row keeps the 400 it inherits, and a caller's `font-*` class on a
+* row still beats both, as it beat nothing before.
+*
+* `data-[highlighted]:text-fg` stays a class: every Look's highlighted row is
+* `fg`. The weight is spelt out whole rather than composed from
+* `_style-body-weight.ts`: a variant prefixed onto an interpolated constant is
+* a class that appears in no source file, and a consumer's Tailwind, which
+* scans this package's build for candidates, would never generate it.
+*
+* @internal Not part of the public API.
+*/
+const OPTION_ROW = "rounded-[var(--cue-style-menu-item-radius,0px)] text-[color:var(--cue-style-option-ink,var(--cue-fg-muted))] [:where(&:not([data-selected]))]:font-[number:var(--cue-style-body-weight,inherit)] data-[highlighted]:bg-[color:var(--cue-style-menu-highlight,var(--cue-accent-soft))] data-[highlighted]:text-fg data-[selected]:text-[color:var(--cue-style-option-selected-ink,var(--cue-accent))]";
+//#endregion
+export { OPTION_ROW };