@aceshooting/lyra-ui 14.0.0 → 14.1.1

package/llms/components/lr-pan-zoom.md

@@ -29,8 +29,7 @@ import to `LyraPanZoom`); `lr-zoomable-frame` now means the mapped iframe compon
   as absent and the default slot renders; no empty or unsafe `<img>` replaces that fallback.
 - `accessibleLabel: string | null` (attribute `aria-label`) — a declarative host label remains on
   the host while the focusable viewport receives the localized inspection-surface purpose name.
-  A property-only value can name the viewport. This avoids cloning one author label onto both the
-  outer component and nested `role="group"`.
+  A property-only value names the viewport and updates reactively without creating a host attribute. This avoids cloning one author label onto both the outer component and nested `role="group"`. An explicitly empty direct property remains empty; a present host attribute, including an empty one, leaves the viewport's localized purpose name intact.
 
 **Methods:** `zoomIn()`, `zoomOut()`, and `resetZoom()` update zoom and emit `lr-zoom-change`
 (`detail: { zoom }`). `resetZoom()` preserves pan; `resetView()` also scrolls the viewport to the

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

@@ -24,6 +24,14 @@ with `loadLibphonenumberAdapter()`. Without an adapter, already-international E.
 normalizes and validates; national input remains editable with `incomplete` validity. The loader
 returns its discovered country catalog as a frozen array of frozen records.
 
+For `default-country`, removing the attribute safely uses the existing country fallback while
+leaving property   readback at native `null`; an existing selected country remains selected.
+Explicit empty   strings remain empty, and later valid default-country values work normally.
+
+Host `aria-describedby` references resolve onto the telephone input before its local hint/error
+guidance. References track missing IDs, target replacement, removal/reinsertion, reconnect, and
+adoption. The country selector keeps its separate existing accessible-name contract.
+
 The country selector keeps the real native `<select>` (localized full country names in its popup,
 native mobile pickers, keyboard type-ahead) but stretches it invisibly over a compact decorative
 trigger showing the selected alpha-2 code plus a design-system chevron — long country names never
@@ -123,13 +131,20 @@ null` (attribute `custom-error`) carries a consumer-supplied validation message.
   removes it from the accessibility tree entirely.)
 - `phoneLabel: string = ''` (attribute `phone-label`) — explicit accessible-name override for the
   native telephone input.
-- `countryLabel: string = 'Select'` (attribute `country-label`) — country-selector accessible name;
-  the untouched default routes through the shared localized `select` message.
+- `countryLabel: string = 'Select'` (attribute `country-label`) — country-selector accessible name.
+  Omitted copy uses the localized `select` message. Explicit text, including `'Select'` and `''`,
+  wins over locale strings. Removing the attribute restores the declared `'Select'` property
+  readback and resumes localization.
 - `incompleteText: string = 'This phone number is incomplete.'` (attribute `incomplete-text`) —
-  validation message for dial-like input that can still become valid with more digits. The
-  untouched default routes through the localized `phoneInputIncomplete` message.
+  validation message for dial-like input that can still become valid with more digits. Omitted
+  copy uses the localized `phoneInputIncomplete` message. Explicit nonempty text, including the
+  English default, wins verbatim; an empty override retains the localized native error reason.
+  Removing the attribute restores its declared English property default and resumes localization.
 - `invalidText: string = 'The value is invalid.'` (attribute `invalid-text`) — completed-invalid
-  message, localized through the same shared key while left at its default.
+  validation message. Omitted copy uses localized `valueInvalid`; explicit nonempty text,
+  including the English default, wins verbatim. An empty override retains the localized native
+  error reason. Removing the attribute restores its declared English property default and resumes
+  localization.
 - `autocomplete: string = 'tel'`, `inputmode: 'tel'|'numeric'|'text' = 'tel'`,
   `enterkeyhint: string = ''` — forwarded to the internal `<input type="tel">`.
 - `readonly: boolean = false` (reflected) — forwards to the native telephone input, locks the

package/llms/components/lr-poll-status.md

@@ -23,6 +23,10 @@ First-party invention (no Web Awesome equivalent); the closest existing componen
 scheduled-interval countdown — this mirrors its internal `<lr-live-region>` composition for
 accessible phase-transition announcements.
 
+Long localized status labels, including unbroken words, wrap within the component’s allocated inline
+size in LTR and RTL. The indicator and pause/resume action retain their size; the 320px example
+shows both inactive and refreshing states.
+
 **Properties:**
 
 - `nextInMs?: number` (attribute `next-in-ms`) — milliseconds until the next scheduled action, as of

package/llms/components/lr-popover.md

@@ -18,6 +18,9 @@
 
 A click-triggered, light-dismiss floating surface positioned with the shared Floating UI positioner.
 
+An open lr-popover repositions when its effective host or inherited text direction changes,
+preserving open state without emitting lifecycle events.
+
 **First-interaction registration.** A performance-sensitive navigation shell can keep a native
 `<details>` disclosure working before JavaScript, then load only the granular popover registration
 when that fallback first opens. The interaction that starts an async import is not replayed after

package/llms/components/lr-popup.md

@@ -48,8 +48,9 @@ replacement and transfer, plus direct and forwarded slot changes, are tracked li
   under RTL. The shared positioner's physical coordinates remain authoritative in either
   direction, so RTL never stretches a fixed-width popup against an opposite logical inset.
 - `strategy: 'absolute' | 'fixed' = 'absolute'` (reflected) — the CSS positioning scheme. `fixed`
-  escapes every ancestor transform/filter/containment context; `absolute` positions against the
-  nearest positioned ancestor, so the popup scrolls with its containing content
+  normally positions relative to the viewport, but ancestors using transforms, filters or
+  containment can establish a different containing block, and ancestor clipping may still apply.
+  `absolute` positions relative to its containing block and scrolls with its containing content.
 - `distance: number = 0` — offset from the anchor along the placement axis, in px
 - `skidding: number = 0` — offset along the anchor's edge, in px
 - `flip: boolean = false` (not reflected), with `flipFallbackPlacements: string = ''` (attribute

package/llms/components/lr-prompt-studio.md

@@ -21,6 +21,13 @@ versions, resolved preview, and save/run intents. Message and variable edits emi
 `lr-change` proposal carrying their complete next state before updating the component's current
 arrays; persistence and execution remain host-owned.
 
+Variable values resolve recursively; undefined and cyclic placeholders remain literal within preview
+bounds. Each preview projection permits at most 64 nested variable resolutions, 10,000 placeholder
+substitutions, and 1,048,576 UTF-16 code units each of aggregate resolved message output and
+aggregate memoized intermediate text. Limits are checked before constructing oversized text.
+Exceeding a limit replaces the resolved preview with a localized visible fallback; raw messages,
+variables, editing and save/run payloads are unchanged.
+
 **Properties:** `messages: readonly PromptStudioMessage[] = []` and
 `variables: readonly PromptStudioVariable[] = []` are property-only editor state: user edits emit a
 cancelable `lr-change` before updating the current arrays, while the host remains responsible for

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

@@ -20,6 +20,9 @@ The grounding breakdown for one answer: a sectioned disclosure panel (Entities /
 Communities / Text chunks) composing this family's own pieces. The chat ↔ graph ↔ document glue
 component. Pure projection + event conduit: no fetching, no graph/viewer imports, no persistence.
 
+Malformed type rows are ignored during lookup, preserving valid later matching records and the
+existing immutable collection ownership.
+
 **Properties:**
 
 - `provenance: LyraProvenance | null = null` (attribute: false) — `LyraProvenance { entities?:

package/llms/components/lr-push-to-talk.md

@@ -22,6 +22,9 @@ microphone — no SDK, no LiveKit/ElevenLabs import, native browser APIs only. `
 default) is a press-and-hold gesture; `mode="toggle"` is click-to-start/click-to-stop with
 `aria-pressed`. Escape cancels the in-progress take in either mode.
 
+For example, `<lr-push-to-talk><span slot="microphone-icon">MIC</span></lr-push-to-talk>` replaces
+the idle microphone glyph. Use `recording-icon` separately for the recording state.
+
 While recording, the optional elapsed timer uses the effective locale's decimal digits, suppresses
 grouping, and pads its seconds field to two locale-aware digits.
 

package/llms/components/lr-radio-button.md

@@ -19,15 +19,24 @@
 The same single-choice control as `lr-radio`, rendered as a button instead of a circle. Mirrors
 `sl-radio-button`.
 
+An explicit live `checked` assignment marks the state dirty even if its boolean value is unchanged.
+For example, assigning `checked = false` to an already-unchecked radio prevents a later
+`defaultChecked = true` from selecting it until form reset. Pristine default propagation and
+owning-group normalization retain their existing behavior.
+
+Host `aria-describedby` references resolve onto the internal `role="radio"`, tracking unresolved
+IDs, target replacement/removal/reinsertion, reconnect, and document adoption. The same behavior
+applies to the button appearance of `lr-radio`.
+
 Deliberately a **subclass of `LyraRadio`**: form association, validity, `form.reset()` restoration
 and the whole `lr-radio-group` ownership/roving-focus contract are inherited rather than
 reimplemented, so the two can never drift apart. Only the chrome differs. A `lr-radio-group` accepts
 either tag and the two can be mixed in one group.
 
-Consecutive `lr-radio-button` siblings collapse their shared borders into one segmented control
-automatically, via `:host(:first-of-type)` / `:host(:last-of-type)` — `:of-type` counts only
-`lr-radio-button` siblings, so a group's `slot="label"`/`slot="hint"` children never shift the ends,
-and nothing has to be set on the group. A lone button matches both ends and comes out fully rounded.
+Inside a horizontal `lr-radio-group`, measured adjacent runs of `lr-radio-button` controls merge
+their touching borders and retain rounded outer corners. Separated or mixed controls, vertical
+layouts, wrapped rows and standalone buttons keep the corners appropriate to their actual layout;
+label and hint slots do not determine the segment endpoints.
 
 Standalone button chrome is allocation-safe too: unbroken labels wrap, and start/end (or retained
 prefix/suffix) adornments are each capped and truncate rather than widening the containing panel.

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

@@ -21,6 +21,11 @@ A labeled, keyboard-navigable group of `lr-radio` controls. Home/End and the ori
 axis move focus and select the next enabled radio: Up/Down when vertical, Left/Right when
 horizontal. Horizontal direction mirrors under RTL, and disabled options are skipped.
 
+Host `aria-describedby` references resolve onto the internal `role="radiogroup"` before its local
+hint/error guidance. References track unresolved IDs, target replacement/removal/reinsertion,
+reconnect, and document adoption. Group descriptions remain on the group; child radios can carry
+their own separately authored descriptions.
+
 **Properties:** `label`, `hint`, `helpText` (`help-text`, Shoelace alias), `errorText`
 (`error-text`), `name` (empty by default, with the empty attribute omitted), live `value`, reflected
 `defaultValue` (attribute `value`; Shoelace's `default-value` is also accepted), `customError`

package/llms/components/lr-radio.md

@@ -18,6 +18,15 @@
 
 A form-associated single-choice control. Use it alone or inside `lr-radio-group`.
 
+An explicit live `checked` assignment marks the state dirty even if its boolean value is unchanged.
+For example, assigning `checked = false` to an already-unchecked radio prevents a later
+`defaultChecked = true` from selecting it until form reset. Pristine default propagation and
+owning-group normalization retain their existing behavior.
+
+Host `aria-describedby` references resolve onto the internal `role="radio"`, tracking unresolved
+IDs, target replacement/removal/reinsertion, reconnect, and document adoption. The same behavior
+applies to the button appearance of `lr-radio`.
+
 **Properties:** live, non-reflecting `checked`; reflected `defaultChecked` (attribute `checked`);
 reflected `customError: string | null` (attribute `custom-error`); `disabled`, `required`, `name`,
 and `value`. A selected standalone radio submits its value through `ElementInternals`.

package/llms/components/lr-rating.md

@@ -21,6 +21,9 @@ that lives in this family rather than in `components/forms/` — if you came loo
 form controls, this is its section. Everything the "Form association" section says about `name`,
 submission, validity and the `user-*` custom states applies to it.
 
+Readonly transitions synchronize validity and `aria-invalid` in the same completed update. Form
+reset restores the independent `default-value` rather than the live `value` attribute.
+
 It is form-associated through `ElementInternals` directly rather than through the shared
 `FormAssociated` mixin, because its `value` is a number and the mixin's contract assumes a plain
 string — routing through it would force every consumer into string round-tripping for what is

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

@@ -27,6 +27,12 @@ own splice/resort logic. `lr-reorder` is cancelable — a listener calling `prev
 the move open (mirroring `lr-confirm-bar`'s cancelable approve/deny pattern) until the host calls
 `finalizePendingMove()`/`revertPendingMove()`.
 
+Direct item `value` property or attribute edits refresh the owning list's valid identities and
+movement boundaries. Correcting a missing or duplicate identity re-enables the corresponding
+controls; making it invalid disables them. Identity edits do not emit a reorder event. Removing the
+value attribute from a standalone item renders it as absent while preserving `null` readback; an
+explicit empty string remains supplied and later valid values recover.
+
 ### `lr-reorder-list`
 
 **Properties:**

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

@@ -27,6 +27,12 @@ own splice/resort logic. `lr-reorder` is cancelable — a listener calling `prev
 the move open (mirroring `lr-confirm-bar`'s cancelable approve/deny pattern) until the host calls
 `finalizePendingMove()`/`revertPendingMove()`.
 
+Direct item `value` property or attribute edits refresh the owning list's valid identities and
+movement boundaries. Correcting a missing or duplicate identity re-enables the corresponding
+controls; making it invalid disables them. Identity edits do not emit a reorder event. Removing the
+value attribute from a standalone item renders it as absent while preserving `null` readback; an
+explicit empty string remains supplied and later valid values recover.
+
 ### `lr-reorder-list`
 
 **Properties:**

package/llms/components/lr-result-card.md

@@ -23,6 +23,9 @@ label/value row" visual language, without each one hand-rolling its own box. Nei
 any code dependency on the tool-result-view registry itself — they're generically usable anywhere a
 small card/field shell is useful.
 
+Removing `heading` or a result field `label` hides that text while preserving the card actions and
+field value.
+
 ### `lr-result-card`
 
 A small bordered card shell. Purely visual, with no state of its own beyond slot-presence tracking.

package/llms/components/lr-result-field.md

@@ -23,6 +23,9 @@ label/value row" visual language, without each one hand-rolling its own box. Nei
 any code dependency on the tool-result-view registry itself — they're generically usable anywhere a
 small card/field shell is useful.
 
+Removing `heading` or a result field `label` hides that text while preserving the card actions and
+field value.
+
 ### `lr-result-card`
 
 A small bordered card shell. Purely visual, with no state of its own beyond slot-presence tracking.

package/llms/components/lr-rubric-form.md

@@ -26,6 +26,18 @@ and error chrome is linked to that same-shadow role. A host `aria-label` wins by
 Both score branches format visible numeric labels with the effective locale (including non-Latin
 digits); segmented item values and submitted rubric values remain stable raw numbers/strings.
 
+Host `aria-describedby` references resolve in the host's root and precede local hint/error guidance
+on that aggregate group. Target replacement, removal, reinsertion, reconnection and document
+adoption keep the relationship current. Aggregate guidance is not copied to every child field; each
+retains its own description/error ownership. Removing `label` or `hint` safely removes the copy
+while retaining native attribute-removal property readback, including `null`; explicit empty and
+later replacement strings remain supported.
+
+Replacing `value` after a multiple-category user edit reconciles the actual checkbox checked states,
+group value and submitted JSON, including when replacement happens in the same task. These parent
+writes use live child state, leave child reset-default/dirty semantics intact, and emit no user-edit
+events.
+
 **Properties:** `keys: readonly RubricKey[] = []` (attribute: false), where the exported immutable
 discriminated union is `ScoreRubricKey | CategoryRubricKey | CommentRubricKey`. Keys use nonblank
 first-wins identity and retained valid spelling is not rewritten. Shared fields are

package/llms/components/lr-select.md

@@ -27,6 +27,15 @@ Session-history/autofill restoration assigns the stored string through the same
 value/form/validity path as a programmatic value write and does not emit `input`, `change`, or
 `lr-change`.
 
+Mounted `option.selected` assignments update the picker value and form submission immediately,
+including deselection and equal-value writes. Duplicate-valued options retain their individual
+occurrence identities. These programmatic writes emit no user input/change event.
+
+Host `aria-describedby` resolves external guidance onto the trigger before internal value, error,
+and hint guidance. References track missing targets, replacement, removal/reinsertion, reconnect,
+and adoption. Removing `label`, `hint`, `help-text`, or `error-text` safely omits the content
+without changing native `null` property readback; explicit empty strings remain empty.
+
 There is no typing-to-filter and no `filter`/`source`/`empty-text`/`max-render` surface — reach for
 `<lr-combobox>` instead whenever any of those apply. Everything else a closed list needs is here:
 `multiple`, `max-options-visible`, `with-clear`, `getTag`, `placement`, `appearance`, and `pill`.

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

@@ -19,6 +19,10 @@
 Steps a current index through `[0, itemCount)` on a fixed interval — explicit discrete-sequence
 playback for time-series scrubbing, without implying native audio/video playback.
 
+When fewer than two items are available, the disabled play button retains its resting border and
+background under hover and press. Enabled playback controls retain their token-driven pointer
+feedback.
+
 **Properties:**
 
 - `itemCount: number = 0` (attribute `item-count`)

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
@@ -114,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-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

@@ -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.

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-thread-list.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
@@ -84,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) =>

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 —