@aceshooting/lyra-ui 21.0.0 → 21.1.0

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

@@ -9,91 +9,6 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** `chart.js`, `chartjs-plugin-annotation`, `chartjs-plugin-datalabels`, `chartjs-plugin-zoom` — see `llms/peers.md`
-- **Themeable via** 16 parts, 37 custom properties — see this component's own `@csspart`/`@cssprop` list below
-- **Documented with** `lr-line-chart`, `lr-bar-chart`, `lr-doughnut-chart`, `lr-radar-chart`, `lr-polar-area-chart`, `lr-bubble-chart`, `lr-scatter-chart` (same section below)
+- **Themeable via** 16 parts, 37 custom properties — see `lr-line-chart.md`
+- **Documented with** `lr-line-chart`: see [lr-line-chart.md](./lr-line-chart.md).
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
-
----
-
-## Typed subclasses: `lr-line-chart`, `lr-bar-chart`, `lr-pie-chart`, `lr-doughnut-chart`, `lr-radar-chart`, `lr-polar-area-chart`, `lr-bubble-chart`, `lr-scatter-chart`
-
-Each is `LyraChart` with a named default `type` — respectively `line`, `bar`, `pie`, `doughnut`,
-`radar`, `polarArea`, `bubble`, `scatter`. In parity with the mirrored tags, `type` remains writable
-and accepts the full `LyraChartType` vocabulary; the tag name is a convenient default, not a lock.
-
-Everything else is inherited verbatim from `lr-chart`; each name below has the same type, default,
-and behavior there. **See `llms/components/lr-chart.md` for the details, code example, and gotchas
-of every entry in these lists.**
-
-**Properties:** `description`, `grid`, `axes`, `compact`, `indexAxis` (`index-axis`), `label`, `hiddenDatasets`, `legendPosition`
-(`legend-position`), `hiddenDatums`, `legendMode` (`legend-mode`), `legendDisplay` (`legend-display`),
-`max`, `min`, `plugins`, `scaleType` (`scale-type`), `annotations`,
-`stacked`, `stackedAxes`, `withoutAnimation` (`without-animation`),
-`withoutLegend` (`without-legend`), `withoutTooltip` (`without-tooltip`), `xLabel` (`x-label`),
-`yLabel` (`y-label`), plus additive `labels`, `datasets`, `valueFormatter`, `formatter`,
-`tooltipTitleFormatter`, `tooltipFooterFormatter`, `area`, `zoom`,
-`height`, `y2Label` (`y2-label`), `beginAtZero` (`begin-at-zero`), `dataLabels`
-(`data-labels`), `stackTotals` (`stack-totals`), `config`, `showDataTable`
-(`show-data-table`), `dataTableToggle` (`data-table-toggle`), `chartArea` (readonly), and `chart`.
-`type` differs only in its initial value.
-
-**Methods:** `appendData(label, values, maxPoints?)`, `exportData('csv' | 'png')`, `renderChart()`, `resetZoom()`,
-`refreshTheme()`.
-
-**Events:** `lr-zoom` (`detail: { zoomed: boolean }`), `lr-datum-activate`, `lr-point-click` (`detail: { datasetIndex,
-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). `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`.
-
-**CSS parts:** `base`, `plot`, `canvas`, `legend`, `legend-item`, `legend-item-hidden`, `legend-swatch`,
-`reset-zoom-button`, `description`, `notices`, `data-table`, `data-table-toggle`, `data-truncation`, `feature-warning`, `center`, `error` (neutral visible message
-rendered in place of `canvas` when the optional `chart.js` peer dependency fails to load; the
-failure transition is announced through the shared document-level light-DOM assertive sink — see
-`llms/components/lr-chart.md`).
-
-**Themeable custom properties:** `--lr-chart-height`, `--lr-chart-grid-color`,
-`--lr-chart-tick-color`, `--lr-chart-tick-font-size`, `--lr-chart-legend-color`, `--lr-chart-tooltip-bg`,
-`--lr-chart-tooltip-text`, `--lr-chart-legend-item-hover-bg`,
-`--lr-chart-legend-item-active-bg`, `--lr-chart-data-table-button-hover-bg`,
-`--lr-chart-data-table-button-active-bg`, `--lr-chart-data-table-toggle-hover-bg`,
-`--lr-chart-data-table-toggle-active-bg`, `--lr-chart-reset-zoom-button-hover-bg`,
-`--lr-chart-reset-zoom-button-active-bg`, `--lr-chart-canvas-hover-outline-width`, and
-`--lr-chart-canvas-hover-outline-color`, `--lr-chart-pattern-step`, plus `--lr-chart-legend-side-max` — all inherited from `LyraChart`, identical in meaning and default (see
-`lr-chart` above); each of the eight variants below reads the same set, so one rule retunes them
-together. The mirrored hooks are `--border-color-1`,
-`--border-color-2`, `--border-color-3`, `--border-color-4`, `--border-color-5`,
-`--border-color-6`, `--fill-color-1`, `--fill-color-2`, `--fill-color-3`, `--fill-color-4`,
-`--fill-color-5`, `--fill-color-6`, `--border-radius`, `--border-width`, `--grid-border-width`,
-`--grid-color`, `--line-border-width`, and `--point-radius`, also identical to the core chart.
-
-**Optional peer deps:** same as `lr-chart` — `chart.js`, plus `chartjs-plugin-zoom` only once
-`zoom` is set, `chartjs-plugin-datalabels` only once `data-labels`/`stack-totals` is set, and
-`chartjs-plugin-annotation` only once `annotations` contains a usable entry.
-
-```html
-<lr-bar-chart></lr-bar-chart>
-<lr-pie-chart></lr-pie-chart>
-<script>
-  document.querySelector('lr-bar-chart').labels = ['A', 'B'];
-  document.querySelector('lr-bar-chart').datasets = [{ label: 'Count', data: [4, 9] }];
-
-  document.querySelector('lr-pie-chart').labels = ['A', 'B', 'C'];
-  document.querySelector('lr-pie-chart').datasets = [{ label: 'Share', data: [30, 45, 25], color: ['#2563eb', '#16a34a', '#dc2626'] }];
-</script>
-```
-
-**Known gotchas (in addition to the core `lr-chart` list in `llms/components/lr-chart.md`):**
-- Changing `type` after construction may rebuild the underlying Chart.js instance; any active zoom
-  state is reset and announced before the new type renders.
-- `lr-bubble-chart` consumes the exported `LyraChartPoint` shape directly. Set `x`/`y`, optional `r`
-  for bubble radius, and optional `label` for the point-level accessible/event/export label; no
-  runtime cast is needed.
-
----

package/llms/components/lr-polar-area-chart.md

@@ -9,91 +9,6 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** `chart.js`, `chartjs-plugin-annotation`, `chartjs-plugin-datalabels`, `chartjs-plugin-zoom` — see `llms/peers.md`
-- **Themeable via** 16 parts, 37 custom properties — see this component's own `@csspart`/`@cssprop` list below
-- **Documented with** `lr-line-chart`, `lr-bar-chart`, `lr-pie-chart`, `lr-doughnut-chart`, `lr-radar-chart`, `lr-bubble-chart`, `lr-scatter-chart` (same section below)
+- **Themeable via** 16 parts, 37 custom properties — see `lr-line-chart.md`
+- **Documented with** `lr-line-chart`: see [lr-line-chart.md](./lr-line-chart.md).
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
-
----
-
-## Typed subclasses: `lr-line-chart`, `lr-bar-chart`, `lr-pie-chart`, `lr-doughnut-chart`, `lr-radar-chart`, `lr-polar-area-chart`, `lr-bubble-chart`, `lr-scatter-chart`
-
-Each is `LyraChart` with a named default `type` — respectively `line`, `bar`, `pie`, `doughnut`,
-`radar`, `polarArea`, `bubble`, `scatter`. In parity with the mirrored tags, `type` remains writable
-and accepts the full `LyraChartType` vocabulary; the tag name is a convenient default, not a lock.
-
-Everything else is inherited verbatim from `lr-chart`; each name below has the same type, default,
-and behavior there. **See `llms/components/lr-chart.md` for the details, code example, and gotchas
-of every entry in these lists.**
-
-**Properties:** `description`, `grid`, `axes`, `compact`, `indexAxis` (`index-axis`), `label`, `hiddenDatasets`, `legendPosition`
-(`legend-position`), `hiddenDatums`, `legendMode` (`legend-mode`), `legendDisplay` (`legend-display`),
-`max`, `min`, `plugins`, `scaleType` (`scale-type`), `annotations`,
-`stacked`, `stackedAxes`, `withoutAnimation` (`without-animation`),
-`withoutLegend` (`without-legend`), `withoutTooltip` (`without-tooltip`), `xLabel` (`x-label`),
-`yLabel` (`y-label`), plus additive `labels`, `datasets`, `valueFormatter`, `formatter`,
-`tooltipTitleFormatter`, `tooltipFooterFormatter`, `area`, `zoom`,
-`height`, `y2Label` (`y2-label`), `beginAtZero` (`begin-at-zero`), `dataLabels`
-(`data-labels`), `stackTotals` (`stack-totals`), `config`, `showDataTable`
-(`show-data-table`), `dataTableToggle` (`data-table-toggle`), `chartArea` (readonly), and `chart`.
-`type` differs only in its initial value.
-
-**Methods:** `appendData(label, values, maxPoints?)`, `exportData('csv' | 'png')`, `renderChart()`, `resetZoom()`,
-`refreshTheme()`.
-
-**Events:** `lr-zoom` (`detail: { zoomed: boolean }`), `lr-datum-activate`, `lr-point-click` (`detail: { datasetIndex,
-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). `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`.
-
-**CSS parts:** `base`, `plot`, `canvas`, `legend`, `legend-item`, `legend-item-hidden`, `legend-swatch`,
-`reset-zoom-button`, `description`, `notices`, `data-table`, `data-table-toggle`, `data-truncation`, `feature-warning`, `center`, `error` (neutral visible message
-rendered in place of `canvas` when the optional `chart.js` peer dependency fails to load; the
-failure transition is announced through the shared document-level light-DOM assertive sink — see
-`llms/components/lr-chart.md`).
-
-**Themeable custom properties:** `--lr-chart-height`, `--lr-chart-grid-color`,
-`--lr-chart-tick-color`, `--lr-chart-tick-font-size`, `--lr-chart-legend-color`, `--lr-chart-tooltip-bg`,
-`--lr-chart-tooltip-text`, `--lr-chart-legend-item-hover-bg`,
-`--lr-chart-legend-item-active-bg`, `--lr-chart-data-table-button-hover-bg`,
-`--lr-chart-data-table-button-active-bg`, `--lr-chart-data-table-toggle-hover-bg`,
-`--lr-chart-data-table-toggle-active-bg`, `--lr-chart-reset-zoom-button-hover-bg`,
-`--lr-chart-reset-zoom-button-active-bg`, `--lr-chart-canvas-hover-outline-width`, and
-`--lr-chart-canvas-hover-outline-color`, `--lr-chart-pattern-step`, plus `--lr-chart-legend-side-max` — all inherited from `LyraChart`, identical in meaning and default (see
-`lr-chart` above); each of the eight variants below reads the same set, so one rule retunes them
-together. The mirrored hooks are `--border-color-1`,
-`--border-color-2`, `--border-color-3`, `--border-color-4`, `--border-color-5`,
-`--border-color-6`, `--fill-color-1`, `--fill-color-2`, `--fill-color-3`, `--fill-color-4`,
-`--fill-color-5`, `--fill-color-6`, `--border-radius`, `--border-width`, `--grid-border-width`,
-`--grid-color`, `--line-border-width`, and `--point-radius`, also identical to the core chart.
-
-**Optional peer deps:** same as `lr-chart` — `chart.js`, plus `chartjs-plugin-zoom` only once
-`zoom` is set, `chartjs-plugin-datalabels` only once `data-labels`/`stack-totals` is set, and
-`chartjs-plugin-annotation` only once `annotations` contains a usable entry.
-
-```html
-<lr-bar-chart></lr-bar-chart>
-<lr-pie-chart></lr-pie-chart>
-<script>
-  document.querySelector('lr-bar-chart').labels = ['A', 'B'];
-  document.querySelector('lr-bar-chart').datasets = [{ label: 'Count', data: [4, 9] }];
-
-  document.querySelector('lr-pie-chart').labels = ['A', 'B', 'C'];
-  document.querySelector('lr-pie-chart').datasets = [{ label: 'Share', data: [30, 45, 25], color: ['#2563eb', '#16a34a', '#dc2626'] }];
-</script>
-```
-
-**Known gotchas (in addition to the core `lr-chart` list in `llms/components/lr-chart.md`):**
-- Changing `type` after construction may rebuild the underlying Chart.js instance; any active zoom
-  state is reset and announced before the new type renders.
-- `lr-bubble-chart` consumes the exported `LyraChartPoint` shape directly. Set `x`/`y`, optional `r`
-  for bubble radius, and optional `label` for the point-level accessible/event/export label; no
-  runtime cast is needed.
-
----

package/llms/components/lr-popover.md

@@ -76,6 +76,16 @@ If the import fails, leave the native disclosure visible and usable.
   escapes transformed, filtered or contained ancestors by promoting the popup into the browser top
   layer where the native Popover API exists; otherwise, as before, such an ancestor contains and
   clips it (see **Anchored overlays and the top layer**).
+- `topLayer: boolean = false` (attribute `top-layer`, reflected) — always shows the open popup in
+  the browser top layer where the native Popover API exists, so it paints above every page layer
+  whatever the stacking contexts around it: the fix for a popover in a `z-index`ed fixed or sticky
+  header, toolbar or rail that a sibling surface stacked higher would otherwise cover. While set the
+  popup is placed with the `fixed` strategy whatever `positioning-strategy` resolves to (the
+  property still reads back its own value). Anchoring, the arrow, RTL placement, focus, Escape,
+  light dismiss, the hover bridge and the show/hide transition are unchanged, because no DOM node
+  moves; the popup stays promoted through its hide transition and leaves the top layer once it
+  settles closed. Changes apply live while open. Without native Popover API support the popup keeps
+  its ordinary `z-index` stacking. Unset, nothing changes: only a trapping ancestor promotes it.
 - `trigger: string = 'click'` — a _space-separated_ list of `click` (the shipped behaviour),
   `hover`, `focus` and `manual`, spelled exactly the way `<lr-tooltip>`'s `trigger` is, so
   `trigger="hover focus"` means the same thing on both. `LyraPopoverTrigger` is the type of one

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

@@ -81,7 +81,11 @@ textarea, paired with `lr-input` and `lr-change`; `lr-submit` (`{ value }`),
 `lr-audio-request`, `lr-attachment-retry` (`{ attachmentId }`), and cancelable
 `lr-attachment-preview-request` (`{ attachmentId, name, mimeType, src }`). Child events are stopped
 and re-emitted from `lr-prompt-input`; all composed interactions are suppressed while `disabled`,
-including a child event dispatched in the same turn that disables the host.
+including a child event dispatched in the same turn that disables the host. The one deliberate
+exception is the built-in voice picker's preview pair: its cancelable `lr-preview-request`
+(`{ voiceId, previewUrl? }`) and `lr-preview-change` (`{ voiceId }`) reach the host unchanged, so a
+host can play its own TTS preview (call `preventDefault()`) for catalog entries without a
+`previewUrl`, including plain-string catalogs.
 
 **Slots:** `controls`; `start` (attachment-control content before the textarea); `chips`; `end`
 (custom send/stop action); and `footer`. `start` replaces the default attachment trigger and `end`

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

@@ -9,91 +9,6 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** `chart.js`, `chartjs-plugin-annotation`, `chartjs-plugin-datalabels`, `chartjs-plugin-zoom` — see `llms/peers.md`
-- **Themeable via** 16 parts, 37 custom properties — see this component's own `@csspart`/`@cssprop` list below
-- **Documented with** `lr-line-chart`, `lr-bar-chart`, `lr-pie-chart`, `lr-doughnut-chart`, `lr-polar-area-chart`, `lr-bubble-chart`, `lr-scatter-chart` (same section below)
+- **Themeable via** 16 parts, 37 custom properties — see `lr-line-chart.md`
+- **Documented with** `lr-line-chart`: see [lr-line-chart.md](./lr-line-chart.md).
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
-
----
-
-## Typed subclasses: `lr-line-chart`, `lr-bar-chart`, `lr-pie-chart`, `lr-doughnut-chart`, `lr-radar-chart`, `lr-polar-area-chart`, `lr-bubble-chart`, `lr-scatter-chart`
-
-Each is `LyraChart` with a named default `type` — respectively `line`, `bar`, `pie`, `doughnut`,
-`radar`, `polarArea`, `bubble`, `scatter`. In parity with the mirrored tags, `type` remains writable
-and accepts the full `LyraChartType` vocabulary; the tag name is a convenient default, not a lock.
-
-Everything else is inherited verbatim from `lr-chart`; each name below has the same type, default,
-and behavior there. **See `llms/components/lr-chart.md` for the details, code example, and gotchas
-of every entry in these lists.**
-
-**Properties:** `description`, `grid`, `axes`, `compact`, `indexAxis` (`index-axis`), `label`, `hiddenDatasets`, `legendPosition`
-(`legend-position`), `hiddenDatums`, `legendMode` (`legend-mode`), `legendDisplay` (`legend-display`),
-`max`, `min`, `plugins`, `scaleType` (`scale-type`), `annotations`,
-`stacked`, `stackedAxes`, `withoutAnimation` (`without-animation`),
-`withoutLegend` (`without-legend`), `withoutTooltip` (`without-tooltip`), `xLabel` (`x-label`),
-`yLabel` (`y-label`), plus additive `labels`, `datasets`, `valueFormatter`, `formatter`,
-`tooltipTitleFormatter`, `tooltipFooterFormatter`, `area`, `zoom`,
-`height`, `y2Label` (`y2-label`), `beginAtZero` (`begin-at-zero`), `dataLabels`
-(`data-labels`), `stackTotals` (`stack-totals`), `config`, `showDataTable`
-(`show-data-table`), `dataTableToggle` (`data-table-toggle`), `chartArea` (readonly), and `chart`.
-`type` differs only in its initial value.
-
-**Methods:** `appendData(label, values, maxPoints?)`, `exportData('csv' | 'png')`, `renderChart()`, `resetZoom()`,
-`refreshTheme()`.
-
-**Events:** `lr-zoom` (`detail: { zoomed: boolean }`), `lr-datum-activate`, `lr-point-click` (`detail: { datasetIndex,
-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). `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`.
-
-**CSS parts:** `base`, `plot`, `canvas`, `legend`, `legend-item`, `legend-item-hidden`, `legend-swatch`,
-`reset-zoom-button`, `description`, `notices`, `data-table`, `data-table-toggle`, `data-truncation`, `feature-warning`, `center`, `error` (neutral visible message
-rendered in place of `canvas` when the optional `chart.js` peer dependency fails to load; the
-failure transition is announced through the shared document-level light-DOM assertive sink — see
-`llms/components/lr-chart.md`).
-
-**Themeable custom properties:** `--lr-chart-height`, `--lr-chart-grid-color`,
-`--lr-chart-tick-color`, `--lr-chart-tick-font-size`, `--lr-chart-legend-color`, `--lr-chart-tooltip-bg`,
-`--lr-chart-tooltip-text`, `--lr-chart-legend-item-hover-bg`,
-`--lr-chart-legend-item-active-bg`, `--lr-chart-data-table-button-hover-bg`,
-`--lr-chart-data-table-button-active-bg`, `--lr-chart-data-table-toggle-hover-bg`,
-`--lr-chart-data-table-toggle-active-bg`, `--lr-chart-reset-zoom-button-hover-bg`,
-`--lr-chart-reset-zoom-button-active-bg`, `--lr-chart-canvas-hover-outline-width`, and
-`--lr-chart-canvas-hover-outline-color`, `--lr-chart-pattern-step`, plus `--lr-chart-legend-side-max` — all inherited from `LyraChart`, identical in meaning and default (see
-`lr-chart` above); each of the eight variants below reads the same set, so one rule retunes them
-together. The mirrored hooks are `--border-color-1`,
-`--border-color-2`, `--border-color-3`, `--border-color-4`, `--border-color-5`,
-`--border-color-6`, `--fill-color-1`, `--fill-color-2`, `--fill-color-3`, `--fill-color-4`,
-`--fill-color-5`, `--fill-color-6`, `--border-radius`, `--border-width`, `--grid-border-width`,
-`--grid-color`, `--line-border-width`, and `--point-radius`, also identical to the core chart.
-
-**Optional peer deps:** same as `lr-chart` — `chart.js`, plus `chartjs-plugin-zoom` only once
-`zoom` is set, `chartjs-plugin-datalabels` only once `data-labels`/`stack-totals` is set, and
-`chartjs-plugin-annotation` only once `annotations` contains a usable entry.
-
-```html
-<lr-bar-chart></lr-bar-chart>
-<lr-pie-chart></lr-pie-chart>
-<script>
-  document.querySelector('lr-bar-chart').labels = ['A', 'B'];
-  document.querySelector('lr-bar-chart').datasets = [{ label: 'Count', data: [4, 9] }];
-
-  document.querySelector('lr-pie-chart').labels = ['A', 'B', 'C'];
-  document.querySelector('lr-pie-chart').datasets = [{ label: 'Share', data: [30, 45, 25], color: ['#2563eb', '#16a34a', '#dc2626'] }];
-</script>
-```
-
-**Known gotchas (in addition to the core `lr-chart` list in `llms/components/lr-chart.md`):**
-- Changing `type` after construction may rebuild the underlying Chart.js instance; any active zoom
-  state is reset and announced before the new type renders.
-- `lr-bubble-chart` consumes the exported `LyraChartPoint` shape directly. Set `x`/`y`, optional `r`
-  for bubble radius, and optional `label` for the point-level accessible/event/export label; no
-  runtime cast is needed.
-
----

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

@@ -9,161 +9,6 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 6 parts, 5 custom properties — see this component's own `@csspart`/`@cssprop` list below
-- **Documented with** `lr-reorder-list` (same section below)
+- **Themeable via** 6 parts, 5 custom properties — see `lr-reorder-list.md`
+- **Documented with** `lr-reorder-list`: see [lr-reorder-list.md](./lr-reorder-list.md).
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
-
----
-
-## `lr-reorder-list` / `lr-reorder-item`
-
-A generic flat-list reorder primitive: per-row move-up/move-down buttons (always available), plus
-Ctrl/Cmd+ArrowUp/ArrowDown from focus anywhere inside a row — the same modifier convention
-`<lr-tree>`'s `reorderable` and `<lr-dashboard-grid>`'s `cells-draggable` already establish. By
-default this list physically moves its own slotted `<lr-reorder-item>` light-DOM nodes itself
-(there is no `data` array prop to reconcile against), and emits `lr-reorder` with the full new
-order so the host can persist it without hand-rolling its own splice/resort logic. Setting
-`controlled` opts into `<lr-tree>`'s controlled `reorderable` contract instead: the list stops
-moving anything itself, and waits for the host to reorder its own backing data and re-render the
-slotted items to match — reconciled by each item's `value` rather than by element reference, so a
-non-keyed host re-render that recreates the moved row (or merely rewrites `value` on the elements
-already at each position) still completes the move once the resulting order matches. `lr-reorder`
-is cancelable — a listener calling `preventDefault()` holds the move open (mirroring
-`lr-confirm-bar`'s cancelable approve/deny pattern) until the host calls
-`finalizePendingMove()`/`revertPendingMove()`; `controlled` changes what "applying" the move
-means (host re-render instead of a physical DOM move) but not this cancelable contract.
-
-Direct item `value` property or attribute edits refresh the owning list's valid identities and
-movement boundaries. Correcting a missing or duplicate identity re-enables the corresponding
-controls; making it invalid disables them. Identity edits do not emit a reorder event. Removing the
-value attribute from a standalone item renders it as absent while preserving `null` readback; an
-explicit empty string remains supplied and later valid values recover.
-
-### `lr-reorder-list`
-
-**Properties:**
-
-- `label: string = ''` — accessible-name fallback for the internal `role="list"`. A present host
-  `aria-label` always wins over `label`, including when the host value is explicitly empty.
-- `disabled: boolean = false` (reflected) — disables every item's move buttons and the Ctrl/Cmd+
-  Arrow shortcut, without mutating any item's own `disabled` attribute.
-- `controlled: boolean = false` (reflected) — opts into the controlled mode described above:
-  an accepted move waits for a matching host re-render (reconciled by `value`) instead of moving
-  the DOM itself. Every move action stays disabled and `aria-busy="true"`/`:state(busy)` apply
-  list-wide for the whole wait, the same as a `preventDefault()`-held move. A host re-render that
-  never reaches the exact emitted `order` leaves the move pending indefinitely; one that drops the
-  moved `value` entirely (removes or renames that row) cancels it silently, with no announcement.
-  Toggling this off while a reconciliation is pending drops it rather than leaving the list stuck
-  busy.
-
-**Events:** `lr-reorder`
-(`detail: LyraReorderDetail { readonly order: readonly string[], readonly fromIndex: number,
-readonly toIndex: number }`, cancelable) — fired before a move is applied; `order` is an immutable
-snapshot of every valid item's stable `value` in the order the move WOULD produce. Uncanceled, the
-move applies synchronously only if the exact mover, target, membership, order, identities, and
-availability remain valid after dispatch — or, while `controlled`, starts waiting for the host's
-own re-render to reach that `order` instead. `preventDefault()` holds the move instead: the
-internal list exposes `aria-busy="true"`, every move action is disabled, the affected item exposes
-`:state(pending)`, and no other move can start until the host resolves it — see **Methods** below.
-Synchronous finalize/revert calls from the canceling listener are supported.
-
-**Methods:** `finalizePendingMove()` — applies a move held via `preventDefault()` (or, while
-`controlled`, starts waiting for the host's own re-render instead of moving the DOM itself).
-`revertPendingMove(options?: { silent?: boolean })` — discards a held move, restoring the prior
-order; pass `{ silent: true }` to suppress the built-in `reorderMoveCancelled` announcement, e.g.
-when a host is deferring the decision to a flow of its own (a confirmation dialog, say) that will
-communicate the outcome itself. Both methods no-op when nothing is pending.
-
-**Slots:** default — `<lr-reorder-item>` elements.
-
-**CSS parts:** `base` — the internal `role="list"` wrapper.
-
-**Themeable custom properties:** `--lr-reorder-list-gap` (default `var(--lr-space-2xs)`) — gap
-between rows.
-
-```html
-<lr-reorder-list label="Form fields">
-  <lr-reorder-item value="name">Name</lr-reorder-item>
-  <lr-reorder-item value="email">Email</lr-reorder-item>
-  <lr-reorder-item value="phone">Phone</lr-reorder-item>
-</lr-reorder-list>
-<script type="module">
-  document
-    .querySelector("lr-reorder-list")
-    .addEventListener("lr-reorder", (e) => console.log(e.detail.order));
-</script>
-```
-
-**Known gotchas:**
-
-- Boundary-disabled state (`atStart`/`atEnd`), `listDisabled`, and `pending` are readonly effective
-  state computed by the owning list and exposed through item custom states.
-- Every item requires a unique, nonempty stable `value`. Missing, whitespace-only, and later
-  duplicate identities remain visible but their move actions are unavailable until corrected.
-- Ctrl/Cmd+Arrow is consumed only for a valid owned move. A boundary/no-op gesture or one from a
-  nested input, select, link, button, editable region, or custom control retains its native action.
-- No pointer drag-and-drop; move-up/move-down buttons and the keyboard shortcut only.
-- `controlled` reconciliation is keyed by `value`, never by element reference: a host re-render
-  that recreates the moved row as a brand-new element, or one that leaves every node in place and
-  just rewrites `value` at each position (the common outcome of a non-keyed `Array.map()` into the
-  default slot), both complete the move once the resulting order matches.
-
----
-
-### `lr-reorder-item`
-
-**Properties:**
-
-- `value: string = ''` — required unique, nonempty stable identifier included in the parent's
-  `lr-reorder` order array.
-- `accessibleLabel?: string` (attribute `accessible-label`) — explicit row identity appended to
-  each repeated move action's accessible name; otherwise the item derives a bounded accessible
-  text projection from its row content.
-- `disabled: boolean = false` (reflected) — disables this row's own move buttons only; does not
-  hide its slotted content.
-- `atStart: boolean`, `atEnd: boolean`, `listDisabled: boolean`, `pending: boolean` (readonly) —
-  effective owner state. Corresponding custom states include `:state(at-start)`, `:state(at-end)`,
-  `:state(list-disabled)`, `:state(pending)`, and `:state(busy)`.
-
-**Events:** `lr-move-request` (`detail: { direction: 'up' | 'down' }` — a move button was activated
-while not disabled; handled by the parent `<lr-reorder-list>`, which performs the actual move)
-
-**Methods:** `focusMoveButton(direction: 'up' | 'down'): boolean` — moves focus to the requested
-move control and returns whether it did; a no-op returning `false` when that control is disabled
-for any reason (this item's own `disabled`, the owning list's `listDisabled`, a move held or a
-controlled reconciliation pending anywhere in the list, an invalid identity, or that direction
-already being this item's boundary). The owning `<lr-reorder-list>` uses it for its own post-move
-focus restore, including onto a freshly recreated element instance while `controlled`; a host can
-call it the same way.
-
-**Slots:** default — arbitrary row content.
-
-**CSS parts:** `base` (row wrapper), `move-up-button`, `move-down-button`,
-`move-up-button__control` / `move-down-button__control` (each move control's own native `<button>` —
-as of 16.0.0 the move controls are composed `<lr-icon-button>`s: the old part names keep placement,
-rotation and activation, while background, radius, hover/press mixes, focus ring and hit-area floor
-come from `--lr-icon-button-*`, and the component's own `--lr-reorder-item-move-button-*` hooks still
-win over those defaults), `content` (default-slot wrapper).
-
-**Border reaches the composed move controls the same way background/color/radius do.** This
-component paints no resting border on either move control, so it relays no
-`--_lr-icon-button-border-default` into their private fallback tier — but that absence is not a
-gap. The public `--lr-icon-button-border` (and its `-hover`/`-active` variants) is the FIRST arm
-of the token chain, resolved by ordinary custom-property inheritance regardless of whether this
-component relays a default for that same property, so setting it on either move control or an
-ancestor reaches it exactly as the background/color/radius tokens do. A component with no resting
-border simply has no default to relay, which is different from border theming being broken. Size
-remains the one exception that does not cross this way: use `--lr-theme-icon-button-size`, never
-`--lr-icon-button-size` — every `LyraElement` re-declares the latter on its own `:host`, so it
-never reaches a composed child (see `llms/tokens.md`).
-
-**Themeable custom properties:** `--lr-reorder-item-gap` (default `var(--lr-space-xs)`) — gap
-between the move buttons and the row content. The move-button interaction paints are independent,
-inherited inline fallbacks: `--lr-reorder-item-move-button-hover-bg` (default
-`var(--lr-color-brand-quiet)`), `--lr-reorder-item-move-button-hover-color` (default
-`var(--lr-color-brand)`), `--lr-reorder-item-move-button-active-bg` (default `color-mix(in oklab,
-var(--lr-color-brand-quiet), var(--lr-color-mix-partner) var(--lr-color-mix-active))`), and
-`--lr-reorder-item-move-button-active-color` (default `var(--lr-color-brand)`). Set them on an item
-or any ancestor to retheme only the hover or pressed move affordance.
-
----

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

@@ -9,121 +9,6 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 3 parts, 0 custom properties — see this component's own `@csspart`/`@cssprop` list below
-- **Documented with** `lr-result-card` (same section below)
+- **Themeable via** 3 parts, 0 custom properties — see `lr-result-card.md`
+- **Documented with** `lr-result-card`: see [lr-result-card.md](./lr-result-card.md).
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
-
----
-
-## `lr-result-card` / `lr-result-field`
-
-A small, tightly-coupled pair giving any custom `lr-tool-result-view` renderer (registered via
-`registerToolRenderer()` in `../tool-result-view/registry.js`) a consistent "small bordered card +
-label/value row" visual language, without each one hand-rolling its own box. Neither component has
-any code dependency on the tool-result-view registry itself — they're generically usable anywhere a
-small card/field shell is useful.
-
-Removing `heading` or a result field `label` hides that text while preserving the card actions and
-field value.
-
-### `lr-result-card`
-
-A small bordered card shell. Purely visual, with no state of its own beyond slot-presence tracking.
-
-**Properties:**
-
-- `heading: string = ''` — small heading for the card. Leave unset for an untitled card (e.g. a bare
-  block of `lr-result-field` rows with no natural heading).
-- `compact: boolean = false` (reflected) — tighter header/body padding for dense contexts (a card
-  rendered as a row in a transcript or result list), same convention as `<lr-agent-run>`'s own
-  `compact`. Purely a density knob: the border and background stay, so use `frame="plain"`
-  instead to drop the chrome entirely. When both are set, plain leaves compact padding and gaps
-  intact.
-- `frame: LyraFrame = 'card'` (reflected) — container treatment, in the library-wide `frame`
-  vocabulary (`'card' | 'plain'`), the same property `<lr-agent-run>`/`<lr-card>` carry. `'card'`
-  (the default) keeps the bordered, filled box. `'plain'` removes the border, background, and corner
-  radius, so a card nested inside a host frame that already draws a border (e.g.
-  `<lr-tool-result-view>`'s own chrome) doesn't double it. Plain controls only the chrome; compact
-  padding and gaps still apply when both are set. The exported alias `ResultCardAppearance` is
-  retained as a name for the same union.
-- `withActions: boolean = false` (attribute `with-actions`, reflected) — explicit first-render
-  presence hint for the `actions` slot. Client-only markup normally does not need it because the
-  component detects assigned actions during upgrade; set it before both server and browser first
-  render when an actions-only header must be present in the no-JavaScript response and reused by
-  hydration.
-
-**Events:** none.
-
-**Slots:** default (the card body — typically one or more `lr-result-field` rows, though any
-content is accepted), `actions` (small header controls, e.g. a copy button, rendered alongside the
-heading).
-
-**CSS parts:** `base` (outer bordered container), `header` (present in the DOM at all times so a
-later `slotchange` on `actions` is still observed, but `hidden` whenever there's no `heading` and no
-`actions` content), `heading` (truncates with an ellipsis when it overflows; carries its own native
-`title` attribute — the full string — so hovering the truncated text reveals it via the browser's
-default tooltip, scoped to just this element rather than the whole card), `actions` (`hidden`
-whenever the slot has no assigned content), `body`.
-
-**Themeable custom properties:** `--lr-result-card-compact-header-padding` (default
-`var(--lr-space-xs)`) — `[part="header"]` block/inline padding while `compact`;
-`--lr-result-card-compact-header-gap` (default `var(--lr-space-xs)`) — gap between
-`[part="header"]`'s heading and actions while `compact`, one step tighter than the uncompacted
-`--lr-space-s`; `--lr-result-card-compact-body-padding` (default `var(--lr-space-xs)`) —
-`[part="body"]` padding while `compact`; `--lr-result-card-compact-body-gap` (default
-`var(--lr-space-2xs)`) — gap between `[part="body"]`'s children while `compact`, one step tighter
-than the uncompacted `--lr-space-xs`. The two gap knobs mean `compact` now tightens interior spacing,
-not only the padding box — a compact card no longer keeps full-size gaps inside a shrunken frame.
-`--lr-result-card-background` (default `var(--lr-color-surface)`), `--lr-result-card-border-color`
-(default `var(--lr-color-border-subtle)`) and `--lr-result-card-radius` (default `var(--lr-radius)`) retune
-the card chrome without a `::part(base)` override. The border-color hook also colors
-`[part="header"]`'s divider, so a retuned card doesn't strand a mismatched interior rule;
-`frame="plain"` still drops the outer chrome and that divider.
-Plus shared tokens — `--lr-space-2xs`/`-xs`/`-s`, `--lr-color-border-subtle`,
-`--lr-color-surface`/`-text`, `--lr-radius`.
-
-### `lr-result-field`
-
-A single label/value row — e.g. "Status: 200 OK" or "Duration: 340ms" — rendered as a dense
-"label: value" line by default, matching the compact, small-card presentation this pair exists for.
-
-**Properties:**
-
-- `label: string = ''` — the field name, e.g. "Status". Leave unset to render a value with no label.
-- `value: string = ''` — plain-text value, e.g. "200 OK". Ignored once the default slot carries real
-  content.
-
-**Events:** none.
-
-**Slots:** default — rich value content (e.g. a `lr-chip` status badge, or a plain text override),
-taking precedence over `value` whenever it has any assigned content. "Real content" means any
-assigned _element_ (even one with no text of its own, like an attribute-driven status badge) or any
-non-whitespace text node — both a rich slotted badge and a plain-text override are caught.
-
-**CSS parts:** `base` (row container), `label` (including its trailing colon), `value` (wrapper
-around either the slotted content or the plain `value` text).
-
-**Themeable custom properties:** shared tokens only — `--lr-space-xs`, `--lr-color-text`/
-`-text-quiet`, `--lr-font`.
-
-**Optional peer deps:** none (either component).
-
-```html
-<lr-result-card heading="Weather">
-  <lr-result-field label="Status" value="200 OK"></lr-result-field>
-  <lr-result-field label="Duration" value="340ms"></lr-result-field>
-  <lr-result-field label="Provider">
-    <lr-chip variant="success">OpenWeather</lr-chip>
-  </lr-result-field>
-</lr-result-card>
-```
-
-**Known gotchas:**
-
-- `HTMLElement.textContent` read on a shadow-DOM wrapper containing a `<slot>` does NOT include the
-  slot's assigned/projected light-DOM content — only literal fallback children of the `<slot>` tag
-  itself (there are none here). Reading `[part="value"]`'s own `.textContent` yields an empty value
-  even when slotted content is rendering correctly; use the slot's
-  `assignedNodes()`/`assignedElements()` instead.
-
----

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

@@ -103,7 +103,9 @@ region. Initial empty content, loading intermediates, and reconnects are not rep
 - `lr-select` (`detail: RetrievalResultsSelectDetail` = `{ chunkIds: string[]; chunks: RetrievalChunk[] }`)
   — the _complete_ updated selection, both as ids and as exactly one canonical record per id, so a
   host needn't re-look-up ids against its own copy on every toggle. This derived detail is always
-  canonicalized nonblank/first-wins regardless of the legacy `dedupe` switch.
+  canonicalized nonblank/first-wins regardless of the legacy `dedupe` switch. It is the only
+  host-level report of a row toggle: the row checkbox's `lr-checkbox-toggle-request`, native
+  `input`/`change`, and `lr-input`/`lr-change` stay inside the component.
 - `lr-load-more` (`detail: null`) — from the virtual list's scroll-near-bottom detection while
   virtualized, or the `[part="load-more"]` button otherwise. Only fires while `hasMore` is true and
   `loading` is false.

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

@@ -79,8 +79,9 @@ errors and own/fieldset validation barring), `lr-submit` (`detail: { value, item
 (`detail: { itemId }`, `skippable` only). `lr-invalid` (no detail) is the one bubbling/composed,
 cancelable alias emitted when the complete rubric fails a native validity check; preventing it also
 suppresses the native event's default validation UI.
-Native and prefixed input/change events from the composed child controls are contained; consumers
-above the rubric receive only the rubric-owned aggregate event shape.
+Native and prefixed input/change events from the composed child controls are contained, as is a
+multiple-category checkbox group's `lr-checkbox-group-toggle-request` proposal; consumers above the
+rubric receive only the rubric-owned aggregate event shape.
 
 **Methods:** `getForm()` returns the owning form. `setCustomValidity(message)` sets or clears a
 form-level error no per-key rule can