@aceshooting/lyra-ui 19.0.0 → 20.0.0

package/llms-full.txt

@@ -4963,7 +4963,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`,
@@ -5303,6 +5318,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
@@ -5313,7 +5333,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
@@ -5894,6 +5917,12 @@ invalid CSS and never matches — which is exactly why these tokens exist.
 `[part='option-badge']` "not in catalog" badge `show-unknown-option` renders on the synthetic
 listbox row, independent of the unknown-value chip's border above.
 
+`--lr-select-tag-remove-hover-bg` (default `var(--lr-color-brand-quiet)`) retints a hovered
+`[part='tag__remove-button']`'s background without a `::part(tag__remove-button)` rule; the pressed
+state mixes from this same token. Scoped independently of `--lr-select-trigger-hover-bg` and
+`--lr-select-option-active-bg` above, which already scope the identical shared token for their own
+purposes.
+
 **Optional peer deps:** none.
 
 ```html
@@ -6139,7 +6168,13 @@ Text field + calendar popover, **form-associated** via the shared `FormAssociate
 
 **Properties (44):**
 
-- `appearance: 'filled'|'outlined'|'filled-outlined' = 'outlined'` (reflected)
+- `appearance: 'accent' | 'filled' | 'outlined' | 'filled-outlined' | 'plain' = 'outlined'`
+  (reflected) — the library's shared field-surface vocabulary, matching `lr-select`'s trigger and
+  `lr-combobox`'s own `appearance`. `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, start/end adornments and clear/expand
+  buttons 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
 - `appliedPreset: LyraDateRangePreset | undefined` (read-only, new in 12.0.0) — the `presets` entry
   whose button produced the current `value`, or `undefined` when the value was picked on the
   calendar, typed into the field, cleared, or reset. Read it inside your own `change`/`input`
@@ -6278,7 +6313,10 @@ With no label text the part is hidden and no glyph is painted.
 `--lr-form-control-height`. All four defaults follow the shared size ladder, including
 `small`/`medium`/`large` aliases and inherited `--lr-theme-form-control-height-*` overrides.
 Inherited or direct public values win. `pill` changes the private radius default to
-`--lr-radius-pill`; a public `--lr-date-input-radius` still wins.
+`--lr-radius-pill`; a public `--lr-date-input-radius` still wins. `--lr-date-input-text-color`
+(default `inherit`) recolors the row's own text; `appearance="accent"` defaults it instead to
+`var(--lr-color-on-brand)`, keeping the placeholder and clear/calendar actions readable on the loud
+brand fill.
 
 Calendar and clear actions fit inside the selected row height while retaining at least 24×24
 CSS-pixel targets. At the default root size, rows measure 30/40/48/56px for s/m/l/xl; 2xs and xs
@@ -8236,9 +8274,13 @@ the reset default, or prior interaction state.
 `form.reset()` restores the original declarative `value` and the default country.
 
 **Slots:** `label`, `hint`, `error`, `country-prefix` (optional visual before the country selector,
-such as a consumer-owned `<lr-flag>`; no flag package is imported automatically).
+such as a consumer-owned `<lr-flag>`; no flag package is imported automatically), `start` (alias
+for `country-prefix`, matching the leading-adornment slot name every other forms/ single-line
+field uses — both feed the same wrapper), `end` (optional trailing adornment after the telephone
+input, matching the trailing-adornment slot name every other forms/ single-line field uses).
 
-**CSS parts:** `form-control`, `form-control-label`, `input-wrapper`, `country-prefix`, `country`
+**CSS parts:** `form-control`, `form-control-label`, `input-wrapper`, `country-prefix` (also
+receives the `start` alias slot's content), `end`, `country`
 (the selector region: invisible native select layered over the visual trigger), `country-select`,
 `country-trigger` (visible, `aria-hidden` closed-state box), `flag` (the `<lr-flag>`, only with
 `flags`), `country-code` (selected alpha-2 code, `data-placeholder` when no country exists),
@@ -8317,8 +8359,8 @@ import "@aceshooting/lyra-ui/components/media/flag/flag-peer.js";
 - The component never imports `@aceshooting/lyra-flags` itself, with `flags` or without. `flags`
   lazily registers only the `<lr-flag>` element; the artwork resolver comes from the consumer's own
   `flag-peer.js` import (plus the installed peer package), so forgetting either shows a flagless
-  trigger rather than erroring. `country-prefix` remains available for a fully consumer-owned
-  adornment instead.
+  trigger rather than erroring. `country-prefix` (or its `start` alias) remains available for a
+  fully consumer-owned adornment instead.
 - The visible trigger (`country-trigger` and everything inside it) is `aria-hidden` by design; the
   layered native select is the accessible control. Don't move interactive content into those parts
   via `::part` styling tricks, and don't expect the flag inside the open popup list — a native
@@ -8810,12 +8852,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`
@@ -8890,6 +8933,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
@@ -9011,7 +9056,7 @@ normally.
 **Events:** a user state change (click, Space, a logical ArrowLeft/ArrowRight change, or the
 programmatic `click()` activation path) emits
 `input`, then `lr-input`, then `change`, then `lr-change` (both aliases carry
-`detail: { checked: boolean }`) — in that order, matching
+`detail: { checked: boolean, value: string }`, matching `lr-radio`'s shape) — in that order, matching
 the native checkbox/radio contract. The two native-style events are **new in 8.0.0**: a boolean
 control that emitted only the `lr-`-prefixed alias was invisible to every form library, validation
 helper, and `<form>`-level `change` listener that binds the native names, which is the ordinary way
@@ -9023,8 +9068,9 @@ assignment, `form.reset()`, or session-state restoration. The internal control's
 check finds the switch invalid.
 **Refusing a toggle.** `lr-switch-toggle-request` is cancelable and fires *before* `checked` moves,
 on every user path (click, Space, a logical ArrowLeft/ArrowRight change, and the host `click()`
-activation it forwards). `detail: { checked: boolean }` is the state the switch **would** take;
-`checked` itself still holds the old value while the event dispatches. `preventDefault()` keeps the
+activation it forwards). `detail: { checked: boolean, value: string }` is the state the switch
+**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 switch never slides at all rather than sliding and snapping back, and none of
 `input`/`lr-input`/`change`/`lr-change` follow. A listener can instead answer by assigning `checked`
 itself during the dispatch, which suppresses the built-in write the same way. It does not fire for a
@@ -9683,7 +9729,9 @@ Public `--lr-otp-input-*` theme inputs stay undeclared on the host, so an ancest
 can override appearance fallbacks; a value set directly on the element still wins.
 
 **Properties:** `label`, `hint`, `errorText` (`error-text`);
-`appearance: 'outlined' | 'filled' | 'filled-outlined' | 'contained' = 'outlined'` (reflected);
+`appearance: 'outlined' | 'filled' | 'filled-outlined' | 'contained' = 'outlined'` (reflected) —
+does not implement the shared vocabulary's `accent`/`plain` tiers; an unsupported value, including
+a raw attribute/property write outside this type, clamps to the `'outlined'` default;
 `autofocus: boolean = false`; `autosubmit: boolean = false` (reflected);
 `size: LyraSize = 'm'` (reflected after an explicit property/attribute write, accepting
 `2xs`/`xs`/`s`/`m`/`l`/`xl` and the shared aliases). While unset, its generic font/radius/height
@@ -10055,7 +10103,12 @@ noneditable token layout remains the default.
 **Properties:** live, non-reflecting `value`, reflected `defaultValue` (attribute `value`, encoded
 as a JSON string array), `customError` (`custom-error`), `label`, `hint`, `errorText`
 (`error-text`), `placeholder`, `name`,
-`required`, `disabled`, `accessibleLabel` (attribute `aria-label` — forwarded to the input wrapper
+`required`, `disabled`,
+`readonly: boolean = false` (reflected — forwards native read-only behavior to the draft input and
+the inline token editor, and blocks adding, removing or editing a token while leaving the draft
+input, tokens and remove buttons focusable and the current value submitted with the form, mirroring
+`lr-input`'s `readonly`),
+`accessibleLabel` (attribute `aria-label` — forwarded to the input wrapper
 and draft text input; precedence is presence-based, so `aria-label=""` remains an explicit empty
 override and suppresses visible-label linkage), `spellcheck: boolean = true`, `autocapitalize: string = ''`, and `autocorrect` (read: `boolean = true`; write: `boolean | string`, attribute values
 `on`/`off`) — all three native text-entry hints are forwarded to both the draft input and the inline
@@ -10139,6 +10192,15 @@ controlled `value`/pristine `defaultValue` shrink, DOM focus moves to the neares
 equivalent surface at the clamped index. If no token remains it moves to the draft input; a newer
 explicit focus destination outside the component is never reclaimed.
 
+**`readonly` — locking the committed list.** Reflects native read-only behavior onto both the draft
+input and the inline token editor, and blocks every other value-committing affordance: typing (or a
+programmatic `input`/`change` dispatch) into the draft, Enter/delimiter/Tab draft commits,
+Backspace-removes-last-token, clicking a remove button, and opening or committing the inline
+editor (`editable`). Unlike `disabled`, it never removes the draft input, a token label, or a
+remove button from the tab order, never blocks `focus()`, and never excludes the current value from
+`FormData` on submit — only `disabled` does that. Turning it on while a draft is half-typed or an
+inline editor is open discards that uncommitted state without moving focus.
+
 **`delimiter` is nullable, and only a single character acts as a commit key.** It does two separate
 jobs: it splits a committed draft into several tokens, and — _only when it is exactly one
 character_ — it is the keystroke that commits the draft. A multi-character delimiter still splits a
@@ -10309,6 +10371,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
@@ -10389,7 +10453,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
@@ -10405,15 +10476,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
@@ -10515,7 +10590,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`.
 
@@ -10646,7 +10722,11 @@ A searchable, keyboard-navigable, form-associated emoji picker. `groups` is full
 — the component ships no emoji data of its own — in the same "zero/optional-peer dependency" spirit
 as `<lr-lite-chart>`/`<lr-heatmap>`; an optional convenience auto-loader fetches a default set on
 connect from the `emoji-picker-element-data` peer, but only when `groups` hasn't already been
-supplied (an explicit empty array still counts as supplied and skips the auto-load).
+supplied (an explicit empty array still counts as supplied and skips the auto-load). The auto-loader
+picks the peer's locale directory closest to `effectiveLocale` (an exact match, then the base
+language, else English), so each emoji's name — and therefore both its accessible name and the
+search index, not just the group headings — follows the page's locale; a later locale change
+reloads it. This only applies to the built-in dataset, never to a consumer-supplied `groups`.
 When the filtered set reaches 200 items, the grid automatically windows its visible rows while
 preserving the full option count through `aria-setsize`/`aria-posinset`.
 
@@ -10844,7 +10924,10 @@ discriminated union is `ScoreRubricKey | CategoryRubricKey | CommentRubricKey`.
 first-wins identity and retained valid spelling is not rewritten. Shared fields are
 `key`, `label?`, `description?`, and `required?`; only scores expose `min?`/`max?`/`step?`, only
 categories expose readonly `RubricKeyOption[]` plus `multiple?`, and only comments expose
-`placeholder?`. Runtime schema normalization retains the first occurrence of each nonempty key and
+`placeholder?`. Each `RubricKeyOption` also accepts an optional `icon?: unknown` -- a decorative
+leading visual rendered into `<lr-option>`'s `start` slot in the single-select branch, or inline
+before the label in the multiple-select `<lr-checkbox>` branch, inert and `aria-hidden` either way,
+matching `LyraFilterBarOption.icon`. Runtime schema normalization retains the first occurrence of each nonempty key and
 rejects malformed rows. `value: RubricValue = {}` is a defensive readonly snapshot and
 `defaultValue: RubricValue = {}` is its explicit form-reset baseline (both attribute: false).
 `itemId: string = ''`
@@ -10891,6 +10974,8 @@ state exposed as `errors.base`, rather than being attributed to one rubric key.
 clearing it hides that region unless the `error` slot supplies other content.
 `click()` forwards to the active field (the same one a submit-and-next transition auto-focuses),
 so the host behaves like a single control under both a `<label>`-driven and a programmatic click.
+`focus(options?)` moves focus to that same active field, matching `click()`'s target; this is also
+what lets the native `autofocus` attribute reach the rubric.
 
 **CSS parts:** `base` (the outer `role="group"` wrapper), `form-control` (aggregate chrome wrapper),
 `aggregate-label` / `form-control-label`, `fields` / `form-control-input`, `aggregate-hint` /
@@ -10948,7 +11033,10 @@ wrapper can override size-tier fallbacks; a value set directly on the element st
 readonly LyraLocaleEntry[]`, `LyraLocaleEntry { tag: string; label?: string; country?: string }`.
   `undefined` (the default) auto-discovers the registry; every supplied array (either form),
   including an authoritative `[]`, overrides it entirely — a curated subset, custom order,
-  custom labels, or a locale offered before its strings are registered. Explicit catalogs are
+  custom labels, or a locale offered before its strings are registered. An entry's `label` overrides
+  the derived `localeNativeName(tag)` endonym only when it is non-blank; an explicitly blank (or
+  whitespace-only) `label` is treated the same as an omitted one and still falls back to
+  `localeNativeName(tag)`. Explicit catalogs are
   capped, cloned and frozen at assignment; mutate a new array/entry and reassign it to update the
   list. `country` (ISO 3166-1 alpha-2 or alpha-3) overrides a row's derived flag — e.g.
   showing Lebanon's flag for an `'ar'` row instead of the library's default Saudi Arabia mapping;
@@ -11160,6 +11248,7 @@ These named interfaces and helper signatures are available to typed integrations
     color: string;
     label?: string;
     disabled?: boolean;
+    icon?: unknown;
   }`
 
 - **`components-forms-combobox-combobox-contracts`** — Supporting data types and helpers for this component family.
@@ -11330,6 +11419,7 @@ These named interfaces and helper signatures are available to typed integrations
     readonly value: string;
     readonly label?: string;
     readonly description?: string;
+    readonly icon?: unknown;
   }`
   Import: `@aceshooting/lyra-ui/components/forms/rubric-form/rubric-form.class.js`.
   `ScoreRubricKey extends RubricKeyBase {
@@ -11768,6 +11858,8 @@ ARIA values as page-local positions rather than as the dataset-wide total.
 `filterType`, `filterFn`, `hidden`, `hideable`, `resizable`, `movable`, `pinnable`, `pinned`,
 `footer`, `aggregation`, and `aggregatedFormatter`. A column with neither `field` nor `value` is an
 action column: its formatter receives `undefined`, and it is not sorted or searched by default.
+An omitted or explicitly blank (or whitespace-only) `label` both render the same humanized
+`field`/`id` fallback for the header cell — only a non-blank `label` overrides it.
 `cellTitle(row) => string | undefined` renders as the generated cell's native `title`, symmetrical
 with `<lr-table>`'s `columns[].cellTitle` — e.g. the untruncated text behind an ellipsized cell, or
 a formatted timestamp behind a relative one. Returning `undefined` or `''` omits the `title`
@@ -12005,7 +12097,7 @@ unchanged.
 
 - `columns: readonly TableColumn<T>[] = []` (attribute: false; clone-owned frozen collection,
   bounded to the first 10,000 source positions; blank keys and later duplicates are omitted first-wins
-  before header, cell, sort, focus, and event paths; reassign to update) — `{ key, label,
+  before header, cell, sort, focus, and event paths; reassign to update) — `{ key, label, ariaLabel?,
 headerCell?, width?, minWidth?, maxWidth?,
 resizable?, sortable?, sortValue?, defaultSortDir?: 'asc'|'desc', align?: 'start'|'end',
 priority?: 'medium'|'low',
@@ -12014,6 +12106,11 @@ editType?: 'text'|'number'|'select',
 editOptions?: { value: string; label: string }[], footer?, cellStyle?, heatValue?,
 cell: (row) => unknown }` — `cell` is required for every `editTrigger` except `'always'`, whose
   persistent editor renders unconditionally so the table's render path never falls back to it —
+  `ariaLabel` overrides that column header's accessible name (applied as the `<th>`'s `aria-label`
+  whenever set) — e.g. an icon-only `headerCell` with no plain-text `label` to fall back on; when
+  `label` is blank (or whitespace-only) and `ariaLabel` is also omitted, the header's accessible
+  name falls back to `key` while the visible header itself stays blank, matching a deliberate
+  icon-only column —
   `sortValue(row) => string | number | null | undefined` supplies the comparable value backing
   client-mode sorting for that column: a finite number sorts numerically, a string sorts through an
   `Intl.Collator` built from the component's effective locale with `numeric: true` (so `item2`
@@ -13035,7 +13132,12 @@ true), `label` (rendered only while `label` is non-empty)
 
 **Themeable custom properties:** `--lr-gauge-fill` (fill stroke; overrides `variant`/`thresholds`
 entirely and falls back to the effective variant's shared semantic token —
-`--lr-color-brand` by default).
+`--lr-color-brand` by default). Each variant also has its own scoped fill, read as the innermost
+fallback before the shared token so a consumer can retint one variant without `--lr-gauge-fill`'s
+uniform override touching the others: `--lr-gauge-neutral-fill` (default `var(--lr-color-neutral)`),
+`--lr-gauge-brand-fill` (default `var(--lr-color-brand)`), `--lr-gauge-success-fill` (default
+`var(--lr-color-success)`), `--lr-gauge-warning-fill` (default `var(--lr-color-warning)`), and
+`--lr-gauge-danger-fill` (default `var(--lr-color-danger)`).
 
 **Optional peer deps:** none.
 
@@ -13156,13 +13258,18 @@ interface LyraFunnelStage {
 }
 ```
 
+At most 500 valid stages render, each as its own bar row; a `stages` array past that length renders
+a localized `limit` notice after the list rather than mounting an unbounded number of bars. Every
+stage's share is still measured against the true first stage regardless of truncation.
+
 **Events:** none.
 
 **Slots:** none.
 
 **CSS parts:** `base`, `stages` (the `<ol>`), `stage`, `dropoff`, `stage-header`, `stage-label`,
 `stage-value`, `stage-share`, `comparison-value`, `track`, `bar`, `bar-overflow` (a second token on
-`bar` when the stage exceeds the first stage), `comparison-bar`, `empty`
+`bar` when the stage exceeds the first stage), `comparison-bar`, `empty`, `limit` (localized notice
+shown when `stages` exceeds the 500-stage render ceiling)
 
 **Themeable custom properties:** `--lr-funnel-bar-color` (default `var(--lr-color-brand)`),
 `--lr-funnel-comparison-color` (default `var(--lr-color-border-strong)`), `--lr-funnel-track-color`
@@ -13702,8 +13809,11 @@ color?: string; label?: string; partOfRamp?: boolean }`: a discrete legend key r
   "no data" color next to an N-step ramp) to exclude just that stop from the comparison; defaults to
   `true`. A caption-only stop (no `color`) is already excluded regardless of this flag.
 
-**Getters/methods:** `exportData('png')` returns a PNG data URL for the most recently completed
-canvas paint. It includes the painted axes, cells, focus/selection/annotation overlays, and frozen
+**Getters/methods:** `exportData('csv'|'png')` returns a spreadsheet-safe CSV snapshot of the
+underlying matrix/calendar values or a PNG data URL for the most recently completed canvas paint.
+The CSV form reads `data` directly (not any bounded render cache) and omits no-data cells — one
+`row,column,value` row per real matrix cell, or `date,value` per real calendar day. The PNG form
+includes the painted axes, cells, focus/selection/annotation overlays, and frozen
 label bands while `stickyLabels` is enabled; the DOM legend, tooltip, and accessible-cell buttons
 are deliberately excluded. It returns `''` before a completed paint, while rendering is deferred or
 zero-sized, after disconnect, or when the browser cannot encode the snapshot. `refreshTheme()` —
@@ -14029,8 +14139,12 @@ block-size), `--lr-sequence-strip-marker-color` (default `var(--lr-color-text)`
 (default `0.625rem` — a legend swatch's inline- and block-size, category and marker rows alike), and
 `--lr-sequence-strip-legend-marker-bg` (default `var(--lr-color-surface-raised)` — the neutral chip
 background behind the marker legend row's bar; it stands in for "any cell", so it deliberately
-matches no category color), and `--lr-sequence-strip-disabled-opacity` (default `var(--lr-opacity-disabled)` — opacity of
-a cell whose activated item sets `disabled`); the tooltip also consumes shared tokens
+matches no category color), `--lr-sequence-strip-disabled-opacity` (default `var(--lr-opacity-disabled)` — opacity of
+a cell whose activated item sets `disabled`), `--lr-sequence-strip-selected-color` (default
+`var(--lr-color-text)` — colour of the persistent selection ring on a cell whose index is in
+`selectedIndex`), and `--lr-sequence-strip-selected-focus-color` (default
+`var(--lr-focus-ring-color)` — colour of that same ring while the cell also has keyboard focus); the
+tooltip also consumes shared tokens
 `--lr-color-surface`, `--lr-color-text`, `--lr-font-size-xs`, `--lr-radius`, and `--lr-shadow`, and
 the legend consumes `--lr-space-2xs`, `--lr-space-xs`, `--lr-space-s`, `--lr-font-size-xs`,
 `--lr-color-text-quiet`, and `--lr-radius-xs`.
@@ -14660,8 +14774,9 @@ owns none of that.
 - `statusDetail: string = ''` (attribute `status-detail`) — appended to the status line
 - `durationMs: number | null = null` (attribute `duration-ms`) — formatted into the status line
 - `selected: boolean = false` (reflected)
-- `compact: boolean = false` (reflected) — tighter card padding for dense canvases and palette
-  previews; the border, background, shadow and the `selected`/`status="running"` treatments all stay
+- `compact: boolean = false` (reflected) — tighter card padding, row gap, and header icon-to-heading
+  gap for dense canvases and palette previews; the border, background, shadow and the
+  `selected`/`status="running"` treatments all stay
 - `inputs: readonly FlowHandle[] = [{ id: 'in' }]`, `outputs: readonly FlowHandle[] = [{ id: 'out'
 }]` (attribute: false) — detached, frozen snapshots of at most the first 10,000 readonly
   `{ id, label? }` handles; blank ids and later duplicates are omitted first-valid/first-wins
@@ -14683,7 +14798,9 @@ carries no card chrome of its own), `card` (the bordered, filled node card), `he
 
 **Themeable custom properties:** `--lr-flow-node-min-inline-size` (default `11rem`),
 `--lr-flow-node-compact-padding` (default `var(--lr-space-xs)`) and `--lr-flow-node-compact-gap`
-(default `var(--lr-space-2xs)`) — `[part="card"]`'s padding and row gap while `compact` — and
+(default `var(--lr-space-2xs)`) — `[part="card"]`'s padding and row gap while `compact`;
+`--lr-flow-node-compact-header-gap` (default `var(--lr-space-2xs)`) — `[part="header"]`'s own
+icon-to-heading gap while `compact` — and
 `--lr-flow-node-selected-outline-color` (default `var(--lr-color-brand)`) — the card's outline color
 while `selected`. Like the other state-scoped custom properties here, it is an inline `var()`
 fallback at its point of use rather than a `:host` declaration, so it can be set on the element _or any
@@ -15057,9 +15174,15 @@ ring stays intact. `--lr-context-meter-selected-arc-stroke` (default `16`, in th
 one bounding box, so a selected arc reports itself by thickening in place rather than by an outline
 that would trace the whole ring identically for every selection.
 `--lr-context-meter-disabled-opacity` (default `var(--lr-opacity-disabled)`) dims a band or legend row whose entry sets
-`disabled`; the band keeps its own colour, since that colour is the datum. Otherwise the component consumes shared tokens
+`disabled`; the band keeps its own colour, since that colour is the datum. Each `data-tone` band
+color is independently retintable, scoped to just this component rather than the shared token
+every other component also reads: `--lr-context-meter-tone-brand-bg` (default
+`var(--lr-color-brand)`), `--lr-context-meter-tone-success-bg` (default `var(--lr-color-success)`),
+`--lr-context-meter-tone-warning-bg` (default `var(--lr-color-warning)`) and
+`--lr-context-meter-tone-danger-bg` (default `var(--lr-color-danger)`) — each read by the bar
+segment, its legend swatch, and (as the `stroke`) the ring shape's arc, so all three surfaces for a
+tone stay in sync. Otherwise the component consumes shared tokens
 `--lr-space-xs`, `--lr-color-text-quiet`, `--lr-font`, `--lr-radius`, `--lr-color-border`,
-`--lr-color-brand`, `--lr-color-success`, `--lr-color-warning`, `--lr-color-danger`,
 `--lr-transition-base`.
 
 **Optional peer deps:** none.
@@ -15094,8 +15217,10 @@ bar/ring either: an over-`total` `segments` array renders as a fully (not over-)
 later segments truncated or squeezed to zero width/arc-length as the budget runs out. `total <= 0`
 (or non-finite) renders zero segments — an empty track/ring — and the announced summary falls back to
 just `"{used} used"` with no `"of {total}"` clause, regardless of what's in `segments`. Ring geometry
-(a 40-radius circle, 12px stroke, centered at 50,50) intentionally matches `lr-gauge`'s own radial
-numbers, so the two circular-meter components in the library share one visual scale.
+(a 40-radius circle centered at 50,50) has its RADIUS/CENTER match `lr-gauge`'s own radial numbers,
+so both components' rings sit on the same circle within their viewBox. The stroke does not match:
+at 12px it is intentionally heavier than `lr-gauge`'s 10px, since tightly-packed multi-tone arcs
+need more width to stay visually distinct than a gauge's single fill arc.
 
 **Known gotchas:**
 
@@ -15153,6 +15278,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
@@ -15166,8 +15296,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
@@ -15496,21 +15628,28 @@ visible label element, so slotted/property/localized label text is also the anno
 effective native validity, including custom errors and own/fieldset validation barring.
 `lr-invalid` is a cancelable bubbling/composed alias; vetoing it suppresses the native invalid
 default. Run, save, load, and delete share one two-phase contract: cancelable
-`lr-before-query-run`, `lr-before-query-save`, `lr-before-query-load`, and
-`lr-before-query-delete` requests precede any local effect; non-cancelable `lr-query-run`,
+`lr-query-run-request`, `lr-query-save-request`, `lr-query-load-request`, and
+`lr-query-delete-request` requests precede any local effect; non-cancelable `lr-query-run`,
 `lr-query-save`, `lr-query-load`, and `lr-query-delete` notifications follow only when accepted.
-The matching before/accepted pair reuses one frozen payload: `{ query }` for run,
+The matching request/accepted pair reuses one frozen payload: `{ query }` for run,
 `{ name, query }` for save, `{ queryId, query }` for load, and `{ queryId }` for delete.
 Run validates before its request. Save veto preserves the draft name. Load requests frozen
 `{ queryId, query }` before changing `value`, so veto preserves the current query; its accepted event
 fires after the new value is applied. Delete remains controlled, so the host removes the accepted
-id from `savedQueries`. The full set is `lr-input`, `lr-validity-change`, `lr-invalid`, and those
-eight phased action events.
-
-Migration note: veto save in `lr-before-query-save`, not `lr-query-save`; the existing
-`lr-query-*` action events are accepted, non-cancelable notifications. **Slots:** `actions`,
+id from `savedQueries`. Each request also fires a **deprecated** `lr-before-query-run` /
+`lr-before-query-save` / `lr-before-query-load` / `lr-before-query-delete` alias immediately after
+its canonical `-request` counterpart, from the same gesture with the same frozen detail; either
+event may veto. The aliases are slated for removal in 21.0.0 — migrate listeners to the
+`lr-query-*-request` names. The full set is `lr-input`, `lr-validity-change`, `lr-invalid`, and
+those twelve phased action events (four requests, four deprecated aliases, four accepted
+notifications).
+
+Migration note: veto save in `lr-query-save-request` (or its deprecated `lr-before-query-save`
+alias), not `lr-query-save`; the existing `lr-query-*` action events are accepted, non-cancelable
+notifications. **Slots:** `actions`,
 `label`, `hint`, `error`. **CSS
-parts:** `base`, `label`, `hint`, `error` (the three form-control chrome parts every
+parts:** `base`, `form-control-label` (`label` remains as a compatibility alias on the same node),
+`hint`, `error` (the three form-control chrome parts every
 form-associated control in this library exposes — see `lr-select`), `path-fields`, `start-input`,
 `end-input`, `relationship-picker`, `relationship-chips`, `node-type-picker`, `node-type-chips`,
 `direction`, `filter-group`, `min-hops`, `max-hops`, `footer`, `run-button`, `save-button`,
@@ -16838,7 +16977,9 @@ toggle button. Not emitted when a consumer assigns `fullscreen` directly), `lr-v
 (cancelable; `detail: { viewId }` is the view proposed by a header view-toggle click. Call
 `preventDefault()` to leave `activeViewId` unchanged. Not emitted when a consumer assigns
 `activeViewId` directly), `lr-view-change` (non-cancelable; `detail: { viewId }`, the accepted
-active view's `viewId`. Not emitted when a consumer sets `activeViewId` directly), and
+active view's `viewId`. Also emitted when a `views` reassignment drops the currently-active view,
+forcing a fallback to the first remaining view. Not emitted when a consumer sets `activeViewId`
+directly, even to a now-invalid id), and
 `lr-activate` (non-cancelable; `detail: { value }` — note the key is `value`, not `viewId` — is the
 activated view's `viewId`, fired on **every** accepted header view-toggle activation whether or not
 `activeViewId` actually moved. `lr-view-request` stays the veto point, and a vetoed activation emits
@@ -16902,6 +17043,17 @@ rendering is unchanged.
 _hover_ state, and the `:hover` rule wraps its selector in `:where()` so a consumer's own
 `::part(view-toggle):hover` override wins without `!important`.
 
+`--lr-widget-collapse-button-hover-bg` (default `var(--lr-color-brand-quiet)`) and
+`--lr-widget-collapse-button-hover-color` (default `var(--lr-color-brand)`), plus
+`--lr-widget-fullscreen-button-hover-bg` (default `var(--lr-color-brand-quiet)`) and
+`--lr-widget-fullscreen-button-hover-color` (default `var(--lr-color-brand)`), are
+the same inline-`var()`-fallback shape for `[part="collapse-button"]` and `[part="fullscreen-button"]`
+respectively; each button's pressed fill mixes from its own `-hover-bg` token. Before these existed,
+both buttons read the library-wide `--lr-color-brand-quiet`/`--lr-color-brand` tokens directly, so a
+consumer retinting those tokens upstream to change only the view toggle's hover (the reason the
+view-toggle pair above exists) also silently repainted these two buttons; each now has its own scoped
+escape hatch, independent of the other and of the view toggle.
+
 **Optional peer deps:** none.
 
 ```html
@@ -17020,8 +17172,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.
@@ -18130,6 +18284,8 @@ resolves.
 
 - `--lr-segmented-track-gap` — Gap between segments. Default: `var(--lr-size-0-125rem)`.
 - `--lr-segmented-track-radius` — Track corner radius. Default: `var(--lr-radius)`.
+- `--lr-segmented-segment-radius` — Each segment's own corner radius, independent of the track's.
+  Default: `calc(var(--lr-form-control-radius) * 0.7)`.
 - `--lr-segmented-track-padding` — Track inset padding. Default: `var(--lr-size-0-125rem)`.
 - `--lr-segmented-track-bg` — Background of the `base` track. Undeclared by default (transparent),
   matching its own current absence of a background.
@@ -19949,11 +20105,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.
 
@@ -23674,10 +23833,14 @@ Tooltip motion resolves `tooltip.show` / `tooltip.hide` through the public anima
 The same per-element/global precedence, RTL keyframe selection, token-timing fallback,
 reduced-motion flattening, and null-disable lifecycle rules documented for `lr-popover` apply.
 
-**Slots:** both mapped shapes are supported. Web Awesome uses named `trigger` plus default tooltip
-content. Shoelace uses the default slot for the trigger and `slot="content"` (or the `content`
-property) for tooltip content. A named trigger always selects the first shape; without one, an
-explicit content source makes the default slot unambiguously the trigger.
+**Slots:** both mapped shapes are supported, plus a Lyra-original addition. `trigger` (the
+highest-priority interaction/ARIA owner, mirroring `<lr-popover>`'s own `trigger` slot) is not a
+Web Awesome shape: `wa-tooltip` has only its single unnamed default slot for tooltip content, and
+its own anchor mechanism is the `for` attribute plus the unrelated `trigger` activation-mode
+attribute documented above. Shoelace uses the default slot for the trigger and `slot="content"`
+(or the `content` property) for tooltip content. A named `trigger` slot always selects that shape;
+without one, an explicit content source (`slot="content"` or the `content` property) makes the
+default slot unambiguously the trigger, matching Shoelace.
 
 **CSS parts:** `popup base tooltip base__popup` are aliases on the same wrapper; `trigger`; `body`;
 and `arrow base__arrow` (rendered unless suppressed). The arrow also carries the resolved side —
@@ -23991,6 +24154,9 @@ presence-based, so an explicitly empty value remains empty rather than invoking
 fallback, and the private `--_lr-progress-track-height` is the `size` property's own tier value,
 `1rem` at the `m` default, unchanged),
 `--lr-progress-track-color` (default `var(--lr-color-brand-quiet)`),
+`--lr-progress-track-radius` (default `var(--lr-radius-pill)`; `indicator`'s `border-radius:
+inherit` picks up the same value, so retuning the track retunes both without a
+`::part(track)`/`::part(indicator)` rule),
 `--lr-progress-indicator-color` (default `var(--lr-progress-indicator-variant-color)`), and
 `--lr-progress-label-color` (default `var(--lr-color-text)`). Upstream aliases are `--height` and
 `--track-height`, plus `--track-color`, `--indicator-color`, and `--label-color`.
@@ -24884,7 +25050,10 @@ hover, `--lr-export-button-hover-background`, `--lr-export-button-hover-color` a
 the current `appearance` resolves to and leaves the other paints alone, so they are also the way to
 keep `appearance="outlined"` chrome while returning its label to neutral text — `outlined` paints
 the label `--lr-color-brand` and, unlike `lr-button`, this component has no `variant` of its own to
-opt out. Before 18.4.0 none of these existed and the only lever was `::part(trigger)`. Plus shared
+opt out. Before 18.4.0 none of these existed and the only lever was `::part(trigger)`.
+`--lr-export-button-gap` (default `var(--lr-space-xs)`, constant across the `size` ladder) and
+`--lr-export-button-radius` (default `var(--lr-radius)`) retune the trigger's icon/label gap and
+corner radius without a `::part(trigger)` rule. Plus shared
 tokens, including `--lr-popover-viewport-clamp` (default `92vw`) — the shared narrow-viewport ceiling the `menu`'s max-inline-size is `min()`ed
 against, alongside its own `20rem` cap and the positioner's available space. See `lr-tour` for the
 shared-clamp note.
@@ -25750,13 +25919,16 @@ renders `open="false"` on first paint)
 `--lr-color-brand-quiet` token, so a consumer can retheme just this highlighted/active row without
 repainting every other component that reuses the same shared token.
 `--lr-mention-popover-option-disabled-opacity` (default `0.5`) — opacity of a row whose `items`
-entry sets `disabled`. Plus shared tokens —
+entry sets `disabled`. `--lr-mention-popover-option-active-color` (default `var(--lr-color-brand)`)
+— text color of the `aria-selected="true"` (keyboard-highlighted) suggestion row, independent of
+`--lr-mention-popover-option-active-bg`: the same component-scoped indirection over
+`--lr-color-brand`, applied to the row's own sibling text-color rule. Plus shared tokens —
 `--lr-space-xs`/`-s`/`-m` (popup padding,
 row padding/gap), `--lr-radius`
 (row corners — the popup's own corner is the overlay family's, below),
 `--lr-transition-fast` (open/close
-transition), `--lr-color-brand` (selected-row
-text), `--lr-color-text-quiet`/`--lr-color-text` (description text, full-contrast on the active
+transition),
+`--lr-color-text-quiet`/`--lr-color-text` (description text, full-contrast on the active
 row), and `--lr-popover-viewport-clamp` (default `92vw`) — the shared narrow-viewport ceiling the
 popup's max-inline-size is `min()`ed against, alongside its own `24rem` cap and the positioner's
 available space. See `lr-tour` for the shared-clamp note.
@@ -25890,6 +26062,14 @@ over an already-formatted string (`<lr-code-block>`'s `language="diff"` only lex
 string the consumer already unified-diffed; it has no two-string-compare entry point of its own).
 First-party invention (no Web Awesome equivalent).
 
+Adopts `DocumentAnchorTarget`: a `line-range` anchor's `start` (and, for `highlights`, the optional
+`end`) addresses the 0-based index into the rendered diff's own op sequence — not an old-file/
+new-file source line number, since those diverge on any insertion or deletion. `scrollToAnchor()`
+resolves it, and both it and search navigation transparently expand (and, for a `highlights` range,
+paint through) any `contextLines` fold currently hiding the target run instead of leaving it
+inaccessible behind a static marker. `search()` is a locale-aware case-insensitive substring match
+over each rendered line's own text, one match per line ordered by that same op index.
+
 **Properties:**
 
 - `oldText: string = ''` (attribute: false) — the "before" text. Default `''` renders an
@@ -25917,6 +26097,8 @@ First-party invention (no Web Awesome equivalent).
   side. Larger input renders the localized `diffViewTooLarge` fallback without computing or
   highlighting the diff. `Infinity` relaxes this line-count ceiling, but the fixed aggregate
   character and comparison-work ceilings remain in force.
+- `anchorKinds: readonly LyraAnchorKind[] = ['line-range']` (this viewer's supported
+  `LyraAnchor.kind` values for the shared anchor-target contract).
 
 Grammar entries are read from own enumerable data fields into a bounded frozen map. A getter,
 unreadable field, non-enumerable field, or malformed proxy branch is skipped without preventing a
@@ -25924,6 +26106,13 @@ later valid grammar from being used; grammar values themselves remain opaque to
 Non-enumerable names do not consume language slots, but every inspected name counts toward the
 20,000 structural ceiling.
 
+**Methods:** `search(query)` resolves the match count via a case-insensitive substring match over
+each rendered line's own text, ordered by `line-range` op index (empty/whitespace query behaves like
+`clearSearch()`); `searchNext()`/`searchPrevious()` advance/step back through matches (wrapping,
+resolving `false` when there are none); `clearSearch()` clears the query, matches, and painted
+marks. `scrollToAnchor(target)` (inherited from `DocumentAnchorTarget`) resolves a `line-range`
+anchor or a `highlights` id string.
+
 **Events:**
 
 - `lr-copy` (`detail: LyraClipboardWriteSuccess`, `{ ok: true; text: string }`) — the frozen full
@@ -25932,6 +26121,14 @@ Non-enumerable names do not consume language slots, but every inspected name cou
 - `lr-copy-error` (`detail: LyraClipboardWriteFailure`) — the frozen failure outcome contains
   `ok: false`, the text, a `LyraCopyErrorReason`, and the original error. The reason is
   `'unsupported' | 'denied' | 'failed'`.
+- `lr-search-change` (`detail: { query, matchCount, matchCountExact, activeIndex }`) — from
+  search/navigation/clear, and effective-locale re-evaluation. Search accepts at most 4,096 query
+  code units, scans at most 4,000,000 line code units, and retains at most 10,000 matches;
+  `matchCountExact=false` identifies a ceiling-truncated lower bound.
+- `lr-highlight-activate` (`detail: { highlightId }`) — a `highlights` entry's
+  `[part="line-highlight-action"]` button was clicked or activated via Enter/Space.
+- `lr-anchor-result` (`detail: { found }`) — fired after an `anchor` assignment or a
+  `scrollToAnchor()` call.
 
 The copy button stays in its resting state until `writeText()` resolves. Success renders and
 announces localized `copied`; failure renders and announces localized `copyFailed`. A newer
@@ -25943,13 +26140,29 @@ retires an older pending outcome, so stale writes cannot confirm or fail a hidde
 **CSS parts:** `base` (the root wrapper), `line` (a single line; carries
 `data-type="equal"|"add"|"remove"|"empty"|"fold"` — `"empty"` is an unbalanced-replace placeholder cell in
 `layout="split"` and never carries a `+`/`-` prefix; `"fold"` is the localized unchanged-lines
-marker), `copy-button` (the copy affordance, only
-rendered while `copyable`), `limit` (the localized over-`maxLines` fallback), `side` (one column in
-`layout="split"`, `data-side="old"|"new"`).
+marker — plus `data-match`/`data-active-match` while a search result covers it, and
+`data-highlight` (the resolved tone, default `accent`) with `data-active-highlight` while a
+`highlights` entry covers it), `line-highlight-action` (the focusable button a resolved
+`highlights` entry adds to the line it first covers; emits `lr-highlight-activate`), `copy-button`
+(the copy affordance, only rendered while `copyable`), `limit` (the localized over-`maxLines`
+fallback), `side` (one column in `layout="split"`, `data-side="old"|"new"`), `anchor-live-region`
+(an aria-hidden, non-live shadow mirror of the latest anchor-jump message; the spoken copy is
+appended to the shared document-level polite sink only while the viewer and its composed ancestors
+are exposed to the accessibility tree).
 
 **Themeable custom properties:** `--lr-diff-view-max-height` (default `none` — an independently
 settable scroll cap on `[part="base"]`; the `maxHeight` property writes the same custom property
-inline on `[part="base"]`), `--lr-diff-view-font` (default `var(--lr-font-mono)`), plus
+inline on `[part="base"]`), `--lr-diff-view-font` (default `var(--lr-font-mono)`),
+`--lr-diff-view-match-color`/`--lr-diff-view-active-match-color` (default
+`var(--lr-color-warning)` for both — outline of a line carrying a non-active/active search match),
+`--lr-diff-view-highlight-accent-background` (default `var(--lr-color-brand-quiet)`),
+`--lr-diff-view-highlight-success-background` (default `var(--lr-color-success-quiet)`),
+`--lr-diff-view-highlight-warning-background` (default `var(--lr-color-warning-quiet)`),
+`--lr-diff-view-highlight-danger-background` (default `var(--lr-color-danger-quiet)`), and
+`--lr-diff-view-highlight-neutral-background` (default `var(--lr-color-surface-raised)`) —
+background of a `highlights` line by tone,
+`--lr-diff-view-highlight-active-outline` (default `var(--lr-color-brand)` — outline of the line
+whose covering highlight is `activeHighlightId`), plus
 shared tokens `--lr-color-border`/`-surface`/`-success`/`-success-quiet`/`-danger`/
 `-danger-quiet`/`-text`, `--lr-radius`, `--lr-space-xs`/`-s`, `--lr-font-size-sm`,
 `--lr-line-height-snug`, `--lr-focus-ring-*`.
@@ -27689,10 +27902,12 @@ large collection is invisible until someone walks the data by hand. Both `chorop
 reduced figure in the feature — a log, a bucket, an index — and keep the exact value in your own
 payload beside the map.
 
-- `label: string = ''` — purpose-specific accessible name for MapLibre's actual focusable canvas.
+- `label?: string` — purpose-specific accessible name for MapLibre's actual focusable canvas.
   A nonempty host `aria-label` remains on the host and is not duplicated onto the canvas; the canvas
-  uses `label` or the localized map name. An explicitly empty host `aria-label` is preserved as an
-  empty canvas name. The non-semantic `[part="base"]` wrapper is not named instead.
+  uses `label` or the localized map name. Omitting `label` localizes the default `map` message; an
+  explicit empty string suppresses that default and renders an empty canvas name. An explicitly
+  empty host `aria-label` is separately preserved as an empty canvas name. The non-semantic
+  `[part="base"]` wrapper is not named instead.
 
 **Authoring types:** `LyraMapLegendEntry`, `LyraMapLegendPattern`, `LyraMapLegendProjection`, `LyraMapChoroplethLayer`,
 `LyraMapGeoJsonDataLayer`, `LyraMapDataLayerKind`, `LyraMapClusterOptions`, `LyraMapHeatmapOptions`,
@@ -28012,6 +28227,9 @@ reimplemented.
   behavior exactly, and a negative, `NaN`, or `Infinity` override is normalized to `0` via
   `finiteCount` rather than corrupting every later comparison.
 - `readonly dragging: boolean` — `true` during an active drag session
+- `size: LyraSize = 'm'` (reflected) — density tier for the overlay's padding, icon and
+  instructional text; identical contract and scale to `lr-file-input`'s own `size`, so a drop-zone
+  can match a neighboring compact `lr-file-input` in the same dense layout.
 
 **Events:** `lr-files` (`detail: LyraDropZoneFilesDetail`, with fresh frozen readonly `files` and
 `rejected` arrays and frozen rejected-file records, plus `remainingFiles`/`remainingTotalSize`
@@ -28038,8 +28256,9 @@ while one exists).
 `--lr-drop-zone-overlay-border-color` (default `var(--lr-color-brand)`, the dashed overlay border in
 its neutral drag state, before an accept/reject verdict) and `--lr-drop-zone-overlay-bg` (default
 `color-mix(in srgb, var(--lr-color-brand) 8%, transparent)`, that same neutral state's fill),
-`--lr-drop-zone-overlay-font-size` (default `var(--lr-font-size-md-sm)`),
-`--lr-drop-zone-overlay-icon-size` (default `var(--lr-font-size-xl)`),
+`--lr-drop-zone-overlay-font-size` (default `var(--lr-font-size-md-sm)`, retuned per `size` tier),
+`--lr-drop-zone-overlay-icon-size` (default `var(--lr-font-size-xl)`, retuned per `size` tier),
+`--lr-drop-zone-overlay-padding` (default `var(--lr-space-l)`, retuned per `size` tier),
 `--lr-drop-zone-overlay-gap` (default `var(--lr-space-xs)`), and the drag accept/reject highlight —
 `--lr-drop-zone-accept-border-color`/`--lr-drop-zone-accept-bg` (defaults `var(--lr-color-success)`/
 `color-mix(in srgb, var(--lr-color-success) 12%, transparent)`) and
@@ -29225,7 +29444,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`.
@@ -29500,11 +29723,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.
 
@@ -30115,11 +30345,13 @@ convenience; every enabled row is independently reachable through ordinary seque
 native `FocusEvent`s (bubbling and composed, preserving `relatedTarget`).
 `lr-video-change` is bubbling and composed but non-cancelable, with exact
 detail `{ previousIndex, currentIndex, video }`. `video` is a fresh detached, recursively frozen plain-data snapshot with
-exact shape `{ title, poster, sources, tracks }`, not the live child element. `sources` contains
-fresh `{ src, type, media }` records for the child's direct `src` and `<source>` declarations;
-`tracks` contains fresh `{ src, kind, srclang, label, default }` records. A listener that needs to
-annotate or reshape the payload must create its own mutable copy; the dispatched detail and every
-nested record/array reject mutation.
+exact shape `{ title, poster, sources, tracks }`, not the live child element, or `null`. `sources`
+contains fresh `{ src, type, media }` records for the child's direct `src` and `<source>`
+declarations; `tracks` contains fresh `{ src, kind, srclang, label, default }` records. A listener
+that needs to annotate or reshape the payload must create its own mutable copy; the dispatched
+detail and every nested record/array reject mutation. Also fired when a light-DOM mutation (a video
+removed, or every remaining video made `inert`/disabled) leaves no enabled video to replace a
+previously active one: `video` is `null` and `currentIndex` is `-1` in that case.
 
 **Slot:** the default slot accepts direct `<lr-video>` children. Nested videos and other elements
 are not playlist items.
@@ -30646,7 +30878,7 @@ These named interfaces and helper signatures are available to typed integrations
   `LyraVideoPlaylistChangeDetail {
     readonly previousIndex: number;
     readonly currentIndex: number;
-    readonly video: LyraVideoPlaylistVideo;
+    readonly video: LyraVideoPlaylistVideo | null;
   }`
   Import: `@aceshooting/lyra-ui/components/media/video-playlist/video-playlist.class.js`.
   `LyraVideoPlaylistItem {
@@ -31096,17 +31328,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
@@ -31654,11 +31893,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`.
 
@@ -31742,10 +31984,12 @@ maxSamples?)` appends finite raw samples and optionally retains only the newest
 `appendData()` remains a working compatibility adapter (no longer deprecated); prefer
 `appendSamples()` for new code.
 
-**Events:** `lr-zoom`, `lr-datum-activate`, `lr-point-click`, `lr-before-datum-visibility-change`
-(cancelable), `lr-datum-visibility-change`, `lr-before-legend-visibility-change` (cancelable), and
+**Events:** `lr-zoom`, `lr-datum-activate`, `lr-point-click`, `lr-datum-visibility-change-request`
+(cancelable), `lr-datum-visibility-change`, `lr-legend-visibility-change-request` (cancelable), and
 `lr-legend-visibility-change` — inherited; `lr-point-click`'s `index` is the bucket index and
 `label` the generated bucket range string (`"lo–hi"`, both bounds at one decimal place).
+`lr-before-datum-visibility-change`/`lr-before-legend-visibility-change` are deprecated aliases of
+the two `*-request` events above (removal not before 21.0.0).
 The inherited datum-visibility events apply only to radial controllers; the histogram keeps its
 bar controller and dataset legend even with `legend-mode="datum"`.
 
@@ -31838,6 +32082,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
@@ -31867,11 +32112,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
@@ -32998,7 +33246,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,
@@ -34458,7 +34713,11 @@ unbroken values from widening a 320px allocation.
 
 **Properties:** `src: string = ''` — URL to fetch and parse. `name: string = ''` — accessible label,
 used as `<lr-map>`'s `label` and the root's `aria-label` (falling back to the localized
-`geojsonViewLabel` when unset). A host `aria-label` takes precedence over `name`. The shared
+`geojsonViewLabel` when unset). A host `aria-label` takes precedence over `name`.
+`maxHeight: string = ''` (attribute `max-height`) is a CSS length that caps `[part="base"]` —
+covering the loaded map, the serialized metadata, and the missing-peer fallback alike — by writing
+`--lr-geojson-viewer-max-height` inline on it; invalid CSS `max-height` values, declaration breaks,
+and `url()` are ignored. The shared
 text-viewer contract adds `highlights`, `activeHighlightId`, `anchor`, and
 `anchorKinds` (`['text-quote', 'fragment']`), plus `search()`, `searchNext()`, `searchPrevious()`,
 `clearSearch()`, and `scrollToAnchor()` for the ordinary-DOM serialized feature metadata and status
@@ -34500,6 +34759,10 @@ body text: `error` is `--lr-color-danger` (matching `lr-docx-viewer`/`lr-email-v
 but working state, since the `lr-json-viewer` fallback below it still renders the data, not a failure
 -- and `status` is the quiet `--lr-color-text-quiet` metadata tone.
 
+**Themeable custom properties:** `--lr-geojson-viewer-max-height` (default `none`) — maximum block
+size of `[part="base"]`, matching every other viewer in this family. It is also settable via the
+`maxHeight` property, which writes this token inline on `[part="base"]`.
+
 The canonical tag is registered by importing `geojson-viewer/geojson-viewer.js`; the permanent
 compatibility tag and old deep route remain available through `geojson-view/geojson-view.js`.
 Remote
@@ -37341,7 +37604,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.
 
@@ -37379,7 +37644,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
@@ -37428,7 +37695,9 @@ opens). `feedbackPending: boolean` (read-only, nonreflecting) — true only whil
 feedback control awaits settlement; it has no `feedback-pending` attribute or change event.
 `revealOnInteraction: boolean = false` (reflected, attribute `reveal-on-interaction`) — hides
 the bar until the closest `lr-chat-message` ancestor is hovered, or the toolbar contains focus.
-`label: string = ''` — accessible name override for the toolbar. `accessibleLabel: string | null =
+`label?: string` — accessible name override for the toolbar. Omitting it localizes the default
+`messageActionsLabel` message; an explicit empty string suppresses that default and renders no
+label. `accessibleLabel: string | null =
 null` (attribute `aria-label`) — overrides the toolbar's computed accessible name, winning over
 `label` and the localized default; attribute-reflects from a host-level `aria-label`.
 
@@ -37740,8 +38009,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.
@@ -38490,8 +38760,10 @@ custom-value editor: they do not navigate options, commit a selection or custom
 popup. Ordinary keyboard behavior resumes after composition.
 
 **Exported types:** `LyraVoiceCatalogEntry extends LyraCatalogEntry { language?: string;
-description?: string; previewUrl?: string }` — `language`/`description` render as a quiet
-`[part="option-meta"]` second line. Voice catalogs use the shared
+description?: string; previewUrl?: string; icon?: string }` — `language`/`description` render as a
+quiet `[part="option-meta"]` second line; `icon` is an optional literal icon hint (for example, an
+emoji), rendered decoratively as the leading `[part="option-icon"]`, matching
+`lr-model-select`'s identical `LyraModelCatalogEntry.icon` field. Voice catalogs use the shared
 `LyraCatalog<LyraVoiceCatalogEntry>` homogeneous readonly union documented under `lr-model-select`,
 including the shared `disabled` field: a disabled voice row cannot be selected by click or keyboard
 and is stepped over by arrow-key/Home/End navigation, but its own `[part="option-preview"]` stays
@@ -38582,7 +38854,8 @@ reports no violation and publishes neither `:state(invalid)` nor
 `:state(user-invalid)`.
 
 **CSS parts:** `form-control` (the complete field frame), `form-control-label`, `trigger` (closed-dropdown mode), `combobox`/`combobox-input`
-(free-text mode), `provider-badge`, `listbox`, `option`, `option-label`, `option-meta` (the quiet
+(free-text mode), `provider-badge`, `listbox`, `option`, `option-icon` (an object-shaped catalog
+row's optional decorative leading icon), `option-label`, `option-meta` (the quiet
 `language · description` second line), `option-badge` (the "not in catalog" badge on a synthetic
 stale-value row), `option-preview` (a pointer-only per-row preview icon, `tabindex="-1"`,
 `aria-hidden`), `preview-button` (the standalone, keyboard-reachable preview toggle beside the
@@ -38816,8 +39089,14 @@ are still derived from the full sequence first, in the same linear prepass, so a
 stays stable even once an earlier citation rolls out of the rendered window. Opt in for a message
 that can grow an unusually large number of interleaved parts (e.g. a long agentic run with many
 tool-call/tool-result pairs), where unbounded live DOM can visibly stall the main thread.
-`renderPart?: MessagePartRenderer` (attribute: false), where returning `undefined` delegates that
-part to the built-in renderer; `accessibleLabel: string | null = null` (attribute `aria-label`).
+`renderPart?: MessagePartRenderer` (attribute: false) — returning `undefined` for a part delegates
+it to the built-in renderer, keeping every built-in affordance intact; any other return fully
+replaces that part's built-in rendering, including every interactive affordance the built-in
+renderer would otherwise wire up for it (the `error` part's retry button's `lr-part-retry`, a
+`citation` part's activation `lr-citation-select`, and the composed `<lr-tool-call-chip>`/
+`<lr-tool-result-view>`/`<lr-attachment-chip>`/`<lr-widget-renderer>` children's own events) — a
+host overriding an interactive part type must reimplement whatever of that interaction it still
+wants; `accessibleLabel: string | null = null` (attribute `aria-label`).
 
 Unsupported direct or `content-mode` attribute values normalize and reflect as `markdown`.
 
@@ -38910,7 +39189,10 @@ LyraAttachmentCapability[] = ['files', 'image', 'audio']`, `mentionItems: readon
 `voiceCatalog?: LyraCatalog<LyraVoiceCatalogEntry>`,
 `sources: readonly LyraSourceEntry[] = []`, `selectedSourceIds: readonly string[] = []`, and `queue:
 readonly PromptQueueItem[] = []` (all attribute: false); `model: string = ''`; `voice: string = ''`;
-`label: string = ''`; `accessibleLabel: string | null = null` (attribute `aria-label`).
+`label?: string` — accessible name for the prompt section. Omitting it localizes the default
+`promptInputLabel` message; an explicit empty string suppresses that default and renders no label.
+`accessibleLabel: string | null = null` (attribute `aria-label`) — wins over `label` and the
+localized default.
 Source roots and queued prompts require unique nonblank `id` values; malformed rows and later
 duplicates are omitted first-wins before section gating and child forwarding. Controlled selected
 source ids use the same unique nonblank projection.
@@ -38980,13 +39262,16 @@ receives focus. Removing an unfocused row does not move focus.
 
 **Properties:** `items: readonly PromptQueueItem[] = []` (attribute: false); `editable: boolean = true`
 (reflected, string-aware true-default converter); `disabled: boolean = false` (reflected);
-`label: string = ''`; `accessibleLabel: string | null = null` (attribute `aria-label`).
+`label?: string`; `accessibleLabel: string | null = null` (attribute `aria-label`).
 `PromptQueueItem = { id: string; value: string; attachments?: readonly DocumentRef[]; createdAt?: number;
 metadata?: Record<string, unknown> }`.
 
 Item ids are occurrence identities. Empty ids and later duplicates are ignored before rendering or
 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.
+editable and read-only rows; the host `label` is also the visible queue heading. Omitting `label`
+localizes the default `promptQueueLabel` message; an explicit empty string suppresses that default
+and renders no visible heading (`accessibleLabel` still overrides the region's accessible name
+independently).
 
 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
@@ -39015,7 +39300,10 @@ Nonmodal, Escape-dismissible text-selection toolbar carrying selected text plus
 **Properties:** `open: boolean = false` (reflected); `text: string = ''`;
 clone-owned `anchor: DocumentLocator | null = null`, `rect: DOMRectReadOnly | null = null`, and
 clone-owned `actions: readonly SelectionAction[] = ['ask', 'quote', 'cite', 'copy']` (attribute: false);
-`label: string = ''`; `accessibleLabel: string | null = null` (attribute `aria-label`).
+`label?: string` — accessible name for the toolbar. Omitting it localizes the default
+`selectionToolbarLabel` message; an explicit empty string suppresses that default and renders no
+label. `accessibleLabel: string | null = null` (attribute `aria-label`) — wins over `label` and
+the localized default.
 `SelectionAction = 'ask' | 'quote' | 'cite' | 'copy'`. Duplicate built-in names are omitted
 first-wins before rendering, roving focus, and action events. The anchor (including any path) and
 actions are bounded frozen snapshots; reassign a new record or array after changes.
@@ -39081,7 +39369,9 @@ clamped by the composed visualizer); `stream: MediaStream | null = null`; `sessi
 entry announcement identity; `entries: LyraTranscriptEntry[] = []` (attribute: false);
 `muted: boolean = false` (reflected);
 `showCapture: boolean = true` (attribute `show-capture`, reflected, string-aware true-default
-converter); `label: string = ''`. Invalid attribute or direct-property values for `state` and
+converter); `label?: string` — accessible name for the session shell. Omitting it localizes the
+default `realtimeSessionLabel` message; an explicit empty string suppresses that default and
+renders no label. Invalid attribute or direct-property values for `state` and
 `voiceState` normalize to their safe defaults (`'disconnected'` and `'idle'`) through the same
 closed-set converter.
 
@@ -39530,6 +39820,7 @@ These named interfaces and helper signatures are available to typed integrations
     language?: string;
     description?: string;
     previewUrl?: string;
+    icon?: string;
     // Inherited from LyraCatalogEntry.
     id: string;
     label: string;
@@ -39699,6 +39990,8 @@ duration"`). A host `aria-label` remains on the host and is not cloned onto that
   not place links, buttons, or other controls there; use the chip activation or detail slot instead
 - Escape only dismisses the tooltip when it's open; it does not fire any event or otherwise affect
   `status`/`open` state, since the chip has no "open" state of its own beyond the tooltip
+- An open tooltip participates in shared Escape ordering even while only hovered, deferring to a
+  genuinely topmost overlay opened on top of it
 
 ---
 
@@ -40236,9 +40529,10 @@ plain text) — this component has no dependency on either.
 - `label?: string` — omitted localizes `thinkingPanelLabel` (`'Thinking'` in the built-in English
   catalog). Any supplied string is an explicit override and renders verbatim, including
   `label="Thinking"` under a non-English `.strings` catalog and `label=""`.
-- `compact: boolean = false` (reflected) — tightens the header/body padding and the header's
-  internal gap for dense transcript rows. This is only a density control: its card border and
-  surface remain, so use `frame="plain"` when surrounding message chrome already supplies them.
+- `compact: boolean = false` (reflected) — tightens the header/body padding, the header's internal
+  gap, and the header/body font size for dense transcript rows. This is only a density control: its
+  card border and surface remain, so use `frame="plain"` when surrounding message chrome already
+  supplies them.
 - `frame: LyraFrame = 'card'` (reflected) — the library-wide container-frame vocabulary
   (`'card' | 'plain'`). `'card'` keeps the bordered, filled outer container. `'plain'` removes its
   border, background, and corner radius so a nested panel does not double an existing frame;
@@ -40291,7 +40585,9 @@ pending duration/toggle accent without changing the shared brand token;
 `--lr-thinking-panel-compact-header-font-size` (default `var(--lr-font-size-sm)`) — font size of
 `[part="header"]` while `compact`; and
 `--lr-thinking-panel-compact-body-padding` (default `var(--lr-space-s)`) — `[part="body"]`
-padding while `compact`. `--lr-thinking-panel-background` (default `var(--lr-color-surface)`),
+padding while `compact`; and `--lr-thinking-panel-compact-body-font-size` (default
+`var(--lr-font-size-sm)`) — font size of `[part="body"]` while `compact`.
+`--lr-thinking-panel-background` (default `var(--lr-color-surface)`),
 `--lr-thinking-panel-border-color` (default `var(--lr-color-border)`) and
 `--lr-thinking-panel-radius` (default `var(--lr-radius)`) retune `[part="base"]`'s card chrome
 without a `::part(base)` override; the border-color hook also colors the header/body divider that
@@ -40706,7 +41002,12 @@ boolean; readonly autocapitalize?: string; readonly autoCorrect?: string; readon
 string; readonly enterKeyHint?: string }` — one `schema.properties`
   entry. `enum` is only meaningful when `type` is `'string'` (rendered as a `<lr-select>`); `const`
   enforces one exact primitive value; `title` is the display label; `description` is helper text;
-  `default` pre-fills a field whenever `value` doesn't already have that key. For a free-form
+  `default` pre-fills a field whenever `value` doesn't already have that key. For a `'string'`
+  (non-enum) or `'number'`/`'integer'` field, `const` also pre-fills the field (taking priority
+  over `default` when both are present) and renders its native control `readonly` — visible,
+  focusable and copyable, but not editable, and still submitted as the locked value. The
+  `'boolean'`/enum `<lr-select>` fields are unaffected: `const` there remains pure post-touch
+  validation, as before. For a free-form
   string field, `autocomplete`, `spellcheck`, `autocapitalize`, `autoCorrect`, `inputMode`, and
   `enterKeyHint` forward the corresponding native editing hints to the rendered text input;
   `spellcheck` defaults to `true`, and the other hints are omitted unless supplied.
@@ -40730,7 +41031,9 @@ Readonly<Record<string, ToolParamFormProperty>>; readonly required?: readonly st
   `lr-input`) as that default, but the `value` property itself is left alone until the user actually
   edits that field. JSON Schema ordinarily treats `default` as an annotation; this renderer
   deliberately materializes it before validation/submission, so a valid default can satisfy
-  `required`.
+  `required`. A `const` on a `'string'` (non-enum) or `'number'`/`'integer'` field takes priority
+  over `default` for this same materialization, and additionally renders that field's control
+  `readonly` so the locked value is visible and submitted but not editable.
 - `name: string = ''` — submission key for optional native `<form>` participation
 - `disabled: boolean = false` (reflected)
 - `customError: string | null = null` (attribute `custom-error`) — reflected consumer validation
@@ -40743,9 +41046,10 @@ Readonly<Record<string, ToolParamFormProperty>>; readonly required?: readonly st
 
 - `effectiveValue: ToolParamFormValue` — a detached, deeply frozen `value` snapshot with every
   property missing from it filled in
-  from `schema`'s own `default`; this is what actually renders and what `lr-input`'s detail carries.
+  from `schema`'s own `const` (when present) or `default`; this is what actually renders and what
+  `lr-input`'s detail carries.
   A key the user has explicitly cleared (a real own property set to `undefined`) stays cleared rather
-  than snapping back to its default — only a key genuinely absent from `value` falls back.
+  than snapping back to its `const`/default — only a key genuinely absent from `value` falls back.
 - `errors: Readonly<Record<string, string>>` — a frozen effective validation-error snapshot.
   Intrinsic errors use their schema property key; a schema-wide/serialization error or consumer
   custom-validity message uses `base`, the whole-control part. It is independent of which fields
@@ -40777,6 +41081,9 @@ Readonly<Record<string, ToolParamFormProperty>>; readonly required?: readonly st
 - `click(): void` — forwards a host click to the first generated field's control, so the form
   behaves like a single control under both a `<label>`-driven and a programmatic click; a no-op
   while `disabled`.
+- `focus(options?: FocusOptions): void` — moves focus to the first generated field's control,
+  mirroring `click()`; a no-op while `disabled`.
+- `blur(): void` — blurs whichever generated field currently holds focus.
 
 **Events:** `lr-input` (deeply frozen `detail: { value: ToolParamFormValue }` — the full detached
 current value snapshot, every property with defaults resolved, not just the field that changed),
@@ -41418,13 +41725,16 @@ element or any ancestor, and they exist because `::part(row)[data-active]` is in
 `--lr-trace-tree-max-indent` (default `var(--lr-size-12rem)`) caps visual nesting indentation;
 semantic `aria-level` remains exact at deeper levels.
 
-**Contrast note:** the active row is more than a tint. Its secondary text would sit at ~4.25:1
+**Contrast note:** the active row is more than a tint. Its secondary text would sit at ~4.17:1
 against the default tint if it stayed at `--lr-color-text-quiet`, so it rises to full-strength
 `--lr-color-text` while the row is active, and the semantic `status-text` labels are rendered as
 `color-mix(in srgb, var(--lr-color-<tone>) 75%, var(--lr-color-text))` — keeping the status hue
-(an error row stays red) while clearing the 4.5:1 floor (success 4.46 → 6.18, `denied` 4.28 →
-5.96). Both adjustments are theme-symmetric, because `--lr-color-text` flips with the color
-scheme. `[part='bar']` is deliberately untouched: it is a non-text graphic on a 3:1 floor, and its
+(an error row stays red) while clearing the 4.5:1 floor with a full point of margin or more for
+every currently shipped default tone. The exact ratio moves with every palette ramp revision
+(`src/internal/tokens/palette.styles.ts`), so no specific number is pinned here — recompute against
+the live tokens before quoting one. Both adjustments are theme-symmetric, because `--lr-color-text`
+flips with the color scheme. `[part='bar']` is deliberately untouched: it is a non-text graphic on
+a 3:1 floor, and its
 saturation is the row's primary status signal.
 
 The two properties are a **pair**. The defaults assume the active background stays on the same
@@ -41482,12 +41792,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
@@ -41509,13 +41820,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
@@ -41532,6 +41849,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`)
@@ -41992,7 +42313,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
@@ -42228,7 +42551,8 @@ menu. These composed child events surface unchanged; the inspector does not emit
 **CSS parts:** `base`, `toolbar`,
 `segments`, `segment`, `segment-header`, `segment-label`, `segment-text`, `segment-tokens`,
 `meter` (the embedded `lr-context-meter`), `citation`, `redaction` (one redaction placeholder
-marker), `truncation-boundary`, `copy-button`, `export-button`, `empty`.
+marker), `truncation-boundary`, `copy-button`, `export-button`, `empty`, `limit` (localized notice
+shown when `segments` exceeds the 500-row render ceiling).
 
 ## `lr-eval-dataset`
 
@@ -42392,7 +42716,8 @@ child events as `lr-example-claim-select` (`{ exampleId, claim }`),
 `header-label`, `progress`, `summary`, `counts`, `count`, `examples`, `example`, `example-summary`,
 `example-label`, `example-status`, `example-status-message`, `input-section`, `input`, `output-section`, `output`,
 `grounding-section`, `grounding-summary`, `tool-trace-section`, `tool-trace`, `section-heading`,
-`live-region`, `empty`.
+`live-region`, `empty`, `limit` (localized notice shown when `examples` exceeds the 500-row render
+ceiling).
 
 ## `lr-policy-summary`
 
@@ -42417,7 +42742,8 @@ resolve/acknowledge action — see `lr-tool-approval-dialog`/`lr-confirm-bar` fo
 gate.
 
 **CSS parts:** `base`, `empty`, `summary`, `count`, `state-badge`,
-`list`, `decision`, `decision-header`, `category`, `label`, `detail`, `explanation`.
+`list`, `decision`, `decision-header`, `category`, `label`, `detail`, `explanation`, `limit`
+(localized notice shown when `decisions` exceeds the 500-row render ceiling).
 
 **Themeable custom properties:** `--lr-policy-summary-count-allow-color` (default
 `var(--lr-color-success)`), `--lr-policy-summary-count-deny-color` (default
@@ -42598,7 +42924,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
@@ -42813,11 +43140,13 @@ caps visual nesting indentation while preserving complete JSON Pointer paths;
 only.
 
 Rendering is capped independently at 500 schema nodes and 500 validation issues; `limit` and
-`issue-limit` show their respective truncation as ordinary, non-live status text. Newly reaching or
-changing either ceiling after the initial baseline appends the localized message to the shared
-polite light-DOM announcement sink; initial and reconnect renders stay silent. Issues are indexed by
-path once before recursive rendering instead of rescanning the full input for every node. Cycles stop
-at the repeated node rather than recursing. **Slots:** none. **Optional peer deps:** none.
+`issue-limit` show their respective truncation as ordinary, non-live status text. When `selectedPath`
+resolves beyond the 500-node ceiling, that node and its resolvable ancestor chain reserve positions
+inside the cap ahead of ordinary traversal order, so the controlled selection remains visible. Newly
+reaching or changing either ceiling after the initial baseline appends the localized message to the
+shared polite light-DOM announcement sink; initial and reconnect renders stay silent. Issues are
+indexed by path once before recursive rendering instead of rescanning the full input for every node.
+Cycles stop at the repeated node rather than recursing. **Slots:** none. **Optional peer deps:** none.
 
 ```ts
 import '@aceshooting/lyra-ui/components/lr-json-schema-viewer.js';
@@ -42864,9 +43193,12 @@ counts, selection, and events.
 `task`, `model`, `progress`, `actions`, `cancel`, `retry`, `limit`, `empty`.
 
 At most 500 runs render, and visual indentation is capped at 12 levels while ARIA hierarchy keeps
-the logical depth. The visible `limit` text is ordinary and non-live; newly reaching or changing the
-run ceiling after the initial baseline appends the localized message to the shared polite light-DOM
-announcement sink, while initial and reconnect renders stay silent. The roving treeitem accepts
+the logical depth. When `selectedRunId` names a run beyond the 500-run ceiling, that run and its
+resolvable ancestor chain reserve positions inside the cap ahead of ordinary array order, so the
+controlled selection remains visible. The visible `limit` text is ordinary and non-live; newly
+reaching or changing the run ceiling after the initial baseline appends the localized message to the
+shared polite light-DOM announcement sink, while initial and reconnect renders stay silent. The
+roving treeitem accepts
 Enter/Space as well as pointer activation for `lr-run-activate`; cancel/retry action names include the
 run label so repeated row actions remain distinguishable to assistive technology. Progress is finite
 and clamped. **Slots:** none.
@@ -43964,10 +44296,13 @@ string; shape?: 'circle' | 'square' | 'diamond' }`, the shared `lr-graph.nodeTyp
   `aria-label` makes the host the sole overall owner (the wrapper omits its duplicate role/name);
   an explicitly empty host label stays empty on the wrapper
 
-**Events:** cancelable `lr-before-visibility-change` (`detail: { hiddenTypes }`, a frozen complete
+**Events:** cancelable `lr-visibility-change-request` (`detail: { hiddenTypes }`, a frozen complete
 next array) fires before a toggle changes state or announces it. Preventing it suppresses all three.
 `lr-visibility-change` (`detail: { hiddenTypes }`, the complete updated array) fires after an
-accepted assignment and announcement.
+accepted assignment and announcement. `lr-before-visibility-change` is a **deprecated** alias of
+`lr-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-visibility-change-request`.
 
 **Slots:** none.
 
@@ -44161,6 +44496,8 @@ ancestor to change every unset entity chip beneath it.
   `lr-entity-card` as shown above, and handle the chip's own `lr-entity-select`/`lr-entity-open`
   events for navigation.
 - A blank `entityId` disables the chip and cannot produce an activation/open event.
+- An open popover participates in shared Escape ordering even while only hovered, deferring to a
+  genuinely topmost overlay opened on top of it.
 
 ---
 
@@ -44296,7 +44633,8 @@ string; summary?: string; memberCount?: number }`; `memberCount` is a non-negati
 - `members: LyraEntity[] = []` (attribute: false) — rendered as chips, up to `maxMembers`
 - `maxMembers: number = 8` (attribute `max-members`) — remaining members collapse into a "+N"
   overflow chip
-- `compact: boolean = false` (reflected) — omits the summary excerpt and member chips
+- `compact: boolean = false` (reflected) — omits the summary excerpt and member chips, and tightens
+  `[part='base']`'s padding/gap — same convention as the sibling `lr-entity-card`'s `compact`
 - `frame: LyraFrame = 'card'` (reflected) — container treatment, in the library-wide `frame`
   vocabulary (`'card' | 'plain'`), the same property this component's sibling `lr-entity-card`
   carries. `'card'` (the default) keeps the bordered, filled, padded box; `'plain'` removes the
@@ -44317,8 +44655,10 @@ activated).
 
 **Themeable custom properties:** `--lr-community-card-bg` (default `var(--lr-color-surface)`) —
 `[part='base']`'s RESTING background, so a panel retinting its `lr-entity-card`/`lr-source-card`
-siblings can retint this card with it; `frame='plain'` still drops the fill entirely. Otherwise
-shared tokens.
+siblings can retint this card with it; `frame='plain'` still drops the fill entirely.
+`--lr-community-card-compact-padding` (default `var(--lr-space-s)`) and
+`--lr-community-card-compact-gap` (default `var(--lr-space-xs)`) — `[part='base']` padding/gap
+while `compact`. Otherwise shared tokens.
 
 **Optional peer deps:** none.
 
@@ -44503,7 +44843,9 @@ string; mimeType?: string; name?: string; children?: LyraSourceEntry[] }`; flat
   omitted state and removes the attribute
 
 **Events:** `lr-sources-change` (`detail: { selectedSourceIds }`, the complete updated leaf-id array,
-fired after every toggle including select-all).
+fired after every toggle including select-all. Also fired when a `sources` reassignment prunes a
+previously-selected id that is no longer a valid leaf. Not fired when a consumer sets
+`selectedSourceIds` directly; that assignment is normalized silently).
 
 **Slots:** none.
 
@@ -44657,6 +44999,14 @@ LyraTopic[] }`; a single root sits at the center, multiple roots hang off an imp
   ring); expansion state afterward is component-managed per topic id and survives `topics`
   reassignment
 
+Above 500 currently-visible nodes (per the current expand/collapse state), the SVG and the
+parallel sr-only tree both render a deterministic, connectivity-preserving, subtree-size-weighted
+sample instead of every node: a kept node's parent, if any, is always kept too (no floating nodes
+with a dangling connector or a gap in the `role="tree"` walk), and a larger branch keeps
+proportionally more of its own nodes than a small one, sampled evenly across a wide/flat branch's
+own child list rather than dropping its tail outright. A surviving node keeps the position the
+full layout gave it. A localized "showing N of M" notice appears in `[part="limit"]`.
+
 **Events:** `lr-topic-select` (`detail: { topicId }`, a _leaf_ topic was activated),
 `lr-topic-toggle` (`detail: { topicId, expanded }`, a parent topic was activated, or auto-expanded by
 keyboard descent).
@@ -44664,7 +45014,8 @@ keyboard descent).
 **Slots:** none.
 
 **CSS parts:** `base`, `svg` (the single-tab-stop focus target), `node`, `node-label`, `link`
-(parent-child connector), `focus-ring` (keyboard focus ring), `live-region` (visually hidden
+(parent-child connector), `focus-ring` (keyboard focus ring), `limit` (the "showing N of M"
+render-cap notice, present only above 500 currently-visible nodes), `live-region` (visually hidden
 announcement region), `empty` (shown when `topics` is empty).
 
 **Themeable custom properties:** `--lr-mind-map-ring-gap` (default `6rem`, radius step per depth
@@ -44816,6 +45167,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.
@@ -44840,6 +45193,15 @@ direct light-DOM children of the list (plain composition — no `.items` array p
   header summary, e.g. `"3 sources"` or `"1 source"`; this component never counts or pluralizes on
   its own. Takes precedence over `label` when both are set. If neither is set, the header falls back
   to the localized `sourceListDefaultLabel` string (English default: `"Sources"`).
+- `compact: boolean = false` (reflected) — tighter header and list padding/gap, for a panel
+  rendered repeatedly down a message transcript — same convention as this list's own slotted
+  `lr-source-card` children's `compact`. Purely a density knob: the outer border and surface stay,
+  so pair it with `frame="plain"` to remove card chrome.
+- `frame: LyraFrame = 'card'` (reflected) — container treatment, in the library-wide `frame`
+  vocabulary (`'card' | 'plain'`). `'card'` (the default) keeps the bordered, filled outer
+  container. `'plain'` removes that outer border, background, and corner radius so a list nested
+  inside existing message chrome does not double it. Plain preserves the header/list divider and
+  whichever regular or compact padding applies.
 
 **Getters:** `sourceCount: number` — read-only, live-updated count of the currently-slotted children,
 handy for building a `label-plural` string reactively, e.g. `` list.labelPlural = `${list.sourceCount} sources` ``.
@@ -44859,7 +45221,13 @@ list/listitem semantics return.
 `toggle` (the chevron indicator inside the header), `list` (wrapper around the default slot, `hidden`
 while collapsed).
 
-**Themeable custom properties:** shared tokens only — `--lr-color-border`, `--lr-color-surface`,
+**Themeable custom properties:** `--lr-source-list-compact-header-padding` (default
+`var(--lr-space-2xs) var(--lr-space-s)`) and `--lr-source-list-compact-header-gap` (default
+`var(--lr-space-2xs)`) — `[part="header"]` padding/gap while `compact`; `--lr-source-list-compact-gap`
+(default `var(--lr-space-2xs)`) and `--lr-source-list-compact-list-padding` (default
+`var(--lr-space-s)`) — `[part="list"]` gap/padding while `compact`. All four are inline `var()`
+fallbacks at their point of use, so any can be set on the element or an ancestor. Otherwise shared
+tokens — `--lr-color-border`, `--lr-color-surface`,
 `--lr-color-text`, `--lr-color-brand` / `-brand-quiet`, `--lr-radius`, `--lr-space-xs`/`-s`/
 `-m`, `--lr-transition-fast`, `--lr-focus-ring-*`.
 
@@ -45100,6 +45468,11 @@ rendering, or events. Usable display fields are captured once while emitted sele
 objects retain their original identity. Malformed rows and later duplicate ids are omitted; the
 first valid occurrence wins.
 
+At most 500 citations render as `evidence-item` rows; a `citations` array past that length still
+reports its true count in `evidence-count` but renders a localized `limit` notice after the list
+rather than mounting an unbounded number of rows. The full citation set is still forwarded to the
+composed `lr-claim-evidence` for claim-to-citation lookup, which applies its own render cap.
+
 **Events:** `lr-citation-select` (`detail: CitationSelectEventDetail` from
 `@aceshooting/lyra-ui/ai` = `{ citation: Citation }`) — emitted when an evidence badge is activated.
 The inner `lr-citation-badge`'s generic activation is stopped at this composition boundary; this
@@ -45116,7 +45489,8 @@ row), `warnings` (omitted when there are none), `warnings-heading`, `warnings-co
 its semantics survive list-style resets),
 `evidence-item` (one `<li>` containing a badge + always-visible label/span text),
 `evidence-label` (omitted when `Citation.label` is unset), `evidence-span` (the formatted
-`Citation.span` range, omitted when unset), `claims` (the claim/evidence region), `empty`
+`Citation.span` range, omitted when unset), `limit` (localized notice shown when `citations` exceeds
+the 500-citation render ceiling), `claims` (the claim/evidence region), `empty`
 (shown when `assessment` is `null`).
 
 **Themeable custom properties:** shared tokens only.
@@ -45503,6 +45877,9 @@ duplicates are omitted first-wins before empty state, focus/disclosure state, co
 rendering, or actions. Rows whose `text` is missing, nonstring, blank, or whitespace-only are also
 omitted without hiding later valid memories.
 
+At most 500 items per section render as `item` rows; a section's list past that length renders a
+localized `limit` notice after that section's list rather than mounting an unbounded number of rows.
+
 **Events:**
 
 - `lr-add` (`detail: LyraMemoryAddDetail` = `{ memory: LyraMemoryItem }`) — a pending "promote to
@@ -45524,7 +45901,8 @@ somewhere to land after a confirmation resolves), `item-row`, `item-text`, `conf
 `data-tone`; omitted when `confidence` is unset), `expand-toggle` / `item-body` (both omitted when
 `provenance` is unset; `item-body` is `hidden` while collapsed), `item-actions`, `add-button`,
 `remove-button`, `forget-all-button`, `forget-all-confirm` (the `lr-confirm-bar` that replaces
-`forget-all-button` while the bulk confirmation is pending).
+`forget-all-button` while the bulk confirmation is pending), `limit` (localized notice shown when a
+section's items exceed the 500-item render ceiling).
 
 **Keyboard/focus contract:** activating an action from the keyboard replaces that control with an
 `lr-confirm-bar`, and focus moves into the bar (landing on Deny, the safe action) rather than
@@ -45938,11 +46316,17 @@ Pointer and programmatic focus synchronize the single roving tab stop, and every
 least a 24×24 CSS px pointer target at narrow allocations without enlarging its marker. Optional
 cluster membership is exposed as each option's description and in a visible text legend, so the
 grouping never depends on color alone.
+Above 1,000 points, the plot renders a deterministic, evenly spaced sample of the whole array
+(spanning the full input, not a leading run) instead of every point, keeping DOM node and listener
+count bounded while the sampled points stay representative of the full plotted distribution; a
+localized "showing N of M" notice appears in `[part="limit"]`. `bounds` and the cluster legend
+still derive from the complete `points` array, so a decimated view keeps the same scale and the
+same complete legend as the full plot.
 
 **Events:** `lr-point-select` (`{ point }`), activated by click or Enter/Space.
 
 **CSS parts:** `base`, `plot`, `point`, `legend`, `legend-item`, `legend-swatch`, `legend-label`,
-`empty`.
+`limit` (the "showing N of M" render-cap notice, present only above 1,000 points), `empty`.
 
 **Themeable custom properties:** `--lr-embedding-explorer-selected-stroke` (default
 `var(--lr-color-brand)`) — stroke color of the selected point; `--lr-embedding-explorer-height`
@@ -46019,6 +46403,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
@@ -46035,7 +46422,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`;
@@ -46108,13 +46496,18 @@ Metrics and runs are canonicalized independently by nonblank `id`. Malformed row
 duplicates are omitted first-wins before metric fallback, slice derivation/filtering, cards, charts,
 history, counts, rendering, or actions.
 
+At most 500 of the currently filtered runs render as `run` buttons and feed the trend chart; a
+filtered set past that length renders a localized `limit` notice after the run history rather than
+mounting an unbounded number of rows.
+
 **Events:** `lr-metric-change` (`{ metricId }`), `lr-slice-change` (`{ slice }`), and
 `lr-run-change` (`{ run }`). All are controlled intents; the component does not mutate the
 corresponding selection properties.
 
 **CSS parts:** `base`, `heading`, `slices`, `slice`, `slice-selected`, `metrics`, `metric`,
 `metric-selected`, `metric-category` (the caller-supplied category rendered visibly on each metric),
-`chart`, `runs`, `runs-heading`, `run`, `empty`.
+`chart`, `runs`, `runs-heading`, `run`, `limit` (localized notice shown when the filtered runs
+exceed the 500-run render ceiling), `empty`.
 
 **Themeable custom properties:** `--lr-rag-eval-dashboard-selected-border-color` (default
 `var(--lr-color-brand)`) — border color shared by the controlled active slice and metric.