@aceshooting/lyra-ui 13.0.1 → 14.1.0

package/llms/components/lr-option.md

@@ -21,6 +21,32 @@ Filterable single/multi-select combining a text input with a listbox. Mirrors th
 `<wa-combobox>` API under the `lr-` prefix. **Form-associated** (hand-rolled internals, not the
 shared `FormAssociated` mixin — see gotchas).
 
+Consumer writes on mounted options immediately update the owning picker and its submission,
+without changing the reset default or emitting picker input/change events. Owner synchronization
+does not echo as a consumer selected write.
+
+A mounted `option.selected` assignment updates the live picker value and form submission
+immediately, including deselection and equal-value writes; it emits no user input/change event.
+
+When `multiple` becomes false, the public value, live option flags, and popup `aria-selected` expose
+one selected occurrence. The retained multiple-selection history returns if multiple is enabled
+again without another selection write.
+
+Composing keyboard events (`isComposing` or legacy key code 229) remain with filter editing; they do
+not navigate, select/create a value, or dismiss the popup.
+
+Source options with `inert`, including inherited inertness, are unavailable through the popup. Live
+inert changes refresh row availability. Text, insertion, replacement, removal, slot
+reassignment/removal, and relevant attributes of `start`/`end`/`prefix`/`suffix` adornments refresh
+the corresponding cloned presentation; unchanged presentation retains its clone identity while
+filtering.
+
+Host `aria-describedby` resolves external descriptions onto the native combobox filter before local
+error/hint guidance. References track missing targets, replacement, removal/reinsertion, reconnect,
+and adoption. Removing `label`, `hint`, or `error-text` safely omits the content while leaving
+removed string properties at their native `null` readback; explicit empty strings remain supplied
+empty strings.
+
 **First-interaction registration.** Where initial-route weight is stricter than a static combobox
 registration allows, keep a labelled native `<input list>` as the working pre-JavaScript control
 and import only the granular combobox registration on its first focus. Copy the native value after
@@ -206,9 +232,12 @@ AbortSignal; limit: number }) => Promise<readonly ComboboxSourceRow[] | { rows,
 - `value: string | string[]` — a getter/setter: plain `string` in single mode, `string[]` in
   `multiple` mode
 - `customError: string | null` (attribute `custom-error`) — reflected consumer validation message
-- `selectedRows: ComboboxSourceRow[]` (read-only getter) — structured rows for the current
-  selection, including any opaque `data` payload supplied by an async source. Selected async rows
-  remain available after the query changes or a later source result no longer contains them
+- `selectedRows` (read: `ComboboxSourceRow[]`; write: `readonly ComboboxSourceRow[]`) — structured
+  rows for the current selection, including any opaque `data` payload supplied by an async source.
+  Reads return detached row snapshots. Writes select stable row values resolved against the
+  current or deferred source, dropping duplicate and detached values without emitting selection
+  events. Selected async rows remain available after the query changes or a later source result
+  no longer contains them
 - `selectionStart`, `selectionEnd`, and `selectionDirection` — selection getters/setters forwarded
   to the internal input
 
@@ -264,7 +293,9 @@ selection. It is the supported way to read that text; reaching into the shadow r
 `[part="combobox-input"]`'s value is not. Named `lr-filter` rather than `lr-input` precisely because
 `lr-input`'s detail on `<lr-input>` is the committed value, and the two must not share a name while
 carrying different strings. It fires for user edits only. Picking a row, `form.reset()`, dismissing
-the listbox, a programmatic `value` write, and `setRangeText()` blank the filter silently.
+the listbox, and a programmatic `value` write blank the filter silently. `setRangeText()` silently
+replaces the requested or selected native text range, synchronizes the resulting query and visible
+options, and refreshes an async source when present; it preserves the committed selection.
 Activating the clear button is a user edit: when a query existed it emits `lr-filter` with
 `value: ''` before the clear transaction finishes.
 `lr-show` and `lr-hide` report the start of listbox visibility transitions. `lr-show` is a

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

@@ -19,6 +19,16 @@
 A form-associated one-time-code field: several character segments that together hold one value.
 Mirrors `wa-otp-input`.
 
+Host `aria-describedby` references resolve onto the native control input before its local error and
+hint guidance. The relationship tracks missing IDs, target replacement, removal/reinsertion,
+reconnect, and document adoption. The decorative code segments do not receive a second copy of the
+descriptions.
+
+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.
+
 The segments are **presentational**. A single real `<input>` sits transparently across them and owns
 focus, selection and the value. It remains the native integration point for SMS autofill
 (`autocomplete` defaults to `one-time-code`), IME composition and mobile keyboards, and keeps the

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-pie-chart.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** `chart.js`, `chartjs-plugin-annotation`, `chartjs-plugin-datalabels`, `chartjs-plugin-zoom` — see `llms/peers.md`
-- **Themeable via** 16 parts, 35 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 16 parts, 36 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Documented with** `lr-line-chart`, `lr-bar-chart`, `lr-doughnut-chart`, `lr-radar-chart`, `lr-polar-area-chart`, `lr-bubble-chart`, `lr-scatter-chart` (same section below)
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
@@ -58,7 +58,7 @@ failure transition is announced through the shared document-level light-DOM asse
 `--lr-chart-data-table-button-active-bg`, `--lr-chart-data-table-toggle-hover-bg`,
 `--lr-chart-data-table-toggle-active-bg`, `--lr-chart-reset-zoom-button-hover-bg`,
 `--lr-chart-reset-zoom-button-active-bg`, `--lr-chart-canvas-hover-outline-width`, and
-`--lr-chart-pattern-step`, plus `--lr-chart-legend-side-max` — all inherited from `LyraChart`, identical in meaning and default (see
+`--lr-chart-canvas-hover-outline-color`, `--lr-chart-pattern-step`, plus `--lr-chart-legend-side-max` — all inherited from `LyraChart`, identical in meaning and default (see
 `lr-chart` above); each of the eight variants below reads the same set, so one rule retunes them
 together. The mirrored hooks are `--border-color-1`,
 `--border-color-2`, `--border-color-3`, `--border-color-4`, `--border-color-5`,

package/llms/components/lr-polar-area-chart.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** `chart.js`, `chartjs-plugin-annotation`, `chartjs-plugin-datalabels`, `chartjs-plugin-zoom` — see `llms/peers.md`
-- **Themeable via** 16 parts, 35 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 16 parts, 36 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Documented with** `lr-line-chart`, `lr-bar-chart`, `lr-pie-chart`, `lr-doughnut-chart`, `lr-radar-chart`, `lr-bubble-chart`, `lr-scatter-chart` (same section below)
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
@@ -58,7 +58,7 @@ failure transition is announced through the shared document-level light-DOM asse
 `--lr-chart-data-table-button-active-bg`, `--lr-chart-data-table-toggle-hover-bg`,
 `--lr-chart-data-table-toggle-active-bg`, `--lr-chart-reset-zoom-button-hover-bg`,
 `--lr-chart-reset-zoom-button-active-bg`, `--lr-chart-canvas-hover-outline-width`, and
-`--lr-chart-pattern-step`, plus `--lr-chart-legend-side-max` — all inherited from `LyraChart`, identical in meaning and default (see
+`--lr-chart-canvas-hover-outline-color`, `--lr-chart-pattern-step`, plus `--lr-chart-legend-side-max` — all inherited from `LyraChart`, identical in meaning and default (see
 `lr-chart` above); each of the eight variants below reads the same set, so one rule retunes them
 together. The mirrored hooks are `--border-color-1`,
 `--border-color-2`, `--border-color-3`, `--border-color-4`, `--border-color-5`,

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-input.md

@@ -34,6 +34,7 @@ request. `label` names the prompt section; it is not generic field chrome.
 `autocomplete: string = ''`, `inputMode: string = ''` (attribute `inputmode`), and
 `enterKeyHint: string = ''` (attribute `enterkeyhint`) forward unchanged to the composed native
 textarea; empty string hints preserve the browser default.
+Invalid `status` values read as `idle` without rewriting the host attribute.
 `attachments: readonly LyraPromptInputAttachment[] = []` — `attachmentId` must be nonempty and
 unique; malformed rows and later duplicates are omitted first-wins before rendering and attachment
 events, and surviving chips reconcile by `attachmentId`. `attachmentCapabilities: readonly
@@ -89,9 +90,12 @@ replaces the built-in composer action.
 **Themeable custom properties:** `--lr-prompt-input-control-width` (default `--lr-size-12rem`) is
 the preferred width of each generated model, voice, and source control before wrapping.
 
-Mention-popover focus transfer is generation-guarded: closing, disabling, disconnecting, adopting,
-or replacing the query/data before its awaited focus step prevents stale focus. Empty `chips` and
-`footer` wrappers are not rendered, so an absent optional region cannot create phantom spacing.
+An open mention or command popup remains open only while focus is in the primary textarea or that
+popup; moving focus to another prompt control or outside closes it. Arrow keys move focus to the
+active option. Enter or Tab accepting an option is handled before textarea submission. Escape
+restores the textarea's prior ARIA and selection. If the popup closes, becomes unavailable, or its
+input/items change before focus moves, no move occurs. Empty `chips` and `footer` wrappers are not rendered, so an absent optional region cannot
+create phantom spacing.
 
 **Optional peer deps:** none of its own.
 

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

@@ -33,6 +33,12 @@ Item ids are occurrence identities. Empty ids and later duplicates are ignored b
 proposing a mutation, preserving one unambiguous `itemId`. Attachment names render visibly for both
 editable and read-only rows; the host `label` is also the visible queue heading.
 
+Supported item and attachment fields are read once when `items` is assigned; create and reassign a
+new collection after changes, because changing an assigned record or reassigning the same mutated
+array does not update the view. Rows or attachments without valid direct data are ignored. Duplicate IDs are resolved
+after validation, so the first valid item wins. `metadata` is opaque and retains identity in
+proposed queue/send-now payloads, while emitted items are new frozen snapshots.
+
 **Events:** `lr-queue-change` (`PromptQueueChangeDetail = { items, reason, itemId }`, with
 `reason: 'edit' | 'remove' | 'reorder'`), `lr-send-now` (`{ item }`). The queue is controlled:
 these events propose complete next values without mutating `items`.

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.
 
@@ -50,6 +53,11 @@ setting it to `0` removes the deadline.
 **Methods:** `start()`, `stop()`, and `cancel()` drive the capture lifecycle imperatively (mirroring
 the pointer/keyboard gestures).
 
+After permission is requested, only a still-active control in the same document may begin
+recording; otherwise any stream returned later is immediately stopped. In hold mode, a later held
+press in that document can take over one pending permission request, and a held press while
+stopping begins after the prior take ends. Only one capture runs at a time.
+
 **Slots:** `microphone-icon` replaces the default mic glyph. `recording-icon` replaces the default
 recording-state pulse glyph. Both are
 decorative inside the named trigger: their flattened content is inert and hidden from accessibility

package/llms/components/lr-qr-code.md

@@ -41,6 +41,12 @@ generation-guarded, including across disconnect/reconnect.
 `LyraQrCode.preload(): Promise<boolean>` is a static optional-peer warm-up that starts the shared
 `qrcode` import without encoding a value; it resolves to `false` when the peer is unavailable.
 
+When `IntersectionObserver` is available, painting waits for a valid intersecting entry and resumes
+whenever the code re-enters view. If the API is unavailable, its constructor fails, or `observe()`
+throws, rendering proceeds immediately. Invalid resolved paint colors fall back to the documented
+safe fill/background without changing the QR's loading or error state: foreground becomes black,
+background becomes transparent, and `imageBackground` becomes the resolved QR background.
+
 At ordinary sizes the backing store is a fixed `2×` the CSS size, independent of device pixel
 ratio. It degrades uniformly only to stay within 4,096 pixels per dimension and 8,388,608 total
 pixels. Modules span the full canvas with no injected quiet zone; add host padding when a scanner

package/llms/components/lr-radar-chart.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** `chart.js`, `chartjs-plugin-annotation`, `chartjs-plugin-datalabels`, `chartjs-plugin-zoom` — see `llms/peers.md`
-- **Themeable via** 16 parts, 35 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 16 parts, 36 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Documented with** `lr-line-chart`, `lr-bar-chart`, `lr-pie-chart`, `lr-doughnut-chart`, `lr-polar-area-chart`, `lr-bubble-chart`, `lr-scatter-chart` (same section below)
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
@@ -58,7 +58,7 @@ failure transition is announced through the shared document-level light-DOM asse
 `--lr-chart-data-table-button-active-bg`, `--lr-chart-data-table-toggle-hover-bg`,
 `--lr-chart-data-table-toggle-active-bg`, `--lr-chart-reset-zoom-button-hover-bg`,
 `--lr-chart-reset-zoom-button-active-bg`, `--lr-chart-canvas-hover-outline-width`, and
-`--lr-chart-pattern-step`, plus `--lr-chart-legend-side-max` — all inherited from `LyraChart`, identical in meaning and default (see
+`--lr-chart-canvas-hover-outline-color`, `--lr-chart-pattern-step`, plus `--lr-chart-legend-side-max` — all inherited from `LyraChart`, identical in meaning and default (see
 `lr-chart` above); each of the eight variants below reads the same set, so one rule retunes them
 together. The mirrored hooks are `--border-color-1`,
 `--border-color-2`, `--border-color-3`, `--border-color-4`, `--border-color-5`,

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
@@ -46,6 +49,11 @@ associated external label focuses the host-owned slider without changing its val
 property is visible label text, since a rating is a bare row of symbols with no field frame of its
 own; wrap the element in your own layout for a labelled field, exactly as `<lr-slider>` does.
 
+For the managed slider name only, an empty or whitespace-only `label` counts as absent and falls
+through to localized `rating`; the raw `label` property still reads exactly as assigned. An
+associated external label and an authored `aria-label`, including `aria-label=""`, keep their
+existing precedence and are never replaced by that fallback.
+
 **Static constructor API:** `LyraRating.validators` is the mirrored callable validator catalog.
 Each access returns a fresh `LyraFormValidator<LyraRating>[]`; its entry observes
 `required`/`disabled`/`readonly`/`value`/`max`, and `checkValidity(element)` projects the element's

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

@@ -37,3 +37,5 @@ are as described under `lr-format-number` above.
 
 Valid output is semantic `<time datetime="…">`. **Slots:** none — an unparseable `date` renders the
 empty string, with no fallback-content hook (unlike the three `lr-format-*` components above).
+Date input accepts primitive strings/numbers or a genuine `Date`; arbitrary objects are rejected
+without calling their conversion hooks.

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.
@@ -114,8 +117,8 @@ around either the slotted content or the plain `value` text).
 
 - `HTMLElement.textContent` read on a shadow-DOM wrapper containing a `<slot>` does NOT include the
   slot's assigned/projected light-DOM content — only literal fallback children of the `<slot>` tag
-  itself (there are none here). Asserting against `[part="value"]`'s own `.textContent` to check
-  rendered slotted content will read as empty even when the component is rendering correctly;
-  assert against the slot's `assignedNodes()`/`assignedElements()` instead.
+  itself (there are none here). Reading `[part="value"]`'s own `.textContent` yields an empty value
+  even when slotted content is rendering correctly; use the slot's
+  `assignedNodes()`/`assignedElements()` instead.
 
 ---

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.
@@ -114,8 +117,8 @@ around either the slotted content or the plain `value` text).
 
 - `HTMLElement.textContent` read on a shadow-DOM wrapper containing a `<slot>` does NOT include the
   slot's assigned/projected light-DOM content — only literal fallback children of the `<slot>` tag
-  itself (there are none here). Asserting against `[part="value"]`'s own `.textContent` to check
-  rendered slotted content will read as empty even when the component is rendering correctly;
-  assert against the slot's `assignedNodes()`/`assignedElements()` instead.
+  itself (there are none here). Reading `[part="value"]`'s own `.textContent` yields an empty value
+  even when slotted content is rendering correctly; use the slot's
+  `assignedNodes()`/`assignedElements()` instead.
 
 ---

package/llms/components/lr-retrieval-results.md

@@ -25,7 +25,7 @@ text verbatim. Large sets window through an internal `lr-virtual-list`.
 **Properties:**
 
 - `chunks: RetrievalChunk[] = []` (attribute: false) — **`RetrievalChunk`, imported from
-  `@aceshooting/lyra-ui/ai`** (`src/ai/types.ts`): `{ id: string; text: string; score: number;
+  `@aceshooting/lyra-ui/ai`**: `{ id: string; text: string; score: number;
 source: DocumentRef; metadata?: Record<string, unknown>; rank?: number; locator?: DocumentLocator;
 queryId?: string; stage?: string; traceId?: string; scores?: RetrievalScoreBreakdown }`. The raw,
   unsorted/ungrouped result set; host-owned. Blank ids and later duplicate ids are omitted

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-scatter-chart.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** `chart.js`, `chartjs-plugin-annotation`, `chartjs-plugin-datalabels`, `chartjs-plugin-zoom` — see `llms/peers.md`
-- **Themeable via** 16 parts, 35 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 16 parts, 36 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Documented with** `lr-line-chart`, `lr-bar-chart`, `lr-pie-chart`, `lr-doughnut-chart`, `lr-radar-chart`, `lr-polar-area-chart`, `lr-bubble-chart` (same section below)
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
@@ -58,7 +58,7 @@ failure transition is announced through the shared document-level light-DOM asse
 `--lr-chart-data-table-button-active-bg`, `--lr-chart-data-table-toggle-hover-bg`,
 `--lr-chart-data-table-toggle-active-bg`, `--lr-chart-reset-zoom-button-hover-bg`,
 `--lr-chart-reset-zoom-button-active-bg`, `--lr-chart-canvas-hover-outline-width`, and
-`--lr-chart-pattern-step`, plus `--lr-chart-legend-side-max` — all inherited from `LyraChart`, identical in meaning and default (see
+`--lr-chart-canvas-hover-outline-color`, `--lr-chart-pattern-step`, plus `--lr-chart-legend-side-max` — all inherited from `LyraChart`, identical in meaning and default (see
 `lr-chart` above); each of the eight variants below reads the same set, so one rule retunes them
 together. The mirrored hooks are `--border-color-1`,
 `--border-color-2`, `--border-color-3`, `--border-color-4`, `--border-color-5`,

package/llms/components/lr-scroller.md

@@ -31,11 +31,11 @@ well as full-width layouts.
 - `scrollStep: number = 0` (attribute `scroll-step`) — custom step; zero uses 80% of the viewport
 - `label: string = ''` — accessible region name; a host `aria-label` is used when set
 
-**Events:** `lr-scroll` with `scrollStart`, `scrollEnd`, `scrollLeft`, and `scrollTop` in the
-detail object. Scroll-driven emissions are coalesced through one `requestAnimationFrame` tick, so a
-fling that fires dozens of native `scroll` events produces at most one `lr-scroll` per frame — the
-same contract `lr-virtual-list`'s identically-named event carries, so the two are interchangeable
-for scroll-linked layout work.
+**Events:** `lr-scroll` has detail `{ scrollStart, scrollEnd, scrollLeft, scrollTop }`.
+Scroll-driven emissions are coalesced through one `requestAnimationFrame` tick, so a fling that
+fires dozens of native `scroll` events produces at most one `lr-scroll` per frame. This is the
+scroller's own event shape, not `lr-virtual-list`'s `lr-virtual-scroll` event
+(`{ scrollTop, viewportHeight }`).
 
 **Slots:** default scrollable content.
 

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`)
@@ -93,8 +97,7 @@ dimming at `itemCount <= 1`), `--lr-focus-ring-*`.
   `currentIndex` clamped into `[0, itemCount)`; fractional, negative, `NaN`, infinite, and oversized
   values cannot poison end conditions or the slider.
 - `interval-ms` is clamped to the 16ms floor and the browser's finite timer ceiling: a non-finite or
-  lower value ticks at 16ms, while an oversized value uses the timer ceiling. Each distinct invalid
-  value is warned once (deduplicated per value, not a single once-ever flag).
+  lower value ticks at 16ms, while an oversized value uses the timer ceiling.
 - Initial `playing` and `item-count` attributes are resolved together on the first update, so
   playback starts consistently regardless of their source order; an invalid final `itemCount <= 1`
   clears the reflected `playing` state.