@aceshooting/lyra-ui 19.0.1 → 20.0.1

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

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 17 parts, 8 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 17 parts, 10 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -52,12 +52,13 @@ plain and virtualized rendering paths while `label` remains the visible header t
 arbitrary rich content (e.g. rendered markdown, or markdown plus a trailing tool-call chip list),
 identically whether or not the feed is currently virtualized; replaces the plain text **inside**
 the persistent `[part="entry-text"]` wrapper rather than removing that part, and `virtualizeAt: number = 199` (attribute
-`virtualize-at`). `compact: boolean = false` (reflected) — tighter header and entry-row padding for
-dense transcript contexts, the same density-only convention `<lr-confirm-bar>`'s and
+`virtualize-at`). `compact: boolean = false` (reflected) — tighter header and entry-row padding and
+gap for dense transcript contexts, the same density-only convention `<lr-confirm-bar>`'s and
 `<lr-thinking-panel>`'s own `compact` establish: the outer border and surface stay, so pair it
 with `frame="plain"` to remove card chrome. Retune it through
-`--lr-activity-feed-compact-header-padding`, `--lr-activity-feed-compact-header-gap`, and
-`--lr-activity-feed-compact-entry-padding`. `frame: LyraFrame = 'card'` (reflected) — `'card' |
+`--lr-activity-feed-compact-header-padding`, `--lr-activity-feed-compact-header-gap`,
+`--lr-activity-feed-compact-entry-padding`, and `--lr-activity-feed-compact-entry-gap`.
+`frame: LyraFrame = 'card'` (reflected) — `'card' |
 'plain'`, imported from the library's shared container-frame vocabulary and behaving exactly as
 it does on `lr-confirm-bar`/`lr-thinking-panel`/`lr-agent-run`/etc.: `'plain'` removes the outer
 border, background, and corner radius so a feed nested inside existing message chrome doesn't
@@ -79,13 +80,19 @@ part is reachable in both rendering paths, virtualized or not.
 tall the expanded body grows before it scrolls internally; and
 `--lr-activity-feed-live-status-color` (default `var(--lr-color-brand)`) — background color of
 `status-dot` while `mode="live"`, independently retunable without changing other brand surfaces.
-The `compact` density is retunable through three properties: `--lr-activity-feed-compact-header-padding`
+The `compact` density is retunable through four properties: `--lr-activity-feed-compact-header-padding`
 (default `var(--lr-space-2xs) var(--lr-space-s)`) and `--lr-activity-feed-compact-header-gap`
 (default `var(--lr-space-2xs)`) both scoped to `[part="header"]` while `compact`, and
-`--lr-activity-feed-compact-entry-padding` (default `var(--lr-space-2xs) var(--lr-space-s)`)
-scoped to `[part="entry"]` while `compact`. All three are inline `var()` fallbacks at their point
+`--lr-activity-feed-compact-entry-padding` (default `var(--lr-space-2xs) var(--lr-space-s)`) and
+`--lr-activity-feed-compact-entry-gap` (default `var(--lr-space-2xs)`) both scoped to
+`[part="entry"]` while `compact`. All four are inline `var()` fallbacks at their point
 of use, so any can be set on the element or on an ancestor, same as `lr-confirm-bar`'s and
-`lr-thinking-panel`'s own compact tokens. The card chrome itself is retunable the same way:
+`lr-thinking-panel`'s own compact tokens. `renderText`'s returned content is otherwise unreachable
+by selector from outside the shadow root it renders into (the plain or the internal
+`<lr-virtual-list>`'s), so a returned anchor specifically is given
+`--lr-activity-feed-entry-text-link-color` (default `var(--lr-color-brand)`), mirroring
+`lr-table`'s identical `cell(row)`-anchor hook; set it to `revert` for the UA default link color.
+The card chrome itself is retunable the same way:
 `--lr-activity-feed-background` (default `var(--lr-color-surface)`) fills `[part="base"]`,
 `--lr-activity-feed-border-color` (default `var(--lr-color-border)`) colors both its border and the
 header/body divider that `frame="plain"` keeps, and `--lr-activity-feed-radius` (default
@@ -102,6 +109,10 @@ hooks tune the card presentation rather than reinstating chrome you asked to dro
   and the dot for DOM queries.
 - `compact`/`frame` render byte-identically to the pre-existing default when unset — neither
   property changes anything about the plain-card presentation.
+- A `renderText`-returned anchor is the only descendant markup given a default styling hook
+  (`--lr-activity-feed-entry-text-link-color`); other rich descendants (`<code>`, `<em>`, custom
+  chips) stay reachable only through inheritance or an inline style on the callback's own return
+  value, since `::part(entry-text)` cannot select past the wrapper.
 - Focus repair after an `entries` change is asynchronous while virtualized (it waits on the
   internal `<lr-virtual-list>`'s own follow-up render before deciding whether the previously
   focused row actually disappeared), but synchronous when collapsing (`expanded` going `false`)

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

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 11 parts, 1 custom property — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 12 parts, 1 custom property — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -38,7 +38,8 @@ resolved while open closes the dialog, and reentrant host updates during selecti
 stale request.
 
 **CSS parts:** `base`, `heading-row`, `heading`, `count`, `list`, `request`, `request-info`,
-`tool-name`, `request-id`, `status`, `empty`. The `[part='request']` row matching
+`tool-name`, `request-id`, `status`, `empty`, `limit` (localized notice shown when `requests`
+exceeds the 500-row render ceiling). The `[part='request']` row matching
 `selectedInvocationId`
 carries both `data-selected="true"` (the styling hook) and `aria-current="true"` (the semantic
 state), so the selection is announced, not merely painted. Other request rows explicitly render

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

@@ -39,7 +39,14 @@ complete entry path; both forms first mount the absolute virtualized row and onl
 shared DOM-level anchor resolution. Rendered rows intentionally do not expose entry paths as DOM
 ids; the fragment mapping is resolved against archive metadata. A jump whose archive is replaced
 by a concurrent `src` reassignment mid-flight, or whose row cannot be located after the wait,
-reports `found: false` rather than a phantom success.
+reports `found: false` rather than a phantom success. A ZIP central directory may legally repeat
+an entry path across multiple entries; since a fragment id names only the path, it always
+resolves to that path's first central-directory occurrence (the same first-match precedent as
+`document.getElementById()`/`:target` for a duplicated DOM id) — a later duplicate is not
+independently addressable through the fragment/anchor API. `search()`/`searchNext()`/
+`searchPrevious()` are unaffected: they track each occurrence by its true row position, so
+navigating search matches (and the resulting active-row highlight) correctly reaches every
+duplicate-named entry, not just the first.
 
 **Events:** `lr-render-error` with `detail.error` when fetching or parsing fails;
 `lr-search-change` (`detail: { query, matchCount, matchCountExact, activeIndex }`) from search,

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

@@ -53,7 +53,9 @@ slot has assigned content. Assigning `view='code'` without assigned code content
 navigation and the built-in copy/download buttons.
 
 **Events:** `lr-view-change` (`detail: { view }`), `lr-version-change` (`detail: { versionId }`,
-fired when the previous/next navigation moves to a different version), `lr-restore` (`detail: {
+fired when the previous/next navigation moves to a different version; not fired when a `versions`
+reassignment drops the currently-active version id — `activeVersionId` resets to `null` silently,
+since `null` is already a documented steady state meaning "the latest version"), `lr-restore` (`detail: {
 versionId }`, fired by the restore-this-version button; mutates nothing itself), `lr-copy`
 (`detail: { ok: true, text }`, after the clipboard write fulfills), `lr-error` plus
 `lr-copy-error` (`detail: { ok: false, text, reason, error }`) on a localized failure, and

package/llms/components/lr-audio-visualizer.md

@@ -30,7 +30,9 @@ hosts that already have one (e.g. `lr-push-to-talk`'s `lr-level` detail); `state
 animation and per-state coloring; `mode: AudioVisualizerMode = 'bars'` (`'bars' | 'waveform'`,
 reflected); `barCount: number = 5` (attribute `bar-count`, normalized to an integer in `[1, 64]`);
 `gain: number = 1` — multiplier applied to the resolved amplitude, with a non-finite value treated
-as `1`; `label: string = ''` — accessible-name override. `level` is clamped to `[0, 1]`; after gain,
+as `1`; `label?: string` — accessible-name override. Omitting it auto-generates "Voice activity:
+{state}"; an explicit empty string suppresses that default and renders an empty accessible name.
+`level` is clamped to `[0, 1]`; after gain,
 waveform and bar values are clamped to `[-1, 1]` and `[0, 1]` respectively. Invalid `state` or
 `mode` attribute/property writes normalize to `idle` and `bars` respectively.
 

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

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 3 parts, 7 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 3 parts, 8 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -69,11 +69,18 @@ that follows `variant`),
 badge label. Its private default follows `size` alongside the badge diameter, matching
 `<lr-avatar>`'s own `--lr-avatar-font-size` scale (`xs`/`sm`/`md-sm`/`m`/`lg`/`xl` font tokens from
 the `2xs` through `xl` size tiers), so the badge and the avatars it caps read at the same optical
-weight. An inherited or direct public value remains authoritative for every hook.
-
-The overflow badge keeps a `--lr-icon-button-size` minimum activation target at every tier while
-the nested visual disc stays exactly avatar-sized, so small tiers do not paint as oversized 40px
-circles.
+weight. `--lr-avatar-group-radius` (default `var(--lr-radius-pill)`) — corner radius of the
+slotted avatars' ring and of the overflow badge's painted disc. Its private default follows
+`shape` (`var(--lr-radius-pill)` for `circle`, `var(--lr-radius)` for `rounded`, `0` for `square`);
+an inherited or direct public value overrides both uniformly, mirroring `<lr-avatar>`'s own
+`--lr-avatar-radius` — a per-avatar `shape` override still wins for that individual avatar's own
+ring, matching the existing mixed-shape-group support. An inherited or direct public value remains
+authoritative for every hook.
+
+The overflow badge keeps a `--lr-icon-button-size` minimum activation target at every tier — a
+floor, not a cap, so the action surface grows past it to always contain the nested visual disc
+once `--lr-avatar-group-avatar-size` exceeds it (the default size and `l`/`xl`) — while small
+tiers still paint an exactly avatar-sized disc instead of an oversized 40px circle.
 
 **Optional peer deps:** none.
 

package/llms/components/lr-avatar.md

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 4 parts, 5 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 4 parts, 6 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -84,7 +84,11 @@ private default changes for a non-neutral `variant` to that variant's loud color
 and of any `em`-sized slotted glyph. Its private default follows `size` alongside the diameter
 (`--lr-font-size-xs` at `2xs`, `--lr-font-size-sm` at `xs`, `--lr-font-size-md-sm` at `s`,
 `--lr-font-size-m` at `m`, `--lr-font-size-lg` at `l`, and `--lr-font-size-xl` at `xl`), so the
-initials track the circle instead of staying one fixed size across every tier. Every public value
+initials track the circle instead of staying one fixed size across every tier. `--lr-avatar-radius`
+(default `var(--lr-radius-pill)`) — corner radius of the container. Its private default follows
+`shape` (`var(--lr-radius-pill)` for `circle`, `var(--lr-radius)` for `rounded`, `0` for `square`);
+an inherited or direct public value overrides uniformly across every shape, the same way
+`--lr-avatar-size` spans every size tier. Every public value
 above can be inherited from an ancestor or set directly on the avatar and remains authoritative
 across size/variant states. Plus shared tokens
 `--lr-radius`/`-pill`, `--lr-font-weight-semibold`.

package/llms/components/lr-bar-chart.md

@@ -41,11 +41,14 @@ of every entry in these lists.**
 `refreshTheme()`.
 
 **Events:** `lr-zoom` (`detail: { zoomed: boolean }`), `lr-datum-activate`, `lr-point-click` (`detail: { datasetIndex,
-index, label, value }`), `lr-before-legend-visibility-change` (cancelable), and
+index, label, value }`), `lr-legend-visibility-change-request` (cancelable), and
 `lr-legend-visibility-change` (commit; both legend events carry `datasetIndex`, `visible`, and the
-complete `hiddenDatasets` snapshot).
-Radial category legends additionally emit `lr-before-datum-visibility-change` (cancelable) and
+complete `hiddenDatasets` snapshot). `lr-before-legend-visibility-change` is a **deprecated** alias
+of `lr-legend-visibility-change-request` (removal not before 21.0.0).
+Radial category legends additionally emit `lr-datum-visibility-change-request` (cancelable) and
 `lr-datum-visibility-change`, carrying `index`, `visible` and the frozen `hiddenDatums` snapshot.
+`lr-before-datum-visibility-change` is a **deprecated** alias of `lr-datum-visibility-change-request`
+(removal not before 21.0.0).
 
 **Slots:** default JSON configuration script, `data-table`, `center`.
 

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

@@ -7,7 +7,7 @@
 - **Family** `components/charts/` — see `llms/index.md` for its siblings
 - **Status** `stable` since `4.0.0` — see the maturity and deprecation policy in `llms/shared.md`
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
-- **Deprecations** none
+- **Deprecated event** `lr-before-legend-visibility-change` since `19.0.1`; use event `addEventListener('lr-legend-visibility-change-request', ...)`; removal not before `21.0.0` — Renamed to the library's dominant *-request veto-event convention; both names fire from the same gesture with an identical detail during the compatibility window, and either may veto.
 - **Optional peers** `@sgratzl/chartjs-chart-boxplot`, `chart.js` — see `llms/peers.md`
 - **Themeable via** 12 parts, 33 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
@@ -47,6 +47,7 @@ apply when the component reconnects.
 - `height: string = '280px'` — valid CSS height used as a private fallback only. A consumer-set
   `--lr-chart-height` always wins; invalid values remove the fallback and leave the public
   token/default in control.
+- `xLabel: string = ''` (attribute `x-label`) — category axis title, mirroring `yLabel`
 - `yLabel: string = ''` (attribute `y-label`)
 - `beginAtZero: boolean = true` (attribute `begin-at-zero`)
 - `label: string | null = null`, `description: string | null = null` — canonical accessible name
@@ -76,11 +77,14 @@ change. Canvas work remains connected/visible-gated, while a rendered DOM legend
 its computed color swatches.
 
 **Events:** `lr-datum-activate` (canonical detail with `kind: 'box'`), `lr-point-click`
-(compatibility), `lr-before-legend-visibility-change` (cancelable proposed legend
+(compatibility), `lr-legend-visibility-change-request` (cancelable proposed legend
 toggle) and `lr-legend-visibility-change` (accepted commit). The two legend events carry
 `{ datasetIndex: number, visible: boolean, hiddenDatasets: readonly number[] }`, where
 `hiddenDatasets` is the complete sorted, valid next snapshot. Calling `preventDefault()` on the
 proposal leaves state untouched and suppresses the commit event.
+`lr-before-legend-visibility-change` is a **deprecated** alias of
+`lr-legend-visibility-change-request`, fired immediately after it from the same gesture with the
+same detail; either event may veto (removal not before 21.0.0).
 
 `lr-point-click` fires when pointer input lands on a box, or when Enter/Space activates the
 keyboard-current box — the same event name and role `lr-chart` and `lr-lite-chart` expose. Its

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

@@ -23,7 +23,9 @@ the new `index` back. Renders nothing at all while `count < 2`, so a host can bi
 on every message regardless of whether that message actually has multiple branches yet.
 
 **Properties:** `index: number = 0` (reflected) and `count: number = 1` (reflected) — the current
-0-based branch and the total branch count. `label: string = ''`.
+0-based branch and the total branch count. `label?: string` — accessible name for the group.
+Omitting it localizes the default `branchPickerLabel` message; an explicit empty string suppresses
+that default and renders no label.
 
 **Methods:** `focus(options?)` forwards to the currently enabled chevron (falling back to the first
 rendered chevron), `blur()` blurs both chevrons, `click()` activates that same enabled target, and

package/llms/components/lr-bubble-chart.md

@@ -41,11 +41,14 @@ of every entry in these lists.**
 `refreshTheme()`.
 
 **Events:** `lr-zoom` (`detail: { zoomed: boolean }`), `lr-datum-activate`, `lr-point-click` (`detail: { datasetIndex,
-index, label, value }`), `lr-before-legend-visibility-change` (cancelable), and
+index, label, value }`), `lr-legend-visibility-change-request` (cancelable), and
 `lr-legend-visibility-change` (commit; both legend events carry `datasetIndex`, `visible`, and the
-complete `hiddenDatasets` snapshot).
-Radial category legends additionally emit `lr-before-datum-visibility-change` (cancelable) and
+complete `hiddenDatasets` snapshot). `lr-before-legend-visibility-change` is a **deprecated** alias
+of `lr-legend-visibility-change-request` (removal not before 21.0.0).
+Radial category legends additionally emit `lr-datum-visibility-change-request` (cancelable) and
 `lr-datum-visibility-change`, carrying `index`, `visible` and the frozen `hiddenDatums` snapshot.
+`lr-before-datum-visibility-change` is a **deprecated** alias of `lr-datum-visibility-change-request`
+(removal not before 21.0.0).
 
 **Slots:** default JSON configuration script, `data-table`, `center`.
 

package/llms/components/lr-calendar.md

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 16 parts, 12 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 18 parts, 12 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -50,6 +50,11 @@ title, readonly color?, readonly data? }`; `date` accepts an ISO `YYYY-MM-DD` st
   section retains the localized purpose name rather than duplicating an authored host name; when
   set programmatically without a host attribute, this value names the section
 
+At most 4 events render as `event` buttons inside a single month-view day cell, and at most 500
+events render as `agenda-event` buttons in agenda view; either ceiling past that count renders a
+localized `event-limit`/`agenda-limit` "+N more" notice rather than mounting an unbounded number of
+buttons.
+
 **Keyboard:** the month grid is a fixed 6×7 matrix (leading/trailing days of adjacent months fill it
 out) with one roving tab stop — `focusedDate`, else `value`, else today, else the first rendered day.
 Arrows move by 1 day (Left/Right swapped under RTL) or 7; stepping past the rendered grid rolls
@@ -63,8 +68,10 @@ Arrows move by 1 day (Left/Right swapped under RTL) or 7; stepping past the rend
 **CSS parts:** `header` and `navigation` are aliases on the header wrapper; `nav` is shared by both
 month-navigation buttons; `previous-button` and `next-button` identify each direct button;
 `nav-glyph` is the chevron (`scaleX(-1)`-mirrored under RTL); `title`, `weekdays`, `weekday`,
-`grid`, `week` (`display: contents`), `day`, `date`, `event` (a month-view marker), `agenda`, and
-`agenda-event`.
+`grid`, `week` (`display: contents`), `day`, `date`, `event` (a month-view marker), `event-limit`
+(localized "+N more" notice shown in a day cell whose events exceed the 4-event per-cell render
+ceiling), `agenda`, `agenda-event`, and `agenda-limit` (localized "+N more" notice shown in agenda
+view when the visible month's events exceed the 500-event render ceiling).
 
 **Themeable custom properties:** `--lr-calendar-day-min-block-size` (default `var(--lr-size-6rem)`)
 and `--lr-calendar-day-min-block-size-narrow` (default `var(--lr-size-4rem)`, applied at container inline-size

package/llms/components/lr-carousel.md

@@ -80,8 +80,10 @@ retain their mapped opt-in defaults, and the autoplay interval remains 3000ms.
   automatically
 
 **Events:** `lr-slide-change` (`detail: { index, slide }`) — emitted after the active slide changes
-from a method, button, key, pagination item, autoplay tick, or settled user scroll. `slide` is the
-original assigned element at `index`, never a loop endcap.
+from a method, button, key, pagination item, autoplay tick, or settled user scroll. Also emitted
+when a `slidesPerPage` change or a slide's removal forces the active index onto a different slide.
+Not emitted when a consumer sets `currentSlide` directly to an out-of-range value; that assignment
+is clamped silently. `slide` is the original assigned element at `index`, never a loop endcap.
 
 **Paging and scrolling.** In non-loop mode the page count is the set of reachable starts from zero
 to `slideCount - slidesPerPage`, stepping by `slidesPerMove` and always including the final start.

package/llms/components/lr-chart.md

@@ -7,7 +7,8 @@
 - **Family** `components/charts/` — see `llms/index.md` for its siblings
 - **Status** `stable` since `4.0.0` — see the maturity and deprecation policy in `llms/shared.md`
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
-- **Deprecations** none
+- **Deprecated event** `lr-before-datum-visibility-change` since `19.0.1`; use event `addEventListener('lr-datum-visibility-change-request', ...)`; removal not before `21.0.0` — Renamed to the library's dominant *-request veto-event convention; both names fire from the same gesture with an identical detail during the compatibility window, and either may veto.
+- **Deprecated event** `lr-before-legend-visibility-change` since `19.0.1`; use event `addEventListener('lr-legend-visibility-change-request', ...)`; removal not before `21.0.0` — Renamed to the library's dominant *-request veto-event convention; both names fire from the same gesture with an identical detail during the compatibility window, and either may veto.
 - **Optional peers** `chart.js`, `chartjs-plugin-annotation`, `chartjs-plugin-datalabels`, `chartjs-plugin-zoom` — see `llms/peers.md`
 - **Themeable via** 16 parts, 37 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
@@ -391,17 +392,24 @@ including a string or finite-number `id` when supplied; invalid ids are omitted.
 is typed `unknown`. Validate or explicitly narrow the value itself before reading point fields;
 checking `detail.kind === 'point'` alone does not narrow `detail.value` in TypeScript.
 `lr-point-click` remains as a compatibility event. Also
-`lr-before-legend-visibility-change` (cancelable proposal), and
+`lr-legend-visibility-change-request` (cancelable proposal), and
 `lr-legend-visibility-change` (accepted commit). Both legend events carry
 `{ datasetIndex: number, visible: boolean, hiddenDatasets: readonly number[] }`; the latter is the
 complete, sorted, valid next snapshot. Call `preventDefault()` on the proposal to veto the toggle;
-then no property change or commit event occurs.
-Category toggles use a separate pair, `lr-before-datum-visibility-change` (cancelable proposal) and
+then no property change or commit event occurs. `lr-before-legend-visibility-change` is a
+**deprecated** alias of `lr-legend-visibility-change-request`, fired immediately after it from the
+same gesture with the same frozen detail; either event may veto. It is slated for removal in
+21.0.0 — migrate listeners to `lr-legend-visibility-change-request`.
+Category toggles use a separate pair, `lr-datum-visibility-change-request` (cancelable proposal) and
 `lr-datum-visibility-change` (accepted commit), carrying
 `{ index: number, visible: boolean, hiddenDatums: readonly number[] }`. Both details and their
 complete, sorted index snapshots are frozen. `index` is the source category index, including when
 the displayed data is sampled; it applies across all rings. Programmatic assignments emit neither
 pair. `preventDefault()` leaves both controlled state and the chart unchanged.
+`lr-before-datum-visibility-change` is a **deprecated** alias of
+`lr-datum-visibility-change-request`, fired immediately after it from the same gesture with the
+same frozen detail; either event may veto. It is slated for removal in 21.0.0 — migrate listeners
+to `lr-datum-visibility-change-request`.
 
 ```html
 <lr-doughnut-chart

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

@@ -42,8 +42,9 @@ index of the first unread item (element-child index in slotted mode, `items` ind
 'off'` (reflected) — policy for the shared light-DOM announcement sink; the internal log itself
 remains non-live. Keep `off` for token-by-token streaming and opt in only when complete messages are
 appended as direct children at an announcement-safe cadence.
-`label: string = ''` — accessible name
-for the log region, defaults to the localized `chatViewportLabel`. `accessibleLabel: string | null =
+`label?: string` — accessible name
+for the log region. Omitting it localizes the default `chatViewportLabel` message; an explicit
+empty string suppresses that default and renders no label. `accessibleLabel: string | null =
 null` (attribute `aria-label`) — host `aria-label`, forwarded to the internal `role="log"` element
 (an `aria-label` left on the host itself names nothing, since the log role lives inside the shadow
 root); wins over `label` and the localized default.

package/llms/components/lr-checkbox.md

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 15 parts, 10 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 15 parts, 11 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -50,12 +50,13 @@ Explicit empty text stays empty; later supplied text renders normally.
 
 **Events:** user toggles emit, in order, bubbling/composed `input`, the compatibility `lr-input`
 alias, bubbling/composed `change`, then the compatibility `lr-change` alias (both aliases carry
-`detail: { checked: boolean }`). Programmatic `.checked` assignments are
-silent. Internal `focus`/`blur` are re-dispatched as bubbling, composed host events. `lr-invalid` (no detail) fires when a
-validity check finds the checkbox invalid.
+`detail: { checked: boolean, value: string }`, matching `lr-radio`'s shape). Programmatic `.checked`
+assignments are silent. Internal `focus`/`blur` are re-dispatched as bubbling, composed host events.
+`lr-invalid` (no detail) fires when a validity check finds the checkbox invalid.
 **Refusing a toggle.** `lr-checkbox-toggle-request` is cancelable and fires *before* `checked`
 moves, on every user path (click, Space, and the host `click()` activation it forwards).
-`detail: { checked: boolean }` is the state the control **would** take; `checked` itself still holds
+`detail: { checked: boolean, value: string }` is the state the control **would** take (`value` is
+the current `.value`, unaffected by the toggle); `checked` itself still holds
 the old value while the event dispatches. `preventDefault()` keeps the current state, so the box
 never flips at all rather than flipping and snapping back, and none of
 `input`/`lr-input`/`change`/`lr-change` follow. A listener can instead answer by assigning `checked`
@@ -130,6 +131,8 @@ State paint is independently themeable through `--lr-checkbox-hover-border`,
 `--lr-checkbox-active-border`, `--lr-checkbox-active-ring`, `--lr-checkbox-invalid-border`,
 `--lr-checkbox-checked-bg`, and `--lr-checkbox-checked-border`; every default preserves the
 corresponding brand/brand-quiet/danger token.
+`--lr-checkbox-box-radius` (default `calc(var(--lr-form-control-radius) * 0.6)`) retunes
+`[part='box']`'s corner radius without a `::part(box)` rule.
 
 **`--lr-checkbox-box-size`** — the edge length of `[part='box']`, defaulting to
 `min(var(--lr-icon-button-size), calc(var(--lr-form-control-height) * 0.7))`. Derived from the

package/llms/components/lr-citation-badge.md

@@ -123,6 +123,8 @@ no background tint, for citations that carry no confidence/verification signal a
   `lr-citation-open` instead of triggering a second `lr-citation-activate`.
 - Escape closes the popover but calls `stopPropagation()`, so it won't also close a surrounding
   `<lr-dialog>` that has its own Escape-to-close handler.
+- An open popover participates in shared Escape ordering even while only hovered, deferring to a
+  genuinely topmost overlay opened on top of it.
 - The preview slot's presence is tracked in JS (`hasPreviewSlot`), not via CSS `:empty` — the
   `[part="popover"]` always contains a literal `<slot>` child, so `:empty` would never match even
   with nothing assigned.

package/llms/components/lr-claim-evidence.md

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 11 parts, 2 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 12 parts, 2 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -33,6 +33,9 @@ duplicates are omitted first-wins before empty state, controlled selection, evid
 rendering, or events. An unrecognized runtime claim status renders as localized “Unsupported” with
 the danger treatment instead of producing an empty or misleading badge.
 
+At most 500 claims render as `claim` rows; a `claims` array past that length renders a localized
+`limit` notice after the list rather than mounting an unbounded number of rows.
+
 - `compact: boolean = false` (reflected) — tighter `claim-trigger` padding and column gap, for dense
   evidence lists — the same convention as `lr-source-card`'s/`lr-entity-card`'s `compact`. Purely a
   density knob: each claim's border and background stay. `false` (the default) keeps the full
@@ -49,7 +52,8 @@ composed `lr-citation-open` event intentionally crosses `lr-claim-evidence` unch
 `{ sourceId, index, href }` detail.
 
 **CSS parts:** `base`, `list`, `claim`, `claim-selected`, `claim-trigger`, `status`, `claim-text`,
-`confidence`, `explanation`, `evidence`, `empty`.
+`confidence`, `explanation`, `evidence`, `limit` (localized notice shown when `claims` exceeds the
+500-claim render ceiling), `empty`.
 
 **Themeable custom properties:** `--lr-claim-evidence-compact-padding` (default
 `var(--lr-space-xs)`) — `[part='claim-trigger']`'s padding while `compact`;

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

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 8 parts, 14 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 8 parts, 15 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -129,6 +129,8 @@ hover and invalid states below.
 `--lr-code-editor-hover-border` (default `var(--lr-color-brand)`) and
 `--lr-code-editor-invalid-border` (default `var(--lr-color-danger)`) retint those frame states
 without changing brand/danger paint in sibling components.
+`--lr-code-editor-radius` (default `var(--lr-radius)`) retunes the editor frame's corner radius
+without a `::part(editor)` rule.
 The `editor` scroll frame also honors the opt-in theme-level
 `--lr-theme-scrollbar-width`/`--lr-theme-scrollbar-gutter` hooks (defaults `auto`/`auto`, matching
 its previous unconditional `scrollbar-width: auto`) — set either on `:root` or any ancestor for one

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

@@ -74,7 +74,14 @@ designer-chosen colours; reach for this when it must not.
 **Properties:** the shared
 form properties `name`, `value`, `defaultValue` (canonical content attribute `value`),
 `customError` (`custom-error`), `disabled`, and
-`required`, plus `label`, `hint`, `errorText`
+`required`,
+`readonly: boolean = false` (reflected — forwards native read-only behavior to the panel's value
+field and blocks every other value-committing affordance: the popup panel opening, the
+saturation/hue/opacity handles, palette swatches, the eyedropper, and Enter/blur-driven text
+commits; the trigger, value field and palette stay focusable, and the current value still submits
+with the form -- only `disabled` excludes it. Toggling it on while the panel is open closes it, and
+cancels an in-flight drag without committing, mirroring `disabled`'s own mid-interaction handling),
+plus `label`, `hint`, `errorText`
 (`error-text`), `accessibleLabel` (`aria-label`), and `size: LyraSize = 'm'`
 (reflected — the same visual-density scale as `lr-input`, applied to the centered visible swatch;
 accepts `2xs`/`xs`/`s`/`m`/`l`/`xl` and `small`/`medium`/`large`; the interactive target
@@ -90,15 +97,19 @@ and:
   applies to the whole string, function names included (`RGB(255, 0, 0)`)
 - `swatches: string | string[] | LyraColorPickerSwatch[] = ''` — a predefined palette, given as a
   `;`-separated string, an array of colour strings, or an array of
-  `{ color: string; label?: string; disabled?: boolean }` objects. Any colour the picker can parse
-  is accepted; blank entries are dropped. An entry that is _not_ parseable is kept in the list and
-  still renders a swatch — it just paints no colour (the bare checkerboard) and clicking it does
-  nothing, so filter the palette yourself if that matters. `label` becomes the swatch's accessible
-  name; a missing, empty, or whitespace-only label falls back to announcing the raw colour string.
+  `{ color: string; label?: string; disabled?: boolean; icon?: unknown }` objects. Any colour the
+  picker can parse is accepted; blank entries are dropped. An entry that is _not_ parseable is kept
+  in the list and still renders a swatch — it just paints no colour (the bare checkerboard) and
+  clicking it does nothing, so filter the palette yourself if that matters. `label` becomes the
+  swatch's accessible name; a missing, empty, or whitespace-only label falls back to announcing the
+  raw colour string.
   `disabled` marks that one swatch non-actionable, independent of the whole control's own
   `disabled`: it renders a genuinely disabled `<button>` (no tab stop, no hover/press affordance)
   and clicking it commits nothing; omitted or `false` renders the swatch exactly as before this
-  field existed. The palette container renders only while the normalized list is non-empty
+  field existed. `icon` is an optional decorative custom shape rendered inside the swatch button
+  behind the `swatch-icon` part -- inert and `aria-hidden`, matching `<lr-swatch-picker>`'s
+  identical `SwatchPickerItem.icon` field. The palette container renders only while the normalized
+  list is non-empty
 - `withoutFormatToggle: boolean = false` (attribute `without-format-toggle`) — removes the button
   that cycles between formats. `noFormatToggle` (`no-format-toggle`) is the Shoelace spelling and
   reaches the same behavior; either one wins
@@ -200,7 +211,8 @@ absent with either format-toggle suppression property), plus `format-button__bas
 `eyedropper-button` / `eye-dropper-button` (rendered only where the browser exposes the EyeDropper
 API), with the corresponding `eyedropper-button__base|start|label|end|caret` and Shoelace
 `eye-dropper-button__base|prefix|label|suffix|caret` aliases; `swatches` (the palette container, rendered only when the normalized `swatches`
-list is non-empty), `swatch` (one palette entry), `swatch-selected` (a token **added to** the
+list is non-empty), `swatch` (one palette entry), `swatch-icon` (a swatch entry's optional
+decorative icon, inert and `aria-hidden`), `swatch-selected` (a token **added to** the
 swatch matching the current value — state after `::part()` never matches, so write
 `::part(swatch-selected)`), `hint`, `error`.
 

package/llms/components/lr-combobox.md

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 33 parts, 32 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 33 parts, 36 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Documented with** `lr-option` (same section below)
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
@@ -153,7 +153,22 @@ An async `source` row can carry the same two fields (`start`, `end`) alongside i
   none. A blank return falls back to the raw value. Not consulted while an async `source` fetch has
   never yet resolved for this element — see "Unknown committed values" below; `loadingText` covers
   that window instead, since the value is not yet known to be unmatched at all
-- `appearance: 'filled' | 'outlined' | 'filled-outlined' = 'outlined'` (reflected)
+- `loading: boolean = false` (reflected) — mirrors `lr-select`'s own `loading`: whether a
+  committed value's real label may still be pending because its `<lr-option>` catalog hasn't
+  arrived yet (e.g. mounted asynchronously with no `source` involved). While `true`, a committed
+  value that currently matches no option/row renders the localized `loadingText` placeholder in the
+  trigger label or the relevant `multiple` tag instead of the raw value, with no
+  `notInCatalog`/`[part='unknown-value']` badge, and the open listbox shows the same loading row a
+  `source` fetch in flight shows. Independent of `source`'s own async lifecycle — either condition
+  alone suppresses the unknown-value presentation. Never mutates `value`/`selectedOptions` itself,
+  and does not itself disable the trigger
+- `appearance: 'accent' | 'filled' | 'outlined' | 'filled-outlined' | 'plain' = 'outlined'`
+  (reflected) — the library's shared field-surface vocabulary, matching `lr-select`'s trigger.
+  `outlined` (the default) is a bordered surface; `filled` swaps the border for a raised fill;
+  `filled-outlined` keeps both; `plain` drops both; `accent` paints the loud brand fill with
+  on-brand text (the placeholder, expand icon, adornments and `multiple` tags all ride that
+  on-brand color rather than the quiet-text tokens). An unsupported value, including a raw
+  attribute/property write outside this type, clamps to the `'outlined'` default
 - `placement: 'top' | 'bottom' = 'bottom'` (reflected; flip/shift can still keep the listbox in view)
 - `positioningStrategy: PlaceStrategy = 'fixed'` (attribute `positioning-strategy`, reflected) —
   the CSS positioning scheme the listbox is laid out with, spelled the same as on `lr-select`,
@@ -493,6 +508,11 @@ standard size supplies an aligned default), plus shared tokens. `--lr-combobox-g
 `--lr-space-xs`, the gap inside `[part='combobox']`) and `--lr-combobox-radius` (default
 `--lr-radius`, its corner radius) are both retunable without a `::part(combobox)` rule but, unlike
 the properties above, do not vary by `size` — the same `--lr-button-gap`/`-radius` pattern.
+`--lr-combobox-tag-bg` (default `var(--lr-color-brand-quiet)`), `--lr-combobox-tag-color` (default
+`var(--lr-color-text)`) and `--lr-combobox-tag-radius` (default `var(--lr-radius)`) retint a
+selected tag's background, text color and corner radius without a `::part(tag)` rule; `-tag-bg` is
+scoped independently of `--lr-combobox-option-active-bg`/`-option-badge-bg` below, which already
+scope the same shared `--lr-color-brand-quiet` token for their own purposes.
 
 The trigger row's own surface became public in 16.0.0, having been a private pair until then:
 `--lr-combobox-fill` (default `var(--lr-color-surface)`) and `--lr-combobox-border-color` (default
@@ -503,7 +523,10 @@ here wins over every treatment. `--lr-combobox-open-border-color` (default
 border before. Read the name as the state the listbox opens in rather than as a synonym for `open`:
 it is bound to `:focus-within`, so it also paints on a focused row whose listbox is closed — after
 an Escape dismissal, say. It is named for symmetry with `lr-select`'s
-`--lr-select-open-border-color`, which really is gated on `open`.
+`--lr-select-open-border-color`, which really is gated on `open`. `--lr-combobox-text-color`
+(default `inherit`) recolors the trigger's own text the same way; `appearance="accent"` defaults it
+instead to `var(--lr-color-on-brand)`, keeping placeholder, adornments and tag text readable on the
+loud brand fill.
 
 The shared field halo `--lr-form-control-focus-shadow` (default `none`) paints a `box-shadow`
 while this control is focused — one name for every field-shaped control in the library, so a

package/llms/components/lr-command-palette.md

@@ -7,7 +7,7 @@
 - **Family** `components/layout/` — see `llms/index.md` for its siblings
 - **Status** `stable` since `4.0.0` — see the maturity and deprecation policy in `llms/shared.md`
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
-- **Deprecations** none
+- **Deprecated event** `lr-open` since `19.0.1`; use event `addEventListener('lr-show', handler)`; removal not before `21.0.0` — lr-open collided in name with an unrelated "item activated" lr-open fired by lr-document-library/lr-source-card, and broke the lr-show/lr-hide overlay-lifecycle vocabulary its architectural sibling lr-lightbox already follows. lr-show fires identically (same null detail, cancelability, and timing) at the same call site, and lr-open is kept as a deprecated alias through the 20.x line.
 - **Optional peers** none
 - **Themeable via** 15 parts, 12 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
@@ -61,11 +61,14 @@ no-op if already open),
 cycling) at the ends; the active row is scrolled into view. Enter selects. Hovering a non-disabled
 row also makes it active.
 
-**Events:** `lr-open`, `lr-close` (both `detail: null`, cancelable — fired before the
+**Events:** `lr-show`, `lr-close` (both `detail: null`, cancelable — fired before the
 mutation, `preventDefault()` keeps the palette in its current open state), `lr-select`
 (`detail: { command }`, fired before the command's own `onSelect` runs and before the palette
 closes), and no-detail `focus`/`blur` events re-dispatched from the host whenever the search input
-gains or loses focus. The `focus`/`blur` bridge is new in 10.0.0: native `focus`/`blur` neither
+gains or loses focus. `lr-open` is a deprecated alias for `lr-show` (same `detail: null`,
+cancelability, and timing, fired at the same call site; either event's `preventDefault()` vetoes
+the open) kept for the 20.x line and removed no earlier than 21.0.0. The `focus`/`blur` bridge is
+new in 10.0.0: native `focus`/`blur` neither
 bubble nor cross the shadow boundary, so a host-level `el.addEventListener('focus', …)` previously
 never fired at all.