@aceshooting/lyra-ui 7.2.0 → 7.4.0

package/llms/components/lr-sequence-strip.md

@@ -15,20 +15,24 @@
 
 A compact, one-thin-cell-per-item strip visualizing a sequence of categorical states, with an
 optional secondary per-cell marker. Pure CSS/flex — no chart.js, no SVG, no canvas — sized/named
-consistently with the sparkline/heatmap family, but a glanceable *aggregate* visualization
-(`role="img"`, one summarizing `aria-label`) rather than a `role="list"` of separately-operable
-items: there is no per-cell keyboard focus and no per-cell click event, matching `<lr-sparkline>`'s
-accessibility model rather than `<lr-heatmap>`'s heavier canvas-plus-keyboard-roving one. Hovering a
-cell (pointer only) shows `[part="tooltip"]` with that item's label. Setting `showLegend`
-additionally renders a static `[part="legend"]` key below the strip, so the color-to-category
-mapping is readable without hovering each cell.
+consistently with the sparkline/heatmap family, and read as a glanceable aggregate. `[part="base"]`
+is a labeled `role="list"` and each cell a named `role="listitem"` (`aria-label`, `aria-posinset`,
+`aria-setsize`), so the sequence is walkable item by item rather than collapsed into one summary
+string. Exactly one cell is tabbable at a time (roving `tabindex`); ArrowLeft/ArrowRight and
+Home/End move the stop — direction-aware, so the arrows swap under RTL — and focusing a cell shows
+the same `[part="tooltip"]` detail that pointer hover does, wired through `aria-describedby`. Cells
+are inspectable, not actionable: there is no per-cell click/activation event, so unlike
+`<lr-heatmap>` there is nothing to fire on Enter/Space. Setting `showLegend` additionally renders a
+static `[part="legend"]` key below the strip, so the color-to-category mapping is readable without
+visiting each cell.
 
 **Properties:**
 - `items: SequenceStripItem[] = []` (attribute: false) — `{ id, category, marker?, label? }`;
   `marker` renders a small bottom marker on that cell independent of the category color (e.g. a
-  subagent-dispatched turn); `label` is per-item hover-tooltip text, falling back to the matching
-  category's own `label` (or its `key`) when unset — not read by the auto-generated `aria-label`,
-  which summarizes by category/count only
+  subagent-dispatched turn); `label` is per-item hover/focus tooltip text *and* that cell's own
+  `role="listitem"` accessible name, falling back to the matching category's own `label` (or its
+  `key`) when unset — it is not read by `[part="base"]`'s auto-generated `aria-label`, which
+  summarizes by category/count only
 - `categories: SequenceStripCategory[] = []` (attribute: false) — `{ key, color, label? }`; `color`
   is the cell background for every item whose `category` matches `key` (an item whose `category`
   matches no entry renders `transparent`); `label` is used in the auto-generated `aria-label` summary
@@ -43,9 +47,9 @@ mapping is readable without hovering each cell.
   order. The key describes the *scheme*, not the current data: a category with no matching item
   still gets a row, and an item whose `category` matches no entry adds none. Deliberately
   non-interactive — it toggles nothing and emits nothing (`lr-graph-legend` is the interactive,
-  filtering legend). Because it only repeats the category names `[part="base"]` already announces
-  through its `role="img"` summary, the legend is `aria-hidden` — visible on screen, announced
-  exactly once — and it wraps onto further rows in a narrow allocation rather than overflowing
+  filtering legend). Because it only repeats the category names `[part="base"]`'s own `aria-label`
+  summary already announces, the legend is `aria-hidden` — visible on screen, announced exactly
+  once — and it wraps onto further rows in a narrow allocation rather than overflowing
 - `markerLabel?: string` (attribute `marker-label`) — names what an item's `marker` *means* (e.g.
   `"Subagent"`). Setting it does two things: with `showLegend` on it adds one trailing
   `[part="legend-item"]`, whose `[part="legend-marker-swatch"]` reproduces the cell's own marker
@@ -57,9 +61,10 @@ mapping is readable without hovering each cell.
 
 **Slots:** none.
 
-**CSS parts:** `base` (the root strip, `role="img"`), `cell` (each item's cell, background-colored
-by its category), `marker` (the small bottom marker on a cell whose item sets `marker: true`),
-`tooltip` (the hover tooltip showing the hovered item's label, hidden until a cell is hovered),
+**CSS parts:** `base` (the root strip, `role="list"`), `cell` (each item's `role="listitem"` cell,
+background-colored by its category and carrying the roving `tabindex`), `marker` (the small bottom
+marker on a cell whose item sets `marker: true`), `tooltip` (the detail tooltip showing the active
+item's label, hidden until a cell is hovered or focused),
 `legend` (the static category key rendered below the strip when `showLegend` is set — `aria-hidden`,
 as it repeats the strip's own `aria-label`), `legend-item` (one swatch + label pair, one per
 `categories` entry, plus one trailing marker row when `markerLabel` is set), `legend-swatch` (the

package/llms/components/lr-slider.md

@@ -51,6 +51,10 @@ pointerup for a drag, or on keyup for a keyboard step, so a single Arrow/Home/En
 fires both `lr-input` and `lr-change`, mirroring native `<input type=range>`'s own `change`-on-every-
 committed-step behavior)
 
+**Methods:** `focus(options?)`, `blur()`, and `click()` forward to the internal `[part="thumb"]`
+control — without them the host's own `focus()`/`blur()`/`click()` would be no-ops, because the
+`role="slider"` element they need to reach lives in the shadow root.
+
 **Slots:** none.
 
 **CSS parts:** `base` (row wrapping the track and optional value readout), `track`, `fill` (filled

package/llms/components/lr-split.md

@@ -6,7 +6,7 @@
 - **Class** `LyraSplit`, also available unregistered from `@aceshooting/lyra-ui/components/layout/split/split.class.js`
 - **Family** `components/layout/` — see `llms/index.md` for its siblings
 - **Optional peers** none
-- **Themeable via** 3 parts, 1 custom property — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 3 parts, 2 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -160,6 +160,14 @@ fired only when an enabled `orientationBreakpoint` actually changes `effectiveOr
 
 **Themeable custom properties:** `--lr-split-overlay-color` (default `var(--lr-color-overlay)`) —
 the `'floating'` drawer's `[part='backdrop']` scrim; scoped to `[part='base']`, not the viewport.
+`--lr-split-divider-hit-slop` (default `calc((var(--lr-size-3px) - var(--lr-icon-button-size)) / 2)`,
+i.e. `-18.5px` at the shipped token values) — the per-side inset of `[part='divider']`'s invisible
+`::before` hit area along the resize axis. It is negative on purpose: the `::before` box extends past
+the divider's own edges so the *effective* pointer/touch target reaches the shared
+`--lr-icon-button-size` WCAG 2.5.8 floor (40px) while the divider anyone can see stays 3px. Unlike
+most properties here it is **declared on `:host`**, so an override has to target the element itself —
+an ancestor rule is shadowed. Overriding it directly is rarely the right move: retheme
+`--lr-size-3px` or `--lr-icon-button-size` and the slop recomputes to keep exactly closing the gap.
 Otherwise shared tokens only.
 
 **Optional peer deps:** none.

package/llms/components/lr-stepper.md

@@ -58,6 +58,10 @@ decides whether/how `steps` changes in response.
   identically-named contract.
 - `narrowOrientation: 'horizontal' | 'vertical' = 'vertical'` (reflected, attribute
   `narrow-orientation`)
+- `wrapLabels: boolean = false` (reflected, attribute `wrap-labels`) — when true, allows long
+  labels to wrap when the effective orientation is vertical. The default preserves single-line
+  labels, and horizontal labels remain single-line even when this is enabled. Set this when a
+  narrow or localized vertical stepper would otherwise clip labels or overflow its allocation.
 - `effectiveOrientation: 'horizontal' | 'vertical'` (readonly getter) — the live layout/navigation
   axis actually in effect; identical to `orientation` whenever `orientationBreakpoint` is unset or
   doesn't resolve to a length. Also reflected as `data-effective-orientation` (only present while
@@ -87,8 +91,10 @@ text color of the `current` step. `--lr-stepper-current-font-weight` (default
 `var(--lr-font-weight-semibold)`) — font weight of the `current` step's label.
 `--lr-stepper-error-color` (default `var(--lr-color-danger)`) —
 text color of an `error` step. `--lr-stepper-current-index-bg` (default `var(--lr-color-brand)`) and
-`--lr-stepper-current-index-color` (default `var(--lr-color-surface)`) — background and text color
-of the `current` step's numbered `step-index` chip. Each is an inline `var()` fallback at the point
+`--lr-stepper-current-index-color` (default `var(--lr-color-on-brand)`) — background and text color
+of the `current` step's numbered `step-index` chip. The text color reads the dedicated on-brand
+foreground token, not `--lr-color-surface`, so the chip stays legible in dark mode and under forced
+colors, where surface and on-brand diverge. Each is an inline `var()` fallback at the point
 of use, never declared on `:host`, so it can be set on the element or on any ancestor; and each is
 scoped to its own `data-state`, so recoloring the current step leaves `pending`/`completed`/`error`
 steps alone. The hooks exist because `::part(step)[data-state='current']` is invalid CSS — Shadow
@@ -96,7 +102,7 @@ Parts forbids an attribute selector after `::part()` — so state-specific themi
 overriding a library-wide `--lr-color-*` token and repainting everything else that read it. Unset,
 each falls back to the token its rule used before. Otherwise shared tokens —
 `--lr-space-m`/`-xs`/`-2xs`,
-`--lr-color-text-quiet`/`-text`/`-danger`/`-brand`/`-surface`, `--lr-radius`/`-pill`,
+`--lr-color-text-quiet`/`-text`/`-danger`/`-brand`/`-on-brand`, `--lr-radius`/`-pill`,
 `--lr-font-size-xs`, `--lr-font-weight-semibold`, `--lr-opacity-disabled`,
 `--lr-focus-ring-*`.
 

package/llms/components/lr-svg-viewer.md

@@ -15,26 +15,42 @@
 
 Fetches an SVG document, sanitizes it with the optional `dompurify` peer, and renders it inline.
 
+Adopts `DocumentAnchorTarget` (the same shared mixin `lr-pdf-viewer`/`lr-csv-viewer` use): a `region`
+anchor addresses one `highlights` entry, matched by reference or by structural equality of its `rect`
+(and optional `page`). Assigning `anchor` or calling `scrollToAnchor()` scrolls the matching
+`[part="region-highlight"]` into view and fires `lr-anchor-result`. No other anchor kind resolves
+here — a sanitized SVG document has neither pages nor extractable text to quote, which is also why
+its registry entry declares `capabilities: { anchors: ['region'], search: false, textSelect: false }`.
+
 **Properties:** `src`, `name`, and `maxHeight` (attribute `max-height`) are strings. `maxHeight` caps
 the scrollable body. `zoomable: boolean = false` (reflected) — wraps the rendered content in an
 internal `<lr-zoomable-frame>`. `false` (the default) preserves the exact pre-`zoomable` DOM — an
 inline thumbnail (e.g. in a chat stream) must not unexpectedly grow a focusable zoom-chrome viewport;
-an inspection surface opts in. `highlights: LyraHighlight[] = []` (attribute: false) — display-only
-`region` highlights painted over the rendered SVG. `activeHighlightId: string | null = null`
+an inspection surface opts in. `anchor: LyraAnchor | string | null = null` (attribute: false) —
+declaratively jump to an anchor (a `LyraAnchor` object, or a `highlights` entry's `id`). Assigning it
+calls `scrollToAnchor()` and fires `lr-anchor-result`; re-assigning the same value re-triggers the
+scroll, it is not reference-gated. `highlights: LyraHighlight[] = []` (attribute: false) —
+display-only `region` highlights painted over the rendered SVG; unchanged behavior, now inherited
+from `DocumentAnchorTarget` rather than declared locally. `activeHighlightId: string | null = null`
 (attribute `active-highlight-id`) — the `highlights` entry, if any, currently treated as active
 (`data-active` on its `region-highlight`). `anchorKinds` is a readonly `['region']` (this viewer's
 supported `LyraAnchor.kind` values for the shared anchor-target contract).
 
-**Methods:** `scrollToAnchor(target)` — scrolls a `region` highlight (by id, or a `LyraAnchor` matched
-back to its owning `LyraHighlight` by reference) into view; resolves `false` when nothing matches, the
-anchor isn't `region`, or the document isn't loaded yet (no retry loop — a caller invoking this before
-`src` resolves simply gets `false`).
+**Methods:** `scrollToAnchor(target): Promise<boolean>` — scrolls the `highlights` entry matching
+`target` (a `region`-kind `LyraAnchor`, matched by reference or by structural equality of
+`rect`/`page`; or a `highlights[].id` string) into view, honoring `prefers-reduced-motion`. Resolves
+`true` when a match was found and scrolled, `false` otherwise, and always fires `lr-anchor-result`
+carrying the same boolean. Called before the SVG has finished loading it retries for up to 5s (real
+timers) rather than failing immediately.
 
 **Events:** `lr-render-error` with `detail.error` when fetching or sanitizing fails.
 `lr-highlight-activate` (`detail: { id }`) — a region highlight was clicked or activated via
-Enter/Space.
+Enter/Space. `lr-anchor-result` (`detail: { found: boolean }`) — fired after an `anchor` assignment
+or a `scrollToAnchor()` call is applied, whether or not a match was found.
 
-**CSS parts:** `base`, `body`, `svg`, `spinner`, `error`, `highlight-layer` (wrapper around every
+**CSS parts:** `base`, `body`, `svg`, `spinner`, `error`, `anchor-live-region` (the visually-hidden
+`role="status"` element announcing anchor-jump results to assistive tech),
+`highlight-layer` (wrapper around every
 rendered region highlight), `region-highlight` (one region highlight, `data-tone`, `data-active`),
 `region-highlight-target` (transparent activation geometry with an independent minimum hit area),
 `highlight-actions` (non-overlapping actions for multiple highlights), `region-highlight-action`

package/llms/components/lr-table.md

@@ -53,7 +53,8 @@ own "consumer computes/renders" contract rather than assuming addition.
   via the retheme-able `--lr-table-heat-tint-lo`/`-hi` custom properties, matching `lr-heatmap`'s
   own ramp-token convention; `cellStyle` is applied directly to the generated `<td>` via `styleMap` — e.g. a computed heat-tint
   background a `cell()`-returned inner element can't paint into the cell's own padding — omit it for
-  no per-cell style override (the default, unchanged output); `editable` enables inline editing —
+  no per-cell style override (the default, unchanged output);
+  `editable` enables inline editing —
   `true` opens a native editor on that cell's double-click (one cell at a time), `'always'` instead
   renders a persistent editor in every body cell of the column from first paint, for a
   settings/rate-style column meant to be typed straight into — while `editValue` supplies the editor
@@ -65,7 +66,16 @@ own "consumer computes/renders" contract rather than assuming addition.
   the live width in CSS pixels. Drag it, or use logical ArrowLeft/ArrowRight for 10px steps (mirrored
   under RTL), Shift+Arrow for 50px steps, Home for the minimum, and End for an explicit pixel
   `maxWidth`; explicit pixel `minWidth`/`maxWidth` values bound both input paths. The separator
-  exposes its current/minimum/bounded-maximum pixel width through ARIA value attributes.
+  exposes its current/minimum/bounded-maximum pixel width through ARIA value attributes. Only the
+  *commit* is vetoable — see `lr-column-resize` under Events.
+- **`cellStyle` beats `heatValue`, always.** `styleMap` writes an inline `style=` attribute, and an
+  inline style outranks any stylesheet rule in the cascade regardless of specificity, while the heat
+  tint is painted by a shadow-stylesheet rule. So a `cellStyle` returning
+  `background`/`backgroundColor` on a column that also defines `heatValue` silently and completely
+  erases that column's tint — no warning, and the cell still contributes to the shared domain, so the
+  *other* tinted columns' scale shifts around a cell that shows no tint at all. Define both on one
+  column only when that override is the intent; to tint *and* style, return only non-background
+  declarations (`color`, `fontWeight`, `textAlign`, …) from `cellStyle`.
 - `columns[].editable: boolean | 'always'` — a widening of the original `boolean`, non-breaking.
   `true` is unchanged: double-click a cell to open its editor, one at a time, Enter commits and
   closes, Escape cancels and closes, blur-after-change commits. `'always'` renders an editor in
@@ -226,7 +236,15 @@ own "consumer computes/renders" contract rather than assuming addition.
 `lr-selection-change` (`detail: { keys }`) when selection is enabled, `lr-filter-change`
 (`detail: { text }`), and `lr-page-change` (`detail: { page }`) from the controlled
 filter/pagination surfaces, and `lr-cell-edit` (`detail: { row, key, value }`) for editable
-columns, and `lr-column-resize` (`detail: { key, width }`) on every pointer or keyboard resize step.
+columns, and `lr-column-resize` (`detail: { key, width }`, `width` in CSS pixels) on every pointer or
+keyboard resize step. **Only the commit is cancelable.** A pointer drag fires the event once per
+pixel of movement as non-cancelable live feedback, then exactly once more — `cancelable: true` — for
+the width committed at drag-end (and only when that width actually differs from the pre-drag one).
+A keyboard step (Arrow/Shift+Arrow/Home/End) is already one discrete action, so it fires that single
+cancelable commit directly, with no live-feedback stream. Calling `preventDefault()` on a cancelable
+emission reverts the column to its pre-gesture width (or removes the override entirely if the column
+had never been resized); calling it on a mid-drag step does nothing, by design — a veto is a decision
+about the final width, not about every pixel the pointer passes through.
 The internal filter/cell-editor native inputs' `focus` and `blur` are also re-dispatched from the
 host as bubbling, composed events (the native ones are neither).
 

package/llms/components/lr-task-list.md

@@ -6,7 +6,7 @@
 - **Class** `LyraTaskList`, also available unregistered from `@aceshooting/lyra-ui/components/agent-tools/task-list/task-list.class.js`
 - **Family** `components/agent-tools/` — see `llms/index.md` for its siblings
 - **Optional peers** none
-- **Themeable via** 11 parts, 4 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 11 parts, 5 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -45,9 +45,13 @@ indicator, only rendered when `collapsible`), `body` (the list of items, `hidden
 `item-detail`, and `item-children` (the nested `role="list"` wrapper around a top-level item's
 children).
 
-**Themeable custom properties:** `--lr-task-list-spin` (default `1s linear`) — running-status icon
-spin animation duration/timing; `--lr-task-list-compact-header-padding` (default
+**Themeable custom properties:** `--lr-task-list-spin` (default `var(--lr-transition-ambient)`, i.e.
+`1.8s ease-in-out`, collapsing to `0.001ms linear` under `prefers-reduced-motion`) — running-status
+icon spin animation duration/timing; `--lr-task-list-compact-header-padding` (default
 `var(--lr-space-2xs) var(--lr-space-s)`) — `[part="header"]` padding while `compact`;
+`--lr-task-list-compact-header-gap` (default `var(--lr-space-2xs)`) — gap between `[part="header"]`'s
+label/summary/toggle while `compact`, one step tighter than the header's uncompacted
+`--lr-space-xs`, so `compact` tightens the header's *interior* spacing and not just its padding;
 `--lr-task-list-compact-gap` (default `var(--lr-space-2xs)`) — gap between `[part="body"]`'s item
 rows while `compact`; `--lr-task-list-compact-body-padding` (default `var(--lr-space-2xs)
 var(--lr-space-s) var(--lr-space-s)`) — `[part="body"]` padding while `compact`.

package/llms/components/lr-terminal.md

@@ -23,12 +23,18 @@ codes. `maxScrollback: number = 5000` (attribute `max-scrollback`), `follow: boo
 string = 'terminal.log'`, `announceOutput: boolean = false` (attribute `announce-output`),
 `accessibleLabel: string = ''` (attribute `aria-label`), `highlights: LyraHighlight[] = []` (attribute:
 false), and `activeHighlightId: string | null = null` (attribute: false). `anchorKinds` is a readonly
-`['page', 'text-quote', 'region']` for the shared anchor-target contract.
+`['line-range']` — a scrollback buffer addresses positions by line number, so `line-range` is the
+only kind `scrollToAnchor()` resolves; `page`/`text-quote`/`region` belong to the paginated document
+viewers, not here. `<lr-terminal>` is not registered in the document-renderer registry, so this field
+is a plain readonly property rather than the `DocumentAnchorTarget` mixin's `override readonly` one.
 
 **Methods:** `write(text)` appends ANSI-parsed text to the buffer. `clear()` empties the buffer.
-`scrollToBottom()` and `scrollToAnchor(anchor)` control scroll position. `search(query)`,
-`searchNext()`, `searchPrevious()`, and `clearSearch()` drive in-buffer text search. `getPlainText()`
-returns the SGR-stripped plain text of the whole buffer.
+`scrollToBottom()` and `scrollToAnchor(anchor): Promise<boolean>` control scroll position.
+`search(query): Promise<number>` (resolves the match count after the resulting render),
+`searchNext()`, `searchPrevious()`, and `clearSearch()` drive in-buffer text search — matching is
+line-granular (a match identifies a whole line, not a character range) and capped, so `matchCount`
+stops climbing on a pathologically repetitive buffer. `getPlainText()` returns the SGR-stripped
+plain text of the whole buffer.
 
 **Events:** `lr-copy` (`detail: { text }`), `lr-download` (`detail: { filename }`),
 `lr-follow-change` (`detail: { following }`), `lr-search-change` (`detail: { query, matchCount,

package/llms/components/lr-time-range.md

@@ -47,6 +47,12 @@ consumer-facing `disabled` property/attribute itself.
 PageDown key press, `detail: { start, end }`), `lr-change` (fired on pointer release /
 key-up-commit, or when a preset button is clicked, `detail: { start, end }`)
 
+**Methods:** `focus(options?)`, `blur()`, and `click()` forward to `[part="handle-start"]`. A
+two-handle control has no single canonical target, so the start handle is the one they address —
+call `.focus()` on `::part(handle-end)` yourself if you need the other. Without these overrides the
+host's own `focus()`/`blur()`/`click()` are no-ops, because the real control lives in the shadow
+root.
+
 **Slots:** none.
 
 **CSS parts:** `base`, `track`, `range`, `handle-start`, `handle-end`, `presets`, `preset-button`

package/llms/components/lr-tool-call-chip.md

@@ -49,9 +49,10 @@ the built-in glyph for the current `status` is used)
 `summary`), `category`, `name`, `summary`, `meta` (wrapper around `status-text` and `duration`),
 `status-text`, `duration`, `tooltip` (the floating detail popup, only meaningful while open)
 
-**Themeable custom properties:** `--lr-tool-call-chip-spin` (default `1s linear` — running-icon
-animation duration/timing) and `--lr-transition-ambient` (default `1.8s ease-in-out` — pending-icon
-pulse duration/timing). `--lr-tool-call-chip-accent`, `--lr-tool-call-chip-bg`, and
+**Themeable custom properties:** `--lr-tool-call-chip-spin` (default `var(--lr-transition-ambient)`,
+i.e. `1.8s ease-in-out` at the shipped token value and `0.001ms linear` under
+`prefers-reduced-motion` — running-icon animation duration/timing) and `--lr-transition-ambient`
+(default `1.8s ease-in-out` — pending-icon pulse duration/timing). `--lr-tool-call-chip-accent`, `--lr-tool-call-chip-bg`, and
 `--lr-tool-call-chip-border` are internal per-status variables reassigned by this component's own
 `:host([status="…"])` rules (e.g. `pending` → `--lr-color-text-quiet`/`--lr-color-surface`/
 `--lr-color-border`; `running` → brand; `success` → success; `error` → danger; `denied` → warning),

package/llms/components/lr-tool-param-form.md

@@ -6,7 +6,7 @@
 - **Class** `LyraToolParamForm`, also available unregistered from `@aceshooting/lyra-ui/components/agent-tools/tool-param-form/tool-param-form.class.js`
 - **Family** `components/agent-tools/` — see `llms/index.md` for its siblings
 - **Optional peers** none
-- **Themeable via** 7 parts, 0 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 8 parts, 0 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -73,7 +73,12 @@ set `valid: false` while `formError`, rather than a fabricated field key, carrie
 
 **Slots:** none.
 
-**CSS parts:** `base`, `field`, `label`, `description`, `error`, `unsupported`, `empty`
+**CSS parts:** `base`, `field`, `label`, `control`, `description`, `error`, `unsupported`, `empty`.
+`control` is the native `<input>` for a `'string'` (non-enum) or `'number'`/`'integer'` field — one
+shared part name across both the text and number inputs, and deliberately *not* present on the
+`'boolean'` (`<lr-checkbox>`), enum (`<lr-select>`), or unsupported-type fallback branches, which are
+composed components with their own part surfaces rather than raw natives. It is purely an additive
+external theming hook: the internal `.control` class the stylesheet targets is unchanged.
 
 **Themeable custom properties:** no component-specific custom properties; shared tokens only —
 `--lr-space-l/-xs/-s`, `--lr-color-border`, `--lr-radius`, `--lr-color-surface`,

package/llms/components/lr-tool-result-dialog.md

@@ -56,7 +56,8 @@ tool name/status/duration), `tool-name`, `status`, `duration`, `header-actions`,
 0.5)` — the backdrop scrim color; component-specific since no shared overlay token exists),
 `--lr-tool-result-dialog-maximized-inset` (default `var(--lr-space-l)` — inset applied to the
 panel while `[maximized]`, overridable e.g. to leave a persistent app rail visible), and
-`--lr-tool-result-dialog-spin` (default `1s linear`, stopped under reduced motion), plus shared
+`--lr-tool-result-dialog-spin` (default `var(--lr-transition-ambient)`, i.e. `1.8s ease-in-out`,
+and effectively stopped under reduced motion because that token collapses to `0.001ms linear`), plus shared
 tokens `--lr-color-surface/-border/-text-quiet/-brand/-brand-quiet/-success/-success-quiet/
 -danger/-danger-quiet/-warning/-warning-quiet`, `--lr-space-*`, `--lr-radius`, `--lr-shadow`,
 `--lr-icon-button-size`, `--lr-focus-ring-*`, `--lr-transition-base`.

package/llms/components/lr-tree-node.md

@@ -6,7 +6,7 @@
 - **Class** `LyraTreeNode`, also available unregistered from `@aceshooting/lyra-ui/components/data/tree/tree-node.class.js`
 - **Family** `components/data/` — see `llms/index.md` for its siblings
 - **Optional peers** none
-- **Themeable via** 8 parts, 1 custom property — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 8 parts, 3 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Documented with** `lr-tree` (same section below)
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 

package/llms/components/lr-widget.md

@@ -6,7 +6,7 @@
 - **Class** `LyraWidget`, also available unregistered from `@aceshooting/lyra-ui/components/layout/widget/widget.class.js`
 - **Family** `components/layout/` — see `llms/index.md` for its siblings
 - **Optional peers** none
-- **Themeable via** 16 parts, 5 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 16 parts, 7 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -89,6 +89,11 @@ override the library-wide `--lr-color-brand-quiet`/`--lr-color-brand` tokens, re
 element that reads them. Left unset, each falls back to exactly the token the rule used before, so
 rendering is unchanged.
 
+`--lr-widget-view-toggle-hover-bg` (default `var(--lr-color-brand-quiet)`) and
+`--lr-widget-view-toggle-hover-color` (default `var(--lr-color-text)`) are the same shape for the
+*hover* state, and the `:hover` rule wraps its selector in `:where()` so a consumer's own
+`::part(view-toggle):hover` override wins without `!important`.
+
 **Optional peer deps:** none.
 
 ```html

package/llms/shared.md

@@ -331,7 +331,7 @@ The side-effect-free `@aceshooting/lyra-ui/localization.js` entry exports
 `LYRA_DEFAULT_STRINGS`, and the types `LyraLocaleStrings` / `LyraMessageKey`. The package root
 continues to re-export the same surface for compatibility, but it also registers the non-peer-gated
 component graph; use the dedicated entry when the application only needs locale setup.
-**`LYRA_DEFAULT_STRINGS` is the authoritative key list** (1005 keys, matching the
+**`LYRA_DEFAULT_STRINGS` is the authoritative key list** (1170 keys, matching the
 `LyraMessageKey` union) — read it to find the key to override rather than guessing one. Lookup
 falls back exact locale → base language → English. Date, number, byte, relative-time and calendar
 output goes through `Intl`.