@aceshooting/lyra-ui 14.0.0 → 14.1.1

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

@@ -24,6 +24,10 @@ and animated panel. The two components intentionally keep distinct vocabularies:
 use `expanded`, `label`, and `expand()`/`collapse()`/`toggle()`, while `open`, `summary`, and
 `show()`/`hide()` belong only to Details.
 
+`lr-toggle` reports the direction and source of an accepted Details transition. Accordion
+coordinates only its direct `lr-accordion-item` children; Details retains independent state and
+optional grouping through a shared non-empty `name`.
+
 **Breaking in 9.0.0:** an accordion coordinates direct `lr-accordion-item` children only. Direct
 `lr-details` panels used to be accepted as well; they are not any more. A `lr-details` slotted into
 an accordion today is ordinary content owning its own disclosure lifecycle — the group applies

package/llms/components/lr-accordion.md

@@ -24,6 +24,10 @@ and animated panel. The two components intentionally keep distinct vocabularies:
 use `expanded`, `label`, and `expand()`/`collapse()`/`toggle()`, while `open`, `summary`, and
 `show()`/`hide()` belong only to Details.
 
+`lr-toggle` reports the direction and source of an accepted Details transition. Accordion
+coordinates only its direct `lr-accordion-item` children; Details retains independent state and
+optional grouping through a shared non-empty `name`.
+
 **Breaking in 9.0.0:** an accordion coordinates direct `lr-accordion-item` children only. Direct
 `lr-details` panels used to be accepted as well; they are not any more. A `lr-details` slotted into
 an accordion today is ordinary content owning its own disclosure lifecycle — the group applies

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

@@ -19,6 +19,9 @@
 Provider-neutral agent/LLM trace view combining span-kind filters, handoff quick-jumps, and a
 hierarchical trace tree from one shared `spans` array.
 
+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 full, unfiltered array; identical contract to

package/llms/components/lr-animation.md

@@ -18,6 +18,10 @@
 
 Declaratively animates one slotted element through the native Web Animations API.
 
+An initial playing mount creates one native animation and emits one `lr-start`. A real target or
+timing change still rebuilds the animation, while replay and reconnect retain their normal
+start/finish lifecycle, including reduced motion.
+
 **Properties:**
 
 - `name: string = 'none'` — accepts any animation registry name. The built-in names are `'none' |

package/llms/components/lr-app-rail-item.md

@@ -122,8 +122,10 @@ vetoing that one would leave `open` stuck `true` in a mode where it's meaningles
 `preventDefault()` to keep the overlay as it is for the other triggers),
 `lr-rail-resize-request` (`detail: LyraAppRailResizeDetail` = `{ widthPx: number }`; a cancelable
 proposed width from drag or keyboard stepping, emitted before the component assigns
-`railWidthPx` — call `preventDefault()` to keep the current width. It is not fired when a consumer
-sets `railWidthPx` directly), and `lr-rail-resize` (`detail: LyraAppRailResizeDetail` =
+`railWidthPx` — call `preventDefault()` to keep the current width. A synchronous request listener
+that disables resizing, leaves full mode, or disconnects the rail also cancels the proposal,
+preserving any width the listener assigned and publishing no accepted resize. Assigning only
+`railWidthPx` does not veto the proposal. It is not fired when a consumer sets `railWidthPx` directly), and `lr-rail-resize` (`detail: LyraAppRailResizeDetail` =
 `{ widthPx: number }`; non-cancelable committed width, emitted immediately for a genuine keyboard
 step and once at pointerup for a genuine drag. Clamped/no-op steps, canceled/lost gestures, and
 consumer property writes emit no committed event).

package/llms/components/lr-app-rail.md

@@ -121,8 +121,10 @@ vetoing that one would leave `open` stuck `true` in a mode where it's meaningles
 `preventDefault()` to keep the overlay as it is for the other triggers),
 `lr-rail-resize-request` (`detail: LyraAppRailResizeDetail` = `{ widthPx: number }`; a cancelable
 proposed width from drag or keyboard stepping, emitted before the component assigns
-`railWidthPx` — call `preventDefault()` to keep the current width. It is not fired when a consumer
-sets `railWidthPx` directly), and `lr-rail-resize` (`detail: LyraAppRailResizeDetail` =
+`railWidthPx` — call `preventDefault()` to keep the current width. A synchronous request listener
+that disables resizing, leaves full mode, or disconnects the rail also cancels the proposal,
+preserving any width the listener assigned and publishing no accepted resize. Assigning only
+`railWidthPx` does not veto the proposal. It is not fired when a consumer sets `railWidthPx` directly), and `lr-rail-resize` (`detail: LyraAppRailResizeDetail` =
 `{ widthPx: number }`; non-cancelable committed width, emitted immediately for a genuine keyboard
 step and once at pointerup for a genuine drag. Clamped/no-op steps, canceled/lost gestures, and
 consumer property writes emit no committed event).

package/llms/components/lr-attachment-chip.md

@@ -26,6 +26,12 @@ wins when both are present. When a real `File` or `preview-src` is available, th
 localized action that emits a plain, non-cancelable `lr-preview-request`; it never registers or owns a viewer
 or overlay, so the host composes the desired preview surface.
 
+An error already present at first mount or reconnection renders as existing state without an
+announcement, including a failure assigned while detached and reconnected before the next render. A
+new connected transition to error still appends one localized failure announcement; repeated
+connected failures remain separately announced, including a retry whose uploading and error writes
+coalesce into one update.
+
 **Properties:**
 
 - `file?: File` (attribute `false`, i.e. property-only) — when set, `name`/`bytes`/`mimeType`/the

package/llms/components/lr-av-player.md

@@ -25,6 +25,20 @@ distinct from `<lr-transcript-feed>` (live captions for an in-progress voice ses
 `anchorKinds: ['time-range']` only — no text selection is bound. The transcript virtualizes through
 `<lr-virtual-list>` the same way `lr-pdf-viewer` virtualizes pages.
 
+Removing `mime-type` consumes the absent hint safely and restores automatic video fallback unless
+`kind` explicitly selects audio. Attribute removal keeps its `null` property readback; an explicit
+empty hint remains empty, and a later audio MIME value restores audio detection.
+
+A cue with no `end` extends to the next strictly chronological applicable start, or remains
+open-ended when none exists. Equal starts do not end each other. The player indexes starts on cue
+assignment in at most O(n log n) work and reconciles each seek/time update in O(n) work. Caller
+order, first ID admission, explicit ends and overlap arbitration are retained; a paused seek uses
+replacement cues immediately, even before rendering. Duration changes preserve the same
+effective-start rules.
+
+An unavailable timeline keeps its resting border and background under hover and press. Enabled
+seeking retains token-driven pointer feedback.
+
 The default document-viewer renderer advertises `time-range` anchors but not search: the generic
 document payload has no cue/transcript field, so advertising search there would expose a control
 whose result is always empty. Standalone `<lr-av-player>` search remains available whenever the

package/llms/components/lr-avatar.md

@@ -22,6 +22,10 @@ named `icon` slot, label and image-load error event) and adds this library's sha
 `variant` vocabulary. Purely presentational, with no built-in interactivity; wrap it in a
 `<button>`/`<lr-menu>` trigger for a user-menu affordance.
 
+Removing the attribute consumes the label as absent while preserving its `null` property readback.
+Explicit empty labels remain empty, host `aria-label` precedence remains intact, and later label
+values restore the image or fallback name.
+
 **Properties:**
 
 - `initials: string = ''` — fallback text (typically 1-2 characters), shown whenever no glyph and no

package/llms/components/lr-box-plot.md

@@ -19,6 +19,12 @@
 Box-and-whisker chart from a precomputed five-number summary (no raw sample data sent to the
 browser). Does **not** extend `LyraChart` — a deliberately bespoke API.
 
+With `IntersectionObserver` available, canvas construction waits for its first delivered visibility
+decision. An off-screen box plot stays unconstructed until visible. Without the observer, drawing
+starts when the peers and canvas are ready; an empty delivered callback retains the visible
+fallback. Peer loading and accessible DOM can settle while visibility is pending. These rules also
+apply when the component reconnects.
+
 **Properties:**
 - `labels: readonly string[] = []` (attribute: false)
 - `datasets: readonly LyraBoxPlotSeries[] = []` (attribute: false) — each series contains readonly

package/llms/components/lr-button.md

@@ -24,6 +24,13 @@ light-DOM form's submission on its own. They remain default actions of the compo
 runs, while `stopPropagation()` alone does not. Canceling the form's later `submit` or `reset`
 event remains an independent veto point.
 
+External descriptions follow the current source element identity when an element with the same ID
+replaces it, when a source is removed or reinserted, and when the control reconnects or moves to
+another document. Host-root lookup and ordering follow the current `aria-describedby` list,
+including unresolved IDs and duplicates. Switching between native button and anchor modes keeps the
+relationship on the current action. Existing accessible names and `aria-controls` relationships
+retain their separate contracts.
+
 Set `href` to a safe link URL and the root renders as a real `<a part="base" href=…>` instead — a
 link styled as a button (e.g. a CTA). Native navigation is then the activation, so the submit/reset
 handling and `type` have no effect in that mode. A disabled link button (its own `disabled` or an
@@ -340,9 +347,10 @@ box no matter what tier or override is in play.
   an ancestor `<form>.elements` the same way `wa-button` does — a sibling text field's own
   Enter-to-submit lookup (which scans `form.elements` for a `type === 'submit'` control) finds it.
 - **`SubmitEvent.submitter` is not this element** whenever `name`/`value` or any `form*` override is
-  set: it is the transient native `<button>` described above, which has already been removed from
-  the DOM by the time a `submit` listener runs. Read the submitted entry from the `FormData`, or
-  the override off your own component, rather than identity-checking the submitter.
+  set: it is the transient native `<button>` described above. That native submitter remains
+  connected throughout synchronous `requestSubmit()` handling, so a `submit` listener can read
+  its `name`, `value` and `form*` fields and construct `FormData` with it. It is removed after
+  submission handling returns; its identity is distinct from the `lr-button` host.
 - The `form*` overrides and `type` are all inert while `href` renders the anchor — native navigation
   is the activation there, and an anchor has no submit/reset concept.
 

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

@@ -21,6 +21,10 @@ plain text, including its title, start/end time, location, and description. RFC
 remain all-day dates rather than fabricated midnight times, and an all-day `DTEND` is displayed as
 the exclusive boundary it represents (14–17 renders as 14–16). No HTML is injected.
 
+Valid early all-day dates, including years `0001`, `0099`, and `0100`, retain their UTC calendar
+year when parsed through `ical.js`; the exclusive `DTEND` display rule remains unchanged. The peer
+may normalize malformed raw date fields before Lyra receives them.
+
 **Properties:** `src: string = ''`, `name: string = ''`, and `maxHeight: string = ''` (attribute
 `max-height`); invalid CSS
 `max-height` values, declaration breaks, and `url()` are ignored. A host `aria-label` takes

package/llms/components/lr-calendar.md

@@ -18,6 +18,11 @@
 
 Responsive month calendar with event markers and an agenda view.
 
+Early ISO dates such as `0001`, `0099`, and `0100` retain their authored local year in the month
+grid and month navigation. Valid colored agenda actions preserve their foreground/background pairing
+through hover and press, with the existing state tokens remaining overridable. Arbitrary caller
+colors still require the caller to choose an accessible contrast pair.
+
 **Properties:**
 
 - `events: CalendarEvent[] = []` (attribute: false) — `{ readonly id?, readonly date, readonly

package/llms/components/lr-carousel.md

@@ -27,6 +27,11 @@ native or authored semantics, and an explicit `role`, `aria-roledescription`, or
 temporarily makes off-page slides inert and aria-hidden, then restores their retained author state
 when they become visible, are removed, or the carousel disconnects.
 
+**Keyboard:** focus the `scroll-container` viewport to navigate with Arrow keys (horizontal LTR/RTL
+or vertical), Home, and End. Keys originating in a native input, textarea, contenteditable surface,
+or supported custom control remain owned by that editor, including when the editor is the assigned
+slide itself; they do not change the active slide or move focus away from it.
+
 **Properties:**
 
 - `currentSlide: number = 0` (attribute `current-slide`, reflected) — zero-based index of the first

package/llms/components/lr-chart.md

@@ -21,6 +21,10 @@ Chart.js wrapper used directly and by the eight typed Chart.js tags plus `lr-his
 series surface and a raw Chart.js `config` passthrough (mirrors Web Awesome's `wa-chart` `config`
 property).
 
+For horizontal scalar bars, tooltip values come from parsed x rather than the category y, including
+an effective raw `config.options.indexAxis` override. Both formatter APIs follow this rule;
+structured points retain their y-value formatting.
+
 **Properties:**
 - `type: LyraChartType = 'bar'` — `LyraChartType = 'line' | 'bar' | 'scatter' | 'pie' | 'doughnut' |
   'radar' | 'polarArea' | 'bubble'` — every named default used by a typed `lr-*-chart` is
@@ -86,7 +90,9 @@ property).
     splitting the series in two.
   - `segmentColors` colors each *segment* (the line drawn between two consecutive points) by the
     segment's **starting** point index, so `['red', 'green']` over 3 points paints the first
-    segment red and the second green; a shorter array cycles. Wired to Chart.js's
+    segment red and the second green; a shorter array cycles. When rows are sampled, each
+    represented segment retains the original source starting-point index modulo the palette length.
+    Wired to Chart.js's
     `segment.borderColor` scriptable option, so it is only meaningful for line-type series.
     Typical use is threshold/anomaly banding along one line. A series that omits it (or passes an
     empty array) emits no `segment` key at all, leaving line rendering exactly as before.
@@ -427,9 +433,12 @@ announced. In particular, unavailable data labels do not remove generated table
   The raw `config` passthrough is deep-merged with `__proto__`/`constructor`/`prototype` keys skipped
   unconditionally, so a JSON-sourced `config` (e.g. parsed from an API response) can't reach up and
   pollute `Object.prototype` through the merge.
-- lazy-redraw + change gating: an `IntersectionObserver` gates `draw()` — while the host is scrolled
-  off-screen, property changes that would otherwise trigger a Chart.js redraw are skipped (and a
-  single redraw fires once it re-enters the viewport). Independently, `updated()` only reaches
+- lazy-redraw + change gating: with `IntersectionObserver` available, canvas construction waits
+  for its first delivered visibility decision. Off-screen charts remain unconstructed until
+  visible, and later off-screen property changes skip redraws until visibility returns. Without
+  the observer, drawing starts when the peer and canvas are ready. An empty delivered callback
+  retains the visible fallback. Peer loading and accessible DOM may settle while visibility is
+  pending. Independently, `updated()` only reaches
   Chart.js when at least one of `type`, `labels`, `datasets`, `description`, `grid`, `indexAxis`,
   `label`, `hiddenDatasets`, `legendPosition`, `min`, `max`, `plugins`, the internal resolved auto legend
   position, `valueFormatter`, `formatter`, `area`, `height`, `xLabel`, `yLabel`, `y2Label`, `beginAtZero`,

package/llms/components/lr-chat-message.md

@@ -27,6 +27,10 @@ else). No built-in copy button is rendered — slot a copy control into `actions
 `<lr-code-block>`'s copy-affordance contract for anything listening at the conversation-surface
 level).
 
+Compose `lr-copy-button` in `actions` with its `value` set to the intended message source. The shell
+does not infer that source or write the clipboard itself; the composed control emits success only
+after the write fulfills.
+
 **Properties:**
 
 - `messageRole: ChatMessageRole = 'assistant'` (`'user' | 'assistant' | 'system'`, attribute

package/llms/components/lr-checkbox.md

@@ -20,6 +20,9 @@ A boolean form control. `role="checkbox"` with an `aria-checked` that can also b
 visual box/checkmark. Structurally the same idea as `<lr-switch>` (form-associated via
 `ElementInternals`, click and Space toggle) but with checkbox semantics.
 
+Removing `error-text` safely omits the message while preserving native `null` property readback.
+Explicit empty text stays empty; later supplied text renders normally.
+
 **Properties:**
 
 - `checked: boolean = false` — the live, non-reflecting state

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

@@ -24,6 +24,9 @@ clicking its remove (×) button only fires `lr-remove` — the chip never remove
 on its own interaction, the same contract `<lr-attachment-chip>`/`<lr-conversation-item>`
 already follow.
 
+Collapsed groups reapply `max-visible` when assigned children are replaced or reordered at the same
+count, preserving authored hidden/inert state and releasing departed visibility leases.
+
 **Two breaks in 8.0.0.** `tone` is now `variant`, with no alias — one concept, one spelling,
 library-wide. And a chip is **no longer a pill by default**: `--lr-chip-radius` used to be
 `var(--lr-radius-pill)` unconditionally, is now `var(--lr-radius)` (a rounded rectangle), and the

package/llms/components/lr-chip.md

@@ -24,6 +24,9 @@ clicking its remove (×) button only fires `lr-remove` — the chip never remove
 on its own interaction, the same contract `<lr-attachment-chip>`/`<lr-conversation-item>`
 already follow.
 
+Collapsed groups reapply `max-visible` when assigned children are replaced or reordered at the same
+count, preserving authored hidden/inert state and releasing departed visibility leases.
+
 **Two breaks in 8.0.0.** `tone` is now `variant`, with no alias — one concept, one spelling,
 library-wide. And a chip is **no longer a pill by default**: `--lr-chip-radius` used to be
 `var(--lr-radius-pill)` unconditionally, is now `var(--lr-radius)` (a rounded rectangle), and the

package/llms/components/lr-code-block-core.md

@@ -26,6 +26,13 @@ plus an explicit oniguruma engine, seeded with _only_ the grammars in `languages
 importing this entry point instead of `code-block.js` gets a build genuinely free of shiki's full
 language table.
 
+Removing `code`, `language`, or `highlight-lines` treats that input as absent: source becomes empty,
+an absent language selects plain text, and attribute-based emphasis clears. Removal preserves Lit's
+`null` property readback; an explicitly empty attribute stays an empty string, and a later value
+resumes normal rendering. Highlighted gutter labels and locale-formatted line numbers follow live
+`.strings` and inherited or explicit locale changes. Unrelated updates retain the existing
+highlighted markup.
+
 A `language` value absent from `languages` always renders the plain `<pre><code>` fallback — there is
 no default/full-table highlighter here to fall back to, unlike `<lr-code-block>`'s dynamic-import
 path for an unmapped language. That fallback is the _default_ rendering path, not a degraded one,
@@ -106,8 +113,12 @@ fallback separately.
 **Optional peer deps:** `shiki` (specifically its `shiki/core`, `shiki/engine/oniguruma`,
 `shiki/wasm`, and `shiki/themes/github-{light,dark}.mjs` subpaths — never `shiki`'s main entry point,
 which is what carries the ~200-language table this component exists to avoid). Building the
-fine-grained highlighter is cached per `languages` object identity (a `WeakMap`), so passing the same
-module-level `languages` constant on every render builds it only once.
+fine-grained highlighter is cached per `languages` object identity. A bounded weak cache also shares
+recently used equivalent, deeply frozen plain grammar maps, including the detached snapshots owned
+by separate component instances. Grammar contents and property/array order must agree completely;
+mutable or unusual inputs keep identity-only caching. Highlighters returned by the public loader
+can therefore be shared across equivalent frozen maps. Passing a stable module-level `languages`
+constant also avoids repeated component snapshots.
 
 ```ts
 import { html } from "lit";
@@ -128,7 +139,8 @@ const view = html`<lr-code-block-core
   added to `languages` will never highlight, no matter how common that language is elsewhere. Reach
   for `<lr-code-block>` instead if you need to support an open-ended set of languages without
   pre-declaring each one.
-- `languages` is keyed by object identity for caching purposes — pass a stable, module-level constant
-  (not a fresh object literal per render), or every render rebuilds its own fine-grained highlighter.
+- Pass a stable, module-level `languages` constant to avoid repeated snapshots on parent renders.
+  Equivalent frozen maps can share a recently used highlighter, but that bounded weak reuse is an
+  optimization: callers must not depend on distinct frozen map objects producing distinct cores.
 
 ---

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

@@ -24,6 +24,13 @@ Shiki does not bundle one. It falls back to a plain `<pre><code>` when that peer
 fallback is the _default_ rendering path, not a degraded one: unhighlighted code is perfectly usable,
 and it's what every instance renders at zero extra bytes until shiki resolves.
 
+Removing `code`, `language`, or `highlight-lines` treats that input as absent: source becomes empty,
+an absent language selects plain text, and attribute-based emphasis clears. Removal preserves Lit's
+`null` property readback; an explicitly empty attribute stays an empty string, and a later value
+resumes normal rendering. Highlighted gutter labels and locale-formatted line numbers follow live
+`.strings` and inherited or explicit locale changes. Unrelated updates retain the existing
+highlighted markup.
+
 **Properties:**
 
 - `code: string = ''` — the raw source text

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

@@ -20,6 +20,15 @@ Long translated form chrome wraps within the host, while long source stays reach
 editor's internal scroll extent instead of widening the page. The `Narrow RTL long content
 (320px)` story covers both boundaries together.
 
+`form.reset()` restores the default value and pristine interaction feedback. Required and custom
+validity constraints remain; a required-empty editor is still invalid. Removing `label`, `hint`, or
+`error-text` treats the removed value as absent for rendering while retaining native
+attribute-removal property readback.
+
+Host `aria-describedby` references resolve in the host root onto the native textarea before its
+local error/hint guidance. Target replacement, removal, reinsertion, unresolved IDs, reconnect, and
+adoption keep that relationship current.
+
 Dependency-free, form-associated multiline code editor built around a native textarea, with an
 optional line-number gutter. No syntax highlighting: `language` is metadata only.
 
@@ -29,9 +38,11 @@ optional line-number gutter. No syntax highlighting: `language` is metadata only
   `data-language`; purely a consumer-reachable styling/metadata hook, nothing tokenizes the text
 - `lineNumbers: boolean = true` (attribute `line-numbers`, reflected) — renders the `gutter` part,
   one row per `\n`-separated line
-- `tabSize: number = 2` (attribute `tab-size`) — spaces inserted per Tab press, and the textarea's
-  inline `tab-size`. Sanitized on assignment to a finite integer clamped to `1..16`, so a
-  `NaN`/`Infinity` value can neither empty the insert nor throw out of `String.repeat()`
+- `tabSize: number = 2` (attribute `tab-size`) — spaces inserted per Tab press and the tab width
+  shared by the native textarea and text measurement. Explicit property/attribute assignment wins
+  over `--lr-code-editor-tab-size`; otherwise the token controls the rendered tab width. Sanitized
+  on assignment to a finite integer clamped to `1..16`, so a `NaN`/`Infinity` value can neither
+  empty the insert nor throw out of `String.repeat()`.
 - `label: string = ''`, `hint: string = ''`, `errorText: string = ''` (attribute `error-text`),
   `placeholder: string = ''`
 - `readonly: boolean = false` (reflected) — also disables Tab indentation
@@ -47,8 +58,10 @@ optional line-number gutter. No syntax highlighting: `language` is metadata only
   `lr-textarea`/`lr-input`/`lr-select`, accepting both spellings of every tier (`2xs`/`xs`/`s`/`m`/
   `l`/`xl` and `small`/`medium`/`large`). Governs the gutter's and textarea's padding and font size,
   plus the editor frame's minimum block size.
-- `wrap: 'off' | 'soft' | 'hard' = 'off'` — native textarea wrapping; `'off'` (the default) makes
-  the `editor` part the single horizontal scroll viewport. `hard` uses the owner realm's native
+- `wrap: 'off' | 'soft' | 'hard' = 'off'` — native textarea wrapping. `'off'` (the default) makes
+  the `editor` part the single horizontal scroll viewport. Soft/hard text wraps within the editor
+  allocation, with the caret and logical line-number gutter following the wrapped lines as the
+  allocation changes; the editor frame owns scrolling. `hard` uses the owner realm's native
   textarea serializer, so FormData receives platform-equivalent `cols` wrapping while the live
   `value` remains unwrapped.
 - `spellcheck: boolean = false` — off by default for code, and parsed with a string-aware converter

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

@@ -21,6 +21,15 @@ opens a popover holding a saturation/brightness grid, a hue slider, an optional
 field accepting any parseable CSS colour, an optional predefined palette, and — where the browser
 supports it — a screen eyedropper.
 
+Host `aria-describedby` references resolve in the host's root and precede the trigger's local error,
+hint and current-value guidance. Same-ID target replacement, removal, reinsertion, reconnection and
+document adoption keep those relationships current. Inline mode has no trigger.
+
+Own or fieldset disablement discards an unfinished native text draft without committing it and
+blocks palette/format actions immediately, including before disabled rendering settles. A valid
+enabled draft still commits on normal blur or Enter. Format changes retain their existing
+programmatic event silence. Pointer and eyedropper cancellation behavior remains unchanged.
+
 **Rewritten in 8.0.0.** It used to wrap a bare native `<input type="color">`; it is now a real
 picker built from the pieces above. Two consequences for existing code:
 

package/llms/components/lr-combobox.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-command-palette.md

@@ -20,6 +20,10 @@ Searchable application command menu. Renders nothing at all while closed. Uses t
 overlay infrastructure as `lr-dialog` (focus-trapping Tab, Escape dismissal, backdrop-click
 dismissal, ref-counted document scroll lock).
 
+Valid string keywords still participate in search alongside the command's label, description, and
+group. Unsafe keyword entries are skipped without invoking accessors, and selection returns the
+original command object.
+
 **Properties:**
 
 - `open: boolean = false` (reflected) — after the initial silent render, property and attribute

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

@@ -19,6 +19,9 @@
 A compact commit summary (subject, author/time, diffstat, per-file changes) that links file rows out
 to a diff view.
 
+Removing the `message` attribute clears the displayed subject and body; the property retains the
+normal `null` readback of a removed string attribute.
+
 **Properties:** `hash: string = ''`, `message: string = ''`, `author: string = ''`, `timestamp?:
 number` (attribute: false, epoch milliseconds), `files: CommitFileChange[] = []` (attribute: false) —
 `CommitFileChange { path: string; additions: number; deletions: number; status?: GitStatus }`

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

@@ -19,6 +19,13 @@
 Side-by-side A/B output comparison with a winner vote (LMSYS-arena / LangSmith-pairwise style): two
 slotted panes, a vote bar, synchronized reading.
 
+Disabled vote buttons retain their resting colors during hover and press, including an existing
+selected vote.
+
+At narrow widths, stacked response panes size to their content up to
+`--lr-compare-panel-max-height`. Short responses remain fully readable; longer responses retain the
+configured height limit and scrolling.
+
 **Properties:** `labelA: string = ''` (attribute `label-a`) and `labelB: string = ''` (attribute
 `label-b`) — pane headings. `vote: 'a' | 'b' | 'tie' | 'both-bad' | null = null` (reflected) — the
 recorded winner, host-writable to reflect a previously-recorded vote back. `itemId: string = ''`

package/llms/components/lr-condition-builder.md

@@ -19,6 +19,11 @@
 Composable flat condition builder for tabular or dashboard data: condition rows combined with an
 AND/OR combinator, distinct by name and model from `lr-graph-query-builder`.
 
+A field or operator select choice updates the builder once and emits one `lr-input` carrying the
+complete `{ value: ConditionBuilderValue }` snapshot. Child native `input`/`change`, prefixed value
+aliases and listbox show/hide lifecycle events remain inside those pickers. Programmatic `value`
+assignments remain silent.
+
 **9.0 migration:** `lr-query-builder` / `LyraQueryBuilder` / `QueryBuilder*` were renamed without
 aliases to `lr-condition-builder` / `LyraConditionBuilder` / `ConditionBuilder*`. Update the tag,
 granular import path, class/type imports, selectors, and framework bindings together.

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

@@ -20,6 +20,9 @@ A selectable row representing one chat session in a history sidebar list. Usable
 `renderItem()` payload of `<lr-virtual-list>`; has no dependency on that (or any) other component.
 First-party invention (no Web Awesome equivalent).
 
+Inline rename keeps IME composition keys in the editor; ordinary Enter commits and Escape cancels
+after composition.
+
 **Properties:**
 
 - `conversationId: string = ''` (attribute `conversation-id`) — stable domain identity carried by

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

@@ -21,6 +21,12 @@ A standalone copy-to-clipboard affordance for a plain text `value` or a source e
 settles; a consumer-provided default-slot trigger can replace that button. The component takes no
 positioning opinion of its own.
 
+The CopyFailure example temporarily supplies a denied clipboard operation during click capture,
+including after a held pointer press, then restores the original own property descriptor or removes
+its temporary override when the clipboard was inherited. Pointer gestures that end without a click
+do not install an override. This example does not change the clipboard contract of ordinary copy
+buttons.
+
 **Properties:**
 
 - `value: string = ''` — the plain text to copy.

package/llms/components/lr-dashboard-grid.md

@@ -19,6 +19,11 @@
 Responsive, keyboard-accessible controlled widget grid. It positions layout entries and emits
 move, resize, collision, and layout-change requests; the host owns persistence and applies updates.
 
+Pointer move and resize gestures measure the rendered column/row pitch, including the gutter, so
+movement by four painted tracks proposes four logical columns in either LTR or RTL. Row-height and
+gap overrides also govern vertical pointer snapping. The component continues to emit controlled
+layout proposals; the caller accepts them by assigning `layout`.
+
 **Properties:** `layout: readonly LyraDashboardCell[] = []` (attribute: false, never mutated by the component),
 `columns: number = 12`, `rowHeight: number = 80` (px, also the row snap pitch), `gap: number = 8`
 (px, both axes), `collision: 'reject' | 'push' | 'overlap' = 'reject'`, `cellsDraggable: boolean = false`

package/llms/components/lr-data-grid.md

@@ -20,6 +20,12 @@ Virtualized client/server data grid with multi-sort, column filters, global sear
 trees, row details, paging, pinning, resizing, reordering, selection, copy, and CSV export. Import
 the granular registration module when the root bundle is not already loaded:
 
+Repeated references to an admitted root row appear once in processed rows, pagination, facets, and
+CSV, matching rendered canonical identity. The retained occurrence remains the original caller-owned
+record. Clicking a supported interactive descendant, including a native control inside its open
+shadow root, runs that control without also emitting `lr-cell-click`. Passive cell content continues
+to activate the cell.
+
 ```js
 import "@aceshooting/lyra-ui/components/data/data-grid/data-grid.js";
 ```
@@ -114,7 +120,11 @@ are `text`, `equals`, `number-range`, `date-range`, `set`, `includes-any`, and `
 
 **Methods:**
 
-- `autoSizeColumn(columnId)`, `autoSizeColumns()`, and `sizeColumnsToFit()` manage measured widths.
+- `autoSizeColumn(columnId)` and `autoSizeColumns()` manage measured widths. `sizeColumnsToFit()`
+  reserves visible effective zero-flex column widths and selection-control allocation before
+  dividing the remaining width proportionally among flexible columns. Fixed widths are preserved;
+  min/max clamps still apply, and an all-fixed grid is unchanged. Maximum clamps can leave unused
+  space, while incompatible minimum widths can still overflow.
 - `collapseAllRows()`, `collapseRow(key)`, `expandAllRows()`, and `expandRow(key)` update expansion
   without emitting the user-only row events.
 - `copySelectedRows(options?: DataGridCopyOptions)` copies selected rows (or all processed rows

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

@@ -34,8 +34,9 @@ rather than a phantom success, and a header-row target scrolls with the same
 `max-height`), and `scrollMode: DatasetViewerScrollMode = 'self'` (attribute `scroll-mode`,
 reflected). Invalid CSS `max-height` values, declaration breaks, and `url()` are ignored.
 `scrollMode='self'` preserves contained horizontal scrolling and applies `maxHeight`.
-`scrollMode='page'` drops both the overflow container and height cap so an uncapped sticky header
-uses the page scrollport; the explicit tradeoff is that a wide dataset can overflow its host.
+`scrollMode='page'` removes intervening scroll containers and the height cap, so a populated table's
+sticky header follows the page scrollport while rows continue below it. The border and rounded
+header corners remain; a wide dataset can overflow its host in page mode.
 Unsupported attribute and untyped property values normalize to `'self'`.
 Host `aria-label` names the table by attribute presence, including an explicitly empty value;
 `name` and the localized row-count caption are fallbacks. The same computed name (host `aria-label`,