@aceshooting/lyra-ui 13.0.1 → 14.1.0

package/llms/components/lr-slider.md

@@ -19,12 +19,22 @@
 A numeric range control (e.g. an LLM "temperature" setting). **Form-associated** directly through
 `ElementInternals`, because its public `value` is a number rather than the string assumed by the
 shared form mixin. `value`, `defaultValue`, and `valueAsNumber` are numeric; `valueAsString` is the
-explicit compatibility round-trip for code that still wants a serialized value. Clicking anywhere
+explicit compatibility round-trip for code that still wants a serialized value. A primary-button press anywhere
 on `[part~="base"]` (not just the thumb) jumps the
 thumb to that point and continues the same gesture as a drag, matching native `<input type=range>`
 click-to-seek — the thumb is also `.focus()`ed on that click, so keyboard interaction can continue
 seamlessly right after. Mirrors the core `<wa-slider>` API under the `lr-` prefix.
 
+Secondary mouse buttons leave the value and input/change events untouched. Primary mouse, touch and
+pen gestures remain supported, including concurrent pointers.
+
+Removing `label`, `hint`, `help-text` or `error-text` safely removes the corresponding copy; native
+attribute-removal property readback remains unchanged, including `null`. Supplying an empty string
+or later replacement remains supported. In single mode, host `aria-describedby` references resolve
+in the host's root and precede local error/hint descriptions on the slider handle. Target
+replacement, removal, reinsertion, host reconnection and document adoption update the relationship
+without losing local guidance.
+
 **Two-handle `range` mode.** `range` turns the control into a selection between `minValue` and
 `maxValue`, defaulting to `0`/`50`. Each handle is a separately focusable `role="slider"` with its
 own localized accessible name and the full domain as its reachable range. When the active handle
@@ -104,7 +114,9 @@ single numeric string entry.
   a range readout joins both values with an en dash. The explicit HTML spelling
   `show-value="false"` stays false.
 - `value: number = 0`, `defaultValue: number = 0` (attribute `value`), `valueAsNumber: number`, and
-  `valueAsString: string` are synchronized, finite, clamped, and step-snapped.
+  `valueAsString: string` are synchronized and finite. Values normalize the low/high domain, snap
+  to the grid anchored at the low endpoint, then clamp so a non-grid endpoint remains reachable;
+  invalid, nonpositive, or below-resolution steps are unstepped.
 - `isRange: boolean` is the read-only normalized range-mode state.
 - `name: string | null = null`, `disabled = false`, `required = false`, reflected `customError`,
   plus read-only `form`, `labels`, `validity`, `validationMessage`, and `willValidate` make up the
@@ -112,9 +124,11 @@ single numeric string entry.
 
 **Events:** native-style `input` (no detail), then `lr-input`, fire continuously during an active
 drag or keyboard step, including OS key-repeat while a key is held. Native-style `change` (no
-detail), then `lr-change`, fire once an interaction commits: on pointerup for a drag, or on keyup
-for a keyboard step, so a single Arrow/Home/End/PageUp/PageDown press fires both pairs, mirroring
-native `<input type=range>` timing.
+detail), then `lr-change`, fire once an interaction commits: on pointerup for an enabled drag,
+or on keyup or ordinary blur for a changed keyboard sequence. A later keyup cannot duplicate a
+blur commit. Own or fieldset disablement, and readonly, cancel unfinished gestures without
+reverting their live values or emitting a later change pair. Pointer cancellation, lost capture
+and disconnection also remain noncommitting.
 The focused handle's native `focus` and `blur` are re-dispatched from the host as bubbling,
 composed events.
 `lr-invalid` (no detail) fires when a validity check finds the slider invalid.

package/llms/components/lr-source-picker.md

@@ -21,6 +21,10 @@ type icons, search. **Not `FormAssociated`, deliberately**: this is a scoping pa
 control — the selection is immediate app state consumed by the next retrieval call, exactly the
 stance `lr-tool-select-dialog` already takes.
 
+Toggling search retains the query and selected source IDs. Re-enabling a retained filter repairs the
+active tree row so one visible usable Tab stop remains whenever rows are visible; focus already in
+the tree follows that repair, while focus outside is preserved.
+
 **Properties:**
 
 - `sources: LyraSourceEntry[] = []` (attribute: false) — `LyraSourceEntry { id: string; label:

package/llms/components/lr-span-waterfall.md

@@ -20,6 +20,9 @@ The horizontal-timeline projection of the same `LyraSpan[]` `<lr-trace-tree>` co
 axis, one row per span in start order, status-toned bars (Langfuse timeline / Temporal
 event-history style).
 
+Span views omit whitespace-only IDs and preserve every nonblank business ID exactly, including
+surrounding whitespace. The first valid admitted duplicate continues to win.
+
 **Properties:** `spans: LyraSpan[] = []` (attribute: false) — `LyraSpan { id: string; parentId?:
 string; name: string; kind: 'agent' | 'llm' | 'tool' | 'retriever' | 'embedding' | 'other';
 startMs: number; endMs?: number; status: 'pending' | 'running' | 'success' | 'error' | 'denied';

package/llms/components/lr-sparkline.md

@@ -20,6 +20,10 @@ Zero-dependency inline SVG trend chart (mirrors `<wa-sparkline>`). Its default a
 `em` tall at a `4 / 1` aspect ratio, so it can sit directly in text; authored block size changes
 both dimensions through the aspect ratio.
 
+An empty or removed `data` attribute uses the `values` collection. With no usable fallback samples,
+no trend path is rendered. Attribute removal preserves `null` property readback, and supplying later
+space-separated samples restores the attribute-driven path.
+
 **Properties:**
 
 - `appearance: 'gradient'|'line'|'solid' = 'solid'` (reflected) — `solid` fills the area below the

package/llms/components/lr-split-panel.md

@@ -21,6 +21,10 @@ component when migrated markup has named `start` and `end` panes. The separate `
 Lyra's multi-panel layout: its direct default-slot children, responsive collapse modes, and
 multi-divider events are intentionally a different API.
 
+Both `lr-reposition-request` detail fields `position` and `positionInPixels` measure from the
+selected primary edge and agree with accepted public property readback, including `primary="end"`.
+Canceling preserves both prior values; direct property writes remain silent.
+
 **Properties:**
 
 - `position: number = 50` (reflected) — divider position from the selected `primary` pane's edge,

package/llms/components/lr-stack-trace.md

@@ -23,6 +23,9 @@ behind a count-labeled toggle. A malformed or non-safe-integer location remains
 non-activatable text. Falls back to verbatim raw text when nothing parses. First-party invention
 (no Web Awesome equivalent).
 
+Removing the `trace` attribute clears parsed content and copies empty text; the property retains
+`null` until assigned again.
+
 **Properties:**
 
 - `trace: string = ''` — the raw stack trace text to parse and render.

package/llms/components/lr-stat.md

@@ -18,6 +18,16 @@
 
 KPI/stat card — value + unit + label + optional icon/trend/caption.
 
+Passive slotted content preserves normal pointer activation and Control/Meta/Shift intent. The
+platform primary modifier and Shift activate a new browsing context through the real anchor;
+listeners may cancel that activation. Nested interactive controls retain their own actions.
+Temporary target and relation values are restored after activation unless the listener changed those
+attributes itself.
+
+Removing `caption` or `sub` omits the attribute fallback without hiding assigned slot content.
+Removal retains `null` property readback; explicit empty strings remain empty and later supplied
+values render normally.
+
 **Renamed in 8.0.0 — breaking:** `appearance` is now `frame`. Library-wide, `appearance` means only
 "how a control fills itself" and `frame` means "whether a container draws itself as a bounded card";
 this property was always the second. There is no alias — `appearance` on `<lr-stat>` is an unknown

package/llms/components/lr-streaming-text.md

@@ -77,9 +77,8 @@ property and therefore never requests `katex` itself.
 ```
 
 Token-by-token streaming can update `content` far faster than a human can usefully perceive a
-re-render, so updates funnel through `Announcer` (`../../internal/announcer.js`), reused here
-purely as a generic "coalesce rapid calls, flush the latest" timing primitive — with none of that
-class's usual DOM/ARIA plumbing. Within any `coalesce-ms` window, only the _last_ `content` value
+re-render, so updates use a shared coalescing timer. Within any `coalesce-ms` window, only the
+_last_ `content` value
 assigned actually reaches the rendered DOM. Two cases always bypass the throttle and flush
 immediately: the very first `content` assignment after mount, and any transition of `streaming`
 between `true` and `false` in _either_ direction — so the final chunk of a finished stream can

package/llms/components/lr-subagent-panel.md

@@ -25,8 +25,9 @@ parents remain renderable instead of recursing forever.
 accessible-name override for the `role="tree"` element, where omission reads back `undefined` and
 localizes the default while any supplied string, including `''`, renders verbatim.
 `SubagentRun = { id: string; parentId?: string; label: string; status: AgentStatusKind; task?:
-string; model?: string; progress?: number; startedAt?: number; endedAt?: number; metadata?:
-Record<string, unknown> }`.
+string; model?: string; readonly progressRatio?: number; startedAt?: number; endedAt?: number;
+metadata?: Record<string, unknown> }`. `progressRatio` represents completion from `0` to `1`,
+inclusive.
 Empty/blank run ids are omitted and later duplicate ids are ignored before hierarchy, focus,
 counts, selection, and events.
 

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

@@ -23,6 +23,9 @@ resource or paint-server references before insertion, preventing fetched SVG con
 the viewer's paint box or starting secondary requests. Local `url(#id)` paint servers and embedded
 raster data remain available.
 
+Fitting SVG content stays centered. In a capped nonzoomable viewer, overflowing content begins
+inside the body's reachable scroll range, keeping both its top and bottom available.
+
 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

package/llms/components/lr-swatch-picker.md

@@ -27,6 +27,10 @@ shortcut list alongside a grid, a hue ramp and a text field that can still expre
 Arrow/Home/End navigation starts from the swatch that actually received the keyboard event, even
 when a controlled `value` write changed the selected or remembered roving item first.
 
+Own `disabled` changes take effect immediately for host `click()` and `focus()`, including calls in
+the same task as the property assignment. Blocked activation leaves value and `lr-change` untouched;
+blocked focus preserves outside focus and emits no native focus inside the picker.
+
 **Properties:**
 
 - `items: readonly SwatchPickerItem[] = []` (attribute: false) — `SwatchPickerItem { readonly value:

package/llms/components/lr-switch.md

@@ -25,6 +25,12 @@ CSS parts), mirroring `<lr-select>`'s pattern for those two pieces — left unse
 Deliberately no separate top-of-field `label` prop/slot/part: the default slot already is this
 control's visible, clickable label (same as `<lr-checkbox>`).
 
+Host `aria-describedby` references resolve onto the internal `role="switch"` before its local
+error/hint guidance. The relationship tracks missing IDs, target replacement/removal/reinsertion,
+reconnect, and document adoption. Removing `hint`, `help-text`, or `error-text` safely omits that
+content while preserving native `null` property readback; explicit empty and later text work
+normally.
+
 **Properties:**
 
 - `checked: boolean = false` — the live, non-reflecting state

package/llms/components/lr-tab-group.md

@@ -19,6 +19,10 @@
 
 A tab strip. Mirrors `wa-tab-group` / `sl-tab-group`.
 
+With manual activation, removing the focused unselected tab rehomes actual focus to a valid survivor
+while retaining a valid selected tab and panel. This repair emits no show/hide events and preserves
+focus already held by an outside control.
+
 **Renamed in 8.0.0.** This element used to be `<lr-tabs>`. The tag is now `<lr-tab-group>`, its
 single `lr-tabs-change` event is now the `lr-tab-hide` → `lr-tab-show` pair below, and every
 `--lr-tabs-*` custom property is now spelled `--lr-tab-group-*` (`--lr-tabs-selected-color` →

package/llms/components/lr-table.md

@@ -26,6 +26,10 @@ add a trailing totals column mirroring `expandedContent`'s leading one — `rowT
 per-row, `grandTotal(rows)` renders at its intersection with the footer row — both sharing `footer`'s
 own "consumer computes/renders" contract rather than assuming addition.
 
+Effective locale changes recollate and filter the current view while keeping activation and edit
+lookups aligned with the rendered page. Direct row focus uses the same stable-key restoration rules;
+programmatic locale changes do not emit a row action.
+
 Header cells and body rows use separate roving tab stops. When a controlled `columns` or rendered
 row collection changes while one of those stops owns focus, the table keeps the same stable key if
 it survives and otherwise clamps focus to the nearest surviving index. Moving focus outside the
@@ -170,7 +174,9 @@ cell: (row) => unknown }` —
   facades; reassign a new set to update
 - `filterable: boolean = false` (attribute `filterable`, reflected) — renders a localized search
   field above the grid
-- `filterText: string = ''` (attribute `filter-text`) — controlled filter text
+- `filterText: string = ''` (attribute `filter-text`) — controlled filter text. Removing the
+  attribute clears the effective filter safely while retaining native removal readback; a later
+  supplied value filters normally.
 - `filter?: (row: T, text: string) => boolean` (attribute: false) — typed predicate used by the
   filter field; when omitted, rows are matched against their JSON representation
 - `filterLabel?: string` (attribute `filter-label`) and `filterPlaceholder?: string`
@@ -254,7 +260,9 @@ cell: (row) => unknown }` —
 - `hideColumnsLabel?: string` (attribute `hide-columns-label`) — the same button's label once
   the columns have been revealed; omission renders localized `showFewerColumns` (`'Show fewer columns'` in the built-in English catalog), while a supplied string (including `''`) is verbatim
 - `priorityColumnsVisible: boolean = false` (attribute `priority-columns-visible`, reflected) —
-  forces responsive priority columns visible and is updated by the built-in reveal button
+  forces responsive priority columns visible and is updated by the built-in reveal button.
+  Priority-hidden columns hide their header, body, and footer cells together at the existing
+  container breakpoints in either direction; revealing columns restores all three bands.
 - `storageKey?: string` (attribute `storage-key`) — when set, persists `priorityColumnsVisible` to
   `localStorage` (namespaced as `lr-table:${storageKey}`) and restores it on the next mount. Unset
   (the default) touches storage not at all. Mirrors `lr-app-rail`'s identical `storage-key` pattern

package/llms/components/lr-terminal.md

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 16 parts, 11 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 16 parts, 16 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`
 
 ---
@@ -21,6 +21,9 @@ cursor-addressed full-screen apps. An ANSI sequence split across chunks retains
 characters; an overlong unterminated CSI/OSC sequence is dropped and the next write resumes from a
 clean parser boundary.
 
+A search with no matches clears earlier rendered match markers. Removing the `content` attribute
+clears output and preserves the normal `null` property readback.
+
 **Properties:** `content: string = ''` — initial/replaceable buffer content, parsed for ANSI/SGR
 codes. `replace(content: string): void` synchronously replaces the parsed buffer and reactive
 `content` source, preserving commit order with same-turn `write()`/`clear()` calls.
@@ -80,13 +83,22 @@ of the text last announced while `announce-output` is set).
 `[part="announcer"]` is a styling and inspection surface only — it carries **no** live-region role
 of its own. The announcement itself goes to the library's shared **light-DOM** polite region,
 appended to the consumer's `<body>` and marked `data-lr-live-region="polite"`, because a live
-region inside a shadow root is not reliably announced (JAWS with Firefox ignores one outright). A
-test therefore asserts against that shared region, not `::part(announcer)`; the part remains the
-right hook for styling, and for reading back what the terminal last announced.
+region inside a shadow root is not reliably announced (JAWS with Firefox ignores one outright).
+Inspect the shared region, not `::part(announcer)`, when reading an announcement; the part remains
+the right hook for styling and for reading back what the terminal last announced.
 
 **Themeable custom properties:** `--lr-terminal-height` (default `var(--lr-size-20rem)`) — the
 viewport's block size; not declared on `:host`, so it is inherited from the host or any ancestor.
-`--lr-terminal-highlight-accent-bg` (default `var(--lr-color-brand-quiet)`),
+`--lr-terminal-surface-color` (default `var(--lr-color-surface-raised)`) controls the card-frame
+background and the fallback foreground for inverse ANSI segments without an explicit background;
+`frame="plain"` remains transparent. `--lr-terminal-toolbar-button-hover-bg` (default
+`var(--lr-color-brand-quiet)`) and `--lr-terminal-toolbar-button-active-bg` (default
+`color-mix(in oklab, var(--lr-terminal-toolbar-button-hover-bg, var(--lr-color-brand-quiet)),
+var(--lr-color-mix-partner) var(--lr-color-mix-active))`) control the copy and download buttons.
+`--lr-terminal-line-hover-bg` (default `var(--lr-color-brand-quiet)`) and
+`--lr-terminal-line-active-bg` (default `color-mix(in oklab, var(--lr-terminal-line-hover-bg,
+var(--lr-color-brand-quiet)), var(--lr-color-mix-partner) var(--lr-color-mix-active))`) control
+ordinary rendered lines. `--lr-terminal-highlight-accent-bg` (default `var(--lr-color-brand-quiet)`),
 `--lr-terminal-highlight-success-bg` (default `var(--lr-color-success-quiet)`),
 `--lr-terminal-highlight-warning-bg` (default `var(--lr-color-warning-quiet)`),
 `--lr-terminal-highlight-danger-bg` (default `var(--lr-color-danger-quiet)`), and

package/llms/components/lr-textarea.md

@@ -21,6 +21,15 @@ submission/validation/reset via `name`/`value`/`disabled`/`required`/`checkValid
 `reportValidity()`). Ships an opt-in `label`/`hint`/`errorText` form-control chrome mirroring
 `lr-select` -- left unset, none of it renders.
 
+Removing `label`, `hint`, `help-text`, or `error-text` safely omits the corresponding content while
+preserving native `null` property readback. Explicit empty strings stay empty; later supplied text
+renders normally.
+
+Changing own `disabled` from true to false in the same task that disables an ancestor fieldset keeps
+the native editing control effectively disabled. The enabled first-legend exception and explicit
+own-disabled state retain their native meaning; validity and form submission follow the effective
+disabled state.
+
 ```html
 <lr-textarea placeholder="Notes" rows="4"></lr-textarea>
 <lr-textarea

package/llms/components/lr-thinking-panel.md

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 6 parts, 5 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 6 parts, 6 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`
 
 ---
@@ -75,6 +75,8 @@ pending duration/toggle accent without changing the shared brand token;
 `--lr-thinking-panel-compact-header-padding` (default `var(--lr-space-2xs) var(--lr-space-s)`) —
 `[part="header"]` padding while `compact`; `--lr-thinking-panel-compact-header-gap` (default
 `var(--lr-space-2xs)`) — gap between the toggle, label, and duration while `compact`; and
+`--lr-thinking-panel-compact-header-font-size` (default `var(--lr-font-size-sm)`) — font size of
+`[part="header"]` while `compact`; and
 `--lr-thinking-panel-compact-body-padding` (default `var(--lr-space-s)`) — `[part="body"]`
 padding while `compact`. Plus shared
 `--lr-color-border`/`-surface`/`-text`/`-text-quiet`/`-brand`/`-brand-quiet`,

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

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 33 parts, 4 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 33 parts, 12 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`
 
 ---
@@ -26,6 +26,9 @@ row actions in that mode. No thread CRUD or persistence — every mutation
 (`lr-thread-pin`/`-archive`/`-delete`/`-rename`) is a controlled event carrying the _requested_ new
 state; the host mutates `threads`.
 
+A conversation row with `slot=""` belongs to the default slot exactly like a row with no slot
+attribute, including after reconnect. Named slots retain their distinct roles.
+
 ArrowUp/ArrowDown/Home/End navigation skips rows that are disabled, hidden, `aria-hidden`, or
 `inert` (including an inert ancestor introduced by `wrapRow`). Arrow navigation continues through
 the complete item model at a virtual-window edge and mounts the next available row before moving
@@ -46,6 +49,10 @@ Data-mode thread ids must be nonempty, nonblank, and unique, and every row must
 before the mode is selected, so focus, actions, slot ownership, and emitted `conversationId`
 values remain unambiguous.
 
+Display fields are captured when `threads` is assigned. After a change, create and assign a new
+collection; changing an assigned record or mutating the assigned array does not update the view.
+`filter`, `groupBy`, row callbacks, and group contexts receive the original source records.
+
 **Properties:** `threads: LyraChatThread[] = []` (attribute: false). `activeConversationId: string = ''`
 (attribute `active-conversation-id`) — data mode:
 marks the matching row `active`/`aria-current` and scrolls it into view. `searchable: boolean =
@@ -80,9 +87,9 @@ property. `stickyGroups: boolean = false` (attribute `sticky-groups`, reflected)
 the current date/custom group's header to the top of the scroll viewport while its rows are in view,
 pushing it off as the next group's header arrives. Group headers are ordinary virtualized rows, so
 this renders an `aria-hidden` copy of the header into the internal `lr-virtual-list`'s sticky layer:
-the real row keeps the `role="heading"`/`aria-level` semantics and the tab order (the copy's toggle
-is not a second tab stop), while the pinned copy stays clickable and requests the same
-`lr-group-toggle` collapse. Default `false` renders exactly as before; `grouping="none"` has no
+the real row keeps the `role="heading"`/`aria-level` semantics and its interactive toggle. The
+pinned copy is inert, pointer-transparent presentation content: its toggle and adornments do not
+receive interaction, and it adds no second tab stop. Default `false` renders exactly as before; `grouping="none"` has no
 headers to pin, so it is a no-op there. `label?: string` — accessible name for the list region.
 Omitting it uses the localized `threadListLabel`; an explicit empty string intentionally leaves the
 list unnamed. `wrapRow?: (thread: LyraChatThread, row: TemplateResult) =>
@@ -157,6 +164,21 @@ prefix: `row-item-base`, `row-item-active-indicator`, `row-item-select-button`,
 internal virtual-list shadow tree, so set them on `lr-thread-list` or any ancestor. They do not style
 marks returned by `renderRowContent` or any other hook.
 
+**Themeable control states:** `--lr-thread-list-group-toggle-hover-bg` (default
+`var(--lr-color-surface-raised)`), `--lr-thread-list-group-toggle-hover-color` (default
+`var(--lr-color-text)`), `--lr-thread-list-group-toggle-active-bg` (default `color-mix(in oklab,
+var(--lr-thread-list-group-toggle-hover-bg, var(--lr-color-surface-raised)),
+var(--lr-color-mix-partner) var(--lr-color-mix-active))`), and
+`--lr-thread-list-group-toggle-active-color` (default
+`var(--lr-thread-list-group-toggle-hover-color, var(--lr-color-text))`) style group-toggle hover
+and pressed states. `--lr-thread-list-row-action-hover-bg` (default
+`var(--lr-color-surface-raised)`), `--lr-thread-list-row-action-hover-color` (default
+`var(--lr-color-text)`), `--lr-thread-list-row-action-active-bg` (default `color-mix(in oklab,
+var(--lr-thread-list-row-action-hover-bg, var(--lr-color-surface-raised)),
+var(--lr-color-mix-partner) var(--lr-color-mix-active))`), and
+`--lr-thread-list-row-action-active-color` (default
+`var(--lr-thread-list-row-action-hover-color, var(--lr-color-text))`) do the same for row actions.
+
 **Keep the two prefixes straight — they are different surfaces.** The `row-*` parts wrap _this_
 component's own render-callback output (`wrapRow`, `renderStart`, `renderExcerpt`,
 `renderRowContent`, `renderMeta`, `renderActions`); the `row-item-*` parts are the row item's

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

@@ -26,6 +26,9 @@ The clear/expand actions sit directly in the shared outer height ladder: compact
 enough for their hit targets, while `l` and `xl` retain the shared 48px and 56px heights rather
 than adding outer padding around the buttons.
 
+Removing `label` or `hint` safely omits that content while retaining native `null` property
+readback. Explicit empty strings remain empty; later supplied text renders normally.
+
 **Properties:**
 
 - `value: string` (also accepts a `Date` or `null` when assigned) — strict `HH:mm`, optional

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

@@ -25,6 +25,11 @@ The `base` part is an accessible `role="group"`: a non-empty host `aria-label` n
 aggregate. A native external `<label for>` remains available through `labels`, but it does not cross
 into the shadow-root group. `startLabel` and `endLabel` continue to name the individual sliders.
 
+Only the primary mouse button starts seeking or dragging. Right and middle presses leave the range
+and input/change events untouched. Touch and pen gestures keep their existing behavior, including
+concurrent pointer support; pointer cancellation and capture cleanup retain their existing
+semantics.
+
 **Properties:**
 
 - `min: number = 0`

package/llms/components/lr-timeline-item.md

@@ -26,6 +26,12 @@ item's `title`/`description` routinely hold focusable content, so wrapping the r
 would trip `nested-interactive`). The opt-in clustered time scale adds only native count-marker
 buttons; it does not make the individual rows interactive.
 
+Horizontal time layouts using `collision="overlap"` or `collision="stack"` allocate their block size
+from the actual item content and lane offsets. The height follows content growth, shrinkage, and
+changes in lane count. `--lr-timeline-time-extent` still controls only the main-axis distance, and
+horizontal scrolling retains clipping on the cross axis. Cluster mode keeps its existing sizing
+behavior.
+
 **`lr-timeline` properties:** `orientation: 'vertical' | 'horizontal' = 'vertical'` — note the
 opposite default from `lr-stepper`; `horizontal` makes `[part='base']` a horizontally scrollable row.
 `accessibleLabel?: string` (attribute `aria-label`) overrides the localized `"Timeline"` name —

package/llms/components/lr-timeline.md

@@ -26,6 +26,12 @@ item's `title`/`description` routinely hold focusable content, so wrapping the r
 would trip `nested-interactive`). The opt-in clustered time scale adds only native count-marker
 buttons; it does not make the individual rows interactive.
 
+Horizontal time layouts using `collision="overlap"` or `collision="stack"` allocate their block size
+from the actual item content and lane offsets. The height follows content growth, shrinkage, and
+changes in lane count. `--lr-timeline-time-extent` still controls only the main-axis distance, and
+horizontal scrolling retains clipping on the cross axis. Cluster mode keeps its existing sizing
+behavior.
+
 **`lr-timeline` properties:** `orientation: 'vertical' | 'horizontal' = 'vertical'` — note the
 opposite default from `lr-stepper`; `horizontal` makes `[part='base']` a horizontally scrollable row.
 `accessibleLabel?: string` (attribute `aria-label`) overrides the localized `"Timeline"` name —

package/llms/components/lr-token-input.md

@@ -21,6 +21,20 @@ prevented, so focus still advances normally. Backspace removes the last token. `
 readonly owned `readonly string[]` snapshot and repeated values are submitted under `name`; mutate
 a new array and reassign it to change the list.
 
+Composing keyboard events (`isComposing` or legacy key code 229) remain with the native draft or
+inline editor without adding/removing tokens, committing an edit or closing the editor. Normal
+Enter, delimiter, Tab, Backspace and Escape behavior is unchanged after composition.
+
+Host `aria-describedby` references resolve in the host's root and precede local hint/error guidance
+on the native draft input. Live source replacement, removal, reinsertion, host reconnection and
+document adoption update the relationship. Removing `label`, `hint` or `error-text` safely removes
+that copy while preserving native attribute-removal property readback, including `null`; explicit
+empty and later replacement strings remain supported.
+
+Editable token labels vertically center their text within the existing pointer target while
+retaining narrow-content ellipsis, wrapping and alignment with the remove action. The ordinary
+noneditable token layout remains the default.
+
 **Properties:** live, non-reflecting `value`, reflected `defaultValue` (attribute `value`, encoded
 as a JSON string array), `customError` (`custom-error`), `label`, `hint`, `errorText`
 (`error-text`), `placeholder`, `name`,

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

@@ -23,6 +23,9 @@ focused) fires `lr-tool-call-chip-select`; a consumer wires that to opening a
 `<lr-tool-result-dialog>` (or anything else) at the call site, keeping the chip reusable wherever
 a compact call summary is useful, with or without a detail surface behind it.
 
+Removing `category` or `summary` hides that optional text; assigning either attribute again restores
+its content.
+
 **Properties:**
 
 - `name: string = ''` — the tool/function name, e.g. `web_search`
@@ -98,8 +101,8 @@ referenced: `--lr-color-text-quiet`, `--lr-color-surface`, `--lr-color-border`,
 </script>
 ```
 
-The default slot's tooltip is positioned with the same `internal/positioner.js` `place()` helper
-`<lr-combobox>` uses for its listbox (`placement: 'top-start'`), and appears/disappears instantly
+The default slot's tooltip uses the same `'top-start'` placement as `<lr-combobox>`'s listbox, and
+appears/disappears instantly
 on hover/focus/blur/mouseleave with no fade transition and no "pointer moved into the tooltip"
 tracking — it's documented as read-only preview content, not an interactive surface meant to retain
 focus of its own. `denied` gets its own warning-toned glyph and color (a policy rejection, not a
@@ -109,9 +112,8 @@ sub-1000ms `"820ms"`, else trimmed to at most one decimal of seconds (`"1.5s"`,
 
 **Known gotchas:**
 
-- the default slot is checked for emptiness by scanning `Array.from(this.children)` for elements
-  once on first update, then kept in sync via `slotchange` — only _element_ children count (a bare
-  text node assigned to the default slot won't trigger the tooltip)
+- meaningful default-slot text or element content enables the preview tooltip; whitespace-only
+  text does not. A text preview needs no wrapper, and the preview remains inert and noninteractive
 - the native button always keeps its purpose-specific generated name (`"name — summary — Status —
 duration"`). A host `aria-label` remains on the host and is not cloned onto that button; even an
   explicit empty host label never leaves the actionable button unnamed

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

@@ -24,6 +24,10 @@ can name the form-associated host. A non-empty host `aria-label` remains on the
 aggregate semantic owner, so `base` omits its duplicate role/name. The individual generated fields
 keep their own purpose-specific names in every case.
 
+Choosing Boolean Unset keeps an explicit `undefined` value when a schema default exists; deleting
+that key or replacing the value with an absent key restores default materialization. Without a
+schema default, Unset removes the key.
+
 **Supported schema subset:** a _flat_ object whose properties use one primitive `type`
 (`'string'`, `'number'`, `'integer'`, or `'boolean'`), `required` property presence, string `enum`,
 primitive `const`, and the `title`/`description`/`default` annotations. Nested objects, arrays, type
@@ -127,8 +131,8 @@ fired once up front at connect time and after every effective change; serializat
 publish their root message as `errors.base` and `formError`), and no-detail `focus`/`blur` events for
 generated native text/number inputs. The composed
 `<lr-select>` controls already bubble their own focus/blur bridges through the host.
-Their implementation events (`input`, `change`, `lr-change`, select show/hide, and option mutation)
-are contained at the form boundary; consumers receive the single form-level `lr-input` contract.
+Nested control events (`input`, `change`, `lr-change`, select show/hide, and option mutation) are
+contained at the form boundary; consumers receive the single form-level `lr-input` contract.
 `lr-invalid` (no detail) is the bubbling/composed, cancelable alias emitted when the complete
 parameter form fails a native validity check; preventing it also prevents the native `invalid`
 event's default validation UI.

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

@@ -24,6 +24,10 @@ so slot-forwarding does not put a forwarding `<slot>` where a slotted `<lr-tab-g
 child scan expects real projected content, while its modal behavior participates in the shared
 overlay stack.
 
+Assigning `accessibleLabel` directly names the inner dialog when no host `aria-label` is present. A
+host `aria-label` retains its separate host ownership, and an empty direct value uses the tool
+title.
+
 **Properties:**
 
 - `open: boolean = false` (reflected) — whether the dialog is open; set it directly or use the

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

@@ -159,12 +159,11 @@ registerToolRenderer("run_query", {
   `registry` prop is set
 - `findToolRenderer(toolName: string, payload: unknown, registry?: ToolRendererRegistry):
 ToolRendererDefinition | undefined` — the dispatch function `<lr-tool-result-view>` calls
-  internally on every resolve; exposed for direct use/testing too
+  internally on every resolve; exposed for direct use too
 - `loadToolRenderer(def: ToolRendererDefinition): Promise<DirectToolRendererDefinition>` — resolves `def`
   to a definition guaranteed to carry a real `render`, awaiting/unwrapping `def.load()` when present
   (or returning `def` unchanged otherwise)
-- `clearToolRenderers(): void` — test-only utility that empties the default registry and its
-  `load()` cache, so one test's `registerToolRenderer()` calls can't leak into the next
+- `clearToolRenderers(): void` — clears the default registry and its `load()` cache
 
 **Dispatch order** (`findToolRenderer`), exactly as `<lr-tool-result-view>`'s own `resolve()` uses
 it:

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

@@ -21,6 +21,10 @@ available in a conversation. It keeps its own panel template rather than nesting
 it has no dependency on the general-purpose dialog, while its modal behavior participates in the
 shared overlay stack. First-party invention (no Web Awesome equivalent).
 
+Programmatic `selectedToolIds` and `useDefaults` replacements synchronize the live checkbox and
+switch state after user edits without emitting change events. Removing `search-placeholder` restores
+localized copy, while an explicitly empty placeholder stays empty.
+
 **Exported types:**
 
 - `ToolSelectDialogTool { id: string; name: string; description?: string; category?: string; icon?:
@@ -85,8 +89,8 @@ the desired detail values after that work succeeds. `lr-close`
 (`detail: ToolSelectDialogCloseReason` — fired exactly once per dismissal, via Escape, a backdrop
 click when `lightDismiss` is enabled, or a `close()` call), and no-detail `focus`/`blur` events
 re-dispatched when the internal search input gains or loses focus.
-Native `input`/`change` and prefixed `lr-input` implementation events from the built-in checkbox and
-switch controls stop at the dialog boundary; listen for the single aggregate `lr-change` proposal.
+Native `input`/`change` and prefixed `lr-input` events from the built-in checkbox and switch
+controls stop at the dialog boundary; listen for the single aggregate `lr-change` proposal.
 
 **Slots:** `footer` — optional action buttons (e.g. a "Done" button), rendered in a bottom row. Changes
 already apply live via `lr-change`, so this slot is purely optional; only visually shown once it has

package/llms/components/lr-tooltip.md

@@ -19,6 +19,12 @@
 A tooltip for a consumer-owned trigger, positioned with the shared Floating UI positioner. Which
 interactions open it is configurable as of 8.0.0; by default it is still hover and focus.
 
+An open lr-tooltip repositions when its effective host or inherited text direction changes,
+preserving open state without emitting lifecycle events.
+
+Removing `content` safely omits tooltip fallback text while preserving `null` property readback;
+later text renders normally.
+
 **Properties:**
 
 - `open: boolean = false` (reflected) — assigning it runs the same lifecycle as `show()`/`hide()`.

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

@@ -20,6 +20,9 @@ A collapsible span hierarchy for one agent/LLM trace (Langfuse/LangSmith run-tre
 name, status, an inline duration bar on the shared trace time scale, and optional tokens/cost
 columns. Consumes the same `LyraSpan[]` as `<lr-span-waterfall>`.
 
+Span views omit whitespace-only IDs and preserve every nonblank business ID exactly, including
+surrounding whitespace. The first valid admitted duplicate continues to win.
+
 **Properties:** `spans: LyraSpan[] = []` (attribute: false) — the same `LyraSpan` shape documented
 under `lr-span-waterfall` above (exported from `trace-tree/span.ts`); hierarchy comes from
 `parentId`, and a span whose `parentId` is missing or doesn't resolve within the same array renders

package/llms/components/lr-transcript-feed.md

@@ -21,6 +21,9 @@ with in-place upgrades keyed by `id`, and a stick-to-bottom auto-scroll with rel
 `follow`/`lr-follow-change` contract `<lr-terminal>` uses. Live captions only — recorded-media
 transcript sync is a separate concern.
 
+Activating the focused jump action resumes follow and transfers focus to the scroll base when the
+action disappears, unless a newer outside focus move takes precedence.
+
 **Properties:** `entries: LyraTranscriptEntry[] = []` (attribute: false) — `LyraTranscriptEntry { id:
 string; speaker?: string; text: string; interim?: boolean; timestamp?: LyraTimestamp }` (exported by
 this module; `LyraTimestamp = Date | string | number`, normalized through Date/TimeClip). Reconciled