@aceshooting/lyra-ui 14.3.2 → 15.0.1

package/llms/components/lr-alert.md

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 5 parts, 0 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 5 parts, 2 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -76,8 +76,16 @@ once. Toast-owned work instead settles and is discarded when its region disconne
 subtree remains visible but is inert and aria-hidden.
 
 **CSS parts:** `base`, `icon`, `message`, and `close-button` / `close-button__base` on the same
-native close button. The pinned surface exposes no component CSS custom properties, custom states,
-form association, native-event relays, or delegated native methods.
+native close button. The pinned surface exposes no custom states, form association, native-event
+relays, or delegated native methods.
+
+**Themeable custom properties:** the close button's two state hooks are
+`--lr-alert-close-hover-bg` (its `:hover` surface; default `color-mix(in oklab, transparent,
+var(--lr-color-mix-partner) var(--lr-color-mix-hover))`) and `--lr-alert-close-active-bg` (its
+`:active` surface, scoped independently from the hover property; default `color-mix(in oklab,
+transparent, var(--lr-color-mix-partner) var(--lr-color-mix-active))`). Each is an inline fallback
+at the relevant state, so setting one on the alert or an ancestor rethemes only that close-button
+state.
 
 By default the light-DOM `<lr-alert>` host owns `role="alert"`, so initially-open/static alerts and
 alerts shown later expose one assertive, content-derived semantic surface without duplicating it in

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

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** `@sgratzl/chartjs-chart-boxplot`, `chart.js` — see `llms/peers.md`
-- **Themeable via** 12 parts, 14 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 12 parts, 32 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -117,7 +117,23 @@ bounded-alternative sampling notice)
 concrete semantic fallbacks rather than retaining a prior canvas paint), but declared in its own stylesheet, not a
 re-export: `lr-box-plot` has no `zoom`, so no `reset-zoom-button` chrome exists here. A `BoxPlotSeries`
 that sets no `color` is assigned an entry from the same `--lr-color-chart-1..8` ramp `lr-chart` uses,
-so `--lr-theme-color-chart-*` retheming reaches box plots too. `--lr-chart-pattern-step`
+so `--lr-theme-color-chart-*` retheming reaches box plots too. That resolved color then layers two
+further per-series override tokens for the canvas paint, each wrapping modulo 8 like the underlying
+ramp and mirroring `lr-chart`'s own `--border-color-N`/`--fill-color-N` palette-override mechanism
+under a box-plot-namespaced name, since box-plot has no raw `config` passthrough to piggyback on:
+`--lr-box-plot-border-color-1` through `--lr-box-plot-border-color-8` (defaulting respectively to
+`--lr-color-chart-1` through `--lr-color-chart-8`) set the box-outline stroke color, and
+`--lr-box-plot-fill-color-1` through `--lr-box-plot-fill-color-8` (the same eight defaults) set the
+box fill and its legend swatch. In full, the stroke tokens are `--lr-box-plot-border-color-1`,
+`--lr-box-plot-border-color-2`, `--lr-box-plot-border-color-3`, `--lr-box-plot-border-color-4`,
+`--lr-box-plot-border-color-5`, `--lr-box-plot-border-color-6`, `--lr-box-plot-border-color-7` and
+`--lr-box-plot-border-color-8`; the fill tokens are `--lr-box-plot-fill-color-1`,
+`--lr-box-plot-fill-color-2`, `--lr-box-plot-fill-color-3`, `--lr-box-plot-fill-color-4`,
+`--lr-box-plot-fill-color-5`, `--lr-box-plot-fill-color-6`, `--lr-box-plot-fill-color-7` and
+`--lr-box-plot-fill-color-8`. `--lr-box-plot-border-width` (default `var(--lr-border-width-thin)`)
+sets the canvas box-outline stroke width in pixels — the same override mechanism as `lr-chart`'s
+`--border-width`. `--lr-box-plot-item-radius` (default `0`) sets the radius, in pixels, of the
+individual raw-sample dots drawn alongside each box; `0` disables them. `--lr-chart-pattern-step`
 (default `var(--lr-space-2xs)`) sizes the forced-colors legend texture and
 `--lr-chart-canvas-hover-outline-width` (default `var(--lr-border-width-thin)`) sizes the `canvas`
 hover outline; `--lr-chart-canvas-hover-outline-color` (default `var(--lr-chart-grid-color)`) sets
@@ -148,8 +164,9 @@ loads are memoized per page.
 ```
 
 **Known gotchas:**
-- no raw `config` passthrough — limited to the properties above; can't reach the underlying
-  controller's own options (`itemRadius`, `outlierRadius`, `coef`).
+- no raw `config` passthrough — limited to the properties above, plus the `--lr-box-plot-border-width`
+  and `--lr-box-plot-item-radius` CSS hooks; the underlying controller's other options
+  (`outlierRadius`, `coef`) remain unreachable.
 - Chart.js receives `effectiveLocale`; generated numeric summaries use it, the y axis moves to
   logical start in RTL, and live ancestor `lang`/`dir` changes redraw the already-mounted canvas
   without requiring another box property write. Canvas tooltip/axis colors are token-driven, and

package/llms/components/lr-chart.md

@@ -93,7 +93,8 @@ structured points retain their y-value formatting.
 - `datasets: readonly LyraChartSeries[] = []` (attribute: false) — `LyraChartSeries { readonly
   label: string; readonly data?: readonly (number|null)[]; readonly points?: readonly
   LyraChartPoint[]; readonly color?: string|readonly string[]; ... }`. The deprecated `Series` and
-  `ChartPoint` names remain aliases for migration. `LyraChartPoint { readonly x: number; readonly
+  `ChartPoint` names were removed in 9.0.0 — import `LyraChartSeries`/`LyraChartPoint` instead.
+  `LyraChartPoint { readonly x: number; readonly
   y: number; readonly r?: number; readonly label?: string }`: `r` is the bubble
   radius, and the optional per-point `label` is retained by events, CSV export, keyboard
   announcements, generated summaries, and the accessible table. Point wording is localized as
@@ -127,9 +128,11 @@ structured points retain their y-value formatting.
   would clip. Its pressed state follows `hiddenDatasets` whenever that controlled snapshot is
   defined, otherwise the effective dataset's declarative `hidden` value before Chart.js is ready
   and across chart type/plugin rebuilds.
-- `legendMode: LyraChartLegendMode = 'dataset'` (attribute `legend-mode`) — `dataset` preserves
-  dataset toggles. `datum` shows one category toggle per slice in pie, doughnut and polar-area
-  charts; other types retain dataset legends. Category names use source labels with localized
+- `legendMode: LyraChartLegendMode = 'auto'` (attribute `legend-mode`) — `auto` resolves to `datum`
+  on pie, doughnut and polar-area charts and to `dataset` everywhere else, so a single-dataset slice
+  chart labels every slice rather than emitting one aggregate row that identifies only the first
+  colour. `dataset` forces dataset toggles even on a slice chart. `datum` shows one category toggle
+  per slice in pie, doughnut and polar-area charts; other types retain dataset legends. Category names use source labels with localized
   numbered fallbacks. Colors and values come from the first dataset. With multiple datasets/rings,
   a category toggle hides that source index in every ring, matching Chart.js category visibility.
 - `hiddenDatums: readonly number[] = []` (attribute: false) — clone-owned hidden source category
@@ -304,6 +307,12 @@ token layer yet, the helper reads the `--lr-theme-color-chart-N` inputs directly
 a fresh eight-color array each call (safe to mutate) and let chart-adjacent UI, KPI tiles, or the
 `Series` array itself come from one source of truth.
 
+The same module also exports `ChartThemeColors`, the resolved chrome colours a chart paints around
+its series. Every field is an already-resolved CSS colour string, because canvas silently ignores a
+raw `var(--lr-…)` string and would paint nothing; `<lr-box-plot>` consumes the same shape, so a
+consumer drawing its own canvas overlay beside a chart can match the grid, tick, legend and tooltip
+chrome exactly rather than re-deriving it.
+
 Import the standalone form from `.../chart/chart-colors.js`, not from `.../chart/chart.js`: the
 latter is `<lr-chart>`'s registration entry, so it defines the element (and pulls in `<lr-skeleton>`)
 as a side effect. `chart-colors.js` is side-effect-free and carries nothing but the palette helpers,

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

@@ -79,10 +79,11 @@ highlighted markup.
   to the default dynamic-import path unchanged. For a TypeScript annotation, use
   `import type { ShikiLanguageInput } from '@aceshooting/lyra-ui/components/conversation/code-block/code-block.js'`;
   the type-only granular import emits no registration side effect.
-  `refreshTheme(): void` re-reads the resolved theme for syntax highlighting.
-  **Methods:** `scrollToAnchor(target)` — resolves a `line-range` anchor (or a `highlights` id string
-  resolving to one) by scrolling its start line into view within `[part="body"]`; resolves `false`
-  when the anchor isn't a `line-range`, the id isn't found, or the start line is out of bounds.
+
+**Methods:** `scrollToAnchor(target)` — resolves a `line-range` anchor (or a `highlights` id string
+resolving to one) by scrolling its start line into view within `[part="body"]`; resolves `false`
+when the anchor isn't a `line-range`, the id isn't found, or the start line is out of bounds.
+`refreshTheme(): void` re-reads the resolved theme for syntax highlighting.
 
 **Events:** `lr-copy` (frozen `detail: { ok: true, text }` — fires only after the raw `code` value
 was written successfully), `lr-error` (`detail: null` — generic notification when clipboard writing

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

@@ -94,6 +94,12 @@ ARIA values as page-local positions rather than as the dataset-wide total.
   The mirrored `selectedKeys` spelling remains a compatibility alias for this same state.
 - `selectedRows: readonly Row[]` (writable, JS-only) — assigning rows that belong to the current source
   maps them to `selectedRowKeys`; detached rows are ignored and single-selection mode keeps the first.
+- `selectionMode: 'none' | 'single' | 'multiple'` (`selection-mode`) — alias of `selectable` using
+  `<lr-table>`'s `selectionMode`/`selection-mode` spelling for the same row-selection concept, so a
+  consumer migrating between the two grid components doesn't need to remember two names.
+  `selectable` remains canonical (mirrored from `wa-data-grid`); this alias reads and writes
+  `selectable` directly, so there is no separate value to fall out of sync, and the bare `''`
+  shorthand for `selectable`'s own `multiple` normalizes to `'multiple'` when read back through it.
 - `server: boolean = false` (`server`, reflected).
 - `size: 'xs' | 's' | 'm' | 'l' | 'xl' | 'small' | 'medium' | 'large' = 'm'` (`size`, reflected).
 - `sort: readonly Array<{ readonly id: string; readonly desc: boolean }> = []` (JS-only).
@@ -106,11 +112,15 @@ ARIA values as page-local positions rather than as the dataset-wide total.
 - `withSearch: boolean = false` (`with-search`, reflected).
 
 `DataGridColumn<Row>` accepts `id`, dot-path `field`, `label`, `align`, numeric `width` /
-`minWidth` / `maxWidth`, `flex`, `formatter(value, row)`, computed `value(row)`, `sortable`,
-`sortFn`, `comparator`, `sortDescFirst`, `sortUndefined`, `searchable`, `filterable`, `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.
+`minWidth` / `maxWidth`, `flex`, `formatter(value, row)`, `cellTitle(row)`, computed `value(row)`,
+`sortable`, `sortFn`, `comparator`, `sortDescFirst`, `sortUndefined`, `searchable`, `filterable`,
+`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.
+`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`
+attribute entirely rather than rendering `title=""`, which would suppress an ancestor's own tooltip.
 
 Built-in sort algorithms are `alphanumeric`, `alphanumericCaseSensitive`, `text`,
 `textCaseSensitive`, `datetime`, and `basic`; `comparator` takes precedence. Built-in filter types
@@ -187,12 +197,16 @@ restores the exact pre-gesture width state; after a live move it emits the resto
 `lr-filter-change`; `lr-page-change`; `lr-row-collapse`; `lr-row-expand`; `lr-group-collapse` and
 `lr-group-expand` (frozen `{ key, columnId, value, rows }` snapshots); `lr-row-select` with
 canonical `{ selectedRowKeys, selectedRows }` plus mirrored `selectedKeys`; row expand/collapse
-details use canonical `rowKey` plus mirrored `key`;
-`lr-sort-change`; `lr-copy` (frozen `{ ok: true, text }` after fulfillment); `lr-copy-error`
+details use canonical `rowKey` plus mirrored `key`; cancelable `lr-sort-request` (frozen readonly
+`detail: { sort }`) precedes `lr-sort-change`; vetoing it leaves `sort` unchanged and suppresses
+`lr-sort-change`, mirroring `<lr-table>`'s identical `lr-sort-request`/`lr-sort` veto-then-commit
+contract;
+`lr-copy` (frozen `{ ok: true, text }` after fulfillment); `lr-copy-error`
 (frozen `{ ok: false, text, reason, error }` after failure); `lr-error` (compatibility failure
-notification with no raw platform error text). Every library event bubbles and is composed; only `lr-cell-contextmenu` is
-cancelable. Structured details and their owned collections are frozen. The toolbar search and active column-filter inputs re-dispatch `focus` and `blur` once
-from the grid host as bubbling, composed native `FocusEvent`s, preserving `relatedTarget` so
+notification with no raw platform error text). Every library event bubbles and is composed; only
+`lr-cell-contextmenu` and `lr-sort-request` are cancelable. Structured details and their owned
+collections are frozen. The toolbar search and active column-filter inputs re-dispatch `focus` and
+`blur` once from the grid host as bubbling, composed native `FocusEvent`s, preserving `relatedTarget` so
 delegated ancestors can observe editor entry and exit without crossing the shadow boundary.
 
 **Slots:** `empty`, `loading`, `no-results`.

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

@@ -47,6 +47,11 @@ is absent, it uses the localized comparison label. Dynamic host-label changes up
   `sync-scroll="false"`.
 - `anchor: LyraAnchor | string | null = null` (attribute: false) — sends the same target to both
   preview panes; repeated assignment of the same value still re-runs.
+- `maxHeight: string = ''` (attribute `max-height`) — a CSS length (e.g. `"30rem"`) that overrides
+  `--lr-document-compare-pane-max-height` declaratively, giving each `view="side-by-side"` pane its
+  maximum block size before it scrolls internally. The value is sanitized as a CSS length, so an
+  invalid one is ignored and the token default applies; the unset default `''` also defers to the
+  token, so setting nothing preserves existing behaviour.
 
 **Exported types:** `DocumentCompareVersion`; `LyraDocumentCompareView = 'diff' |
 'side-by-side'`; `DocumentComparePaneSide = 'old' | 'new'`.

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

@@ -100,6 +100,23 @@ A focusable action row owned by `<lr-menu>`. The host itself carries `role="menu
 - `type: 'normal' | 'checkbox' = 'normal'`
 - `checked: boolean = false` — meaningful only for `type="checkbox"`
 - `loading: boolean = false`
+- `href?: string` — when set to a safe link URL (`http:`/`https:`/`blob:`/`mailto:`/relative; see
+  `safeLinkHref`, or `safeDownloadHref` when `download` is set, which drops `mailto:`),
+  `[part="base"]` renders as a real `<a href=…>` instead of a `<span>`, and activation (click, or
+  the owning menu's Enter/Space handling, which forwards through `click()` for a link item so the
+  anchor's own native default action runs) navigates there in addition to firing the usual
+  `select()`/`lr-select` contract. An unsafe/unparseable value falls back to the plain `<span>`,
+  matching `lr-button`'s identical fallback
+- `target?: string` — native anchor `target`, used only while `href` resolves to a link. Setting it
+  (e.g. `'_blank'`) always force-adds `noopener noreferrer` to the rendered anchor's `rel`,
+  matching `lr-button`'s identical pattern
+- `rel?: string` — independently settable author relationship tokens, no default. Author tokens are
+  merged rather than replaced: `opener` is always stripped, and whenever `target` is set the
+  non-removable `noopener noreferrer` floor is added, so a same-tab link (no `target`) keeps
+  exactly the author's tokens while a link opening a new context can never lose the guard
+- `download?: string` — native anchor `download` attribute, used only while `href` resolves to a
+  link. Presence narrows the safe-URL allowlist to `safeDownloadHref`'s, which drops `mailto:` — a
+  mail handoff names no retrievable bytes, so it cannot be a download target
 - `hasSubmenu: boolean` (read-only)
 - `submenuOpen: boolean = false` — transient live state; assigning it drives an existing submenu
   without moving focus and disconnect resets it
@@ -190,6 +207,13 @@ properties, slots, parts, methods, checkbox/state events, roving focus, and cano
 `lr-select` behavior. Its host also exposes native, non-bubbling, composed `focus` and `blur`
 events.
 
+**Attributes:** `href`, `target`, `rel`, and `download` — the same link-rendering properties
+documented above for `<lr-menu-item>`, settable directly in markup
+(`<lr-dropdown-item href="/settings" target="_blank">`). The `rel` guard is identical: author
+tokens merge rather than get replaced, `opener` is always stripped, and setting `target` force-adds
+the non-removable `noopener noreferrer` floor, so a same-tab link keeps exactly the author's tokens
+while a link opening a new context can never lose the guard.
+
 **Events:** native, non-bubbling, composed, non-cancelable `focus` and `blur` (`FocusEvent`) when
 the focusable host gains or loses focus, plus the shared menu-item events above.
 

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

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 10 parts, 0 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 11 parts, 0 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -38,7 +38,7 @@ expectedOutput?: string; tags?: readonly string[]; metadata?: Record<string, unk
   `searchable`; empty string leaves the corresponding browser default in effect
 - `accept: string = ''` — forwarded to the internal `lr-file-input`'s `accept` (e.g. `'.json,.csv'`);
   empty accepts any type
-- `exportFormats: ExportFormatOption[] = ['csv', 'json']` (attribute: false) — forwarded to the
+- `exportFormats: readonly LyraExportFormatOption[] = ['csv', 'json']` (attribute: false) — forwarded to the
   internal `lr-export-button`
 - `disabled: boolean = false` (reflected) — disables every add/remove/import/export affordance, e.g.
   while a host-side mutation is still in flight
@@ -57,8 +57,9 @@ loses focus, since native focus neither bubbles nor crosses the shadow boundary.
 All three built-in columns are sortable; activating one of their headers produces that commit for
 the host to apply to its controlled `examples` array.
 
-**CSS parts:** `base`, `toolbar`, `search`, `search-input`, `tag-filter`, `grid`,
-`add-button`, `remove-button`, `import`, `export`.
+**CSS parts:** `base`, `toolbar`, `search`, `search-input`, `search-clear` (replaces the native
+search-cancel glyph the component resets; rendered only while the field has text), `tag-filter`,
+`grid`, `add-button`, `remove-button`, `import`, `export`.
 
 **Known gotchas:**
 

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

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 5 parts, 0 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 6 parts, 0 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -59,13 +59,18 @@ extension?: string }`. Descriptor labels/descriptions are consumer-supplied, alr
 substitute your own server-generated download instead of the built-in client-side one),
 `lr-export-complete` (`detail: { format: 'csv' | 'json' }`, fires only after a non-cancelled
 built-in download completes), `lr-export-error` (`detail: { format: 'csv' | 'json', error:
-unknown }`, fires when a built-in export cannot be serialized or downloaded; activation does not
-throw into consumer code), `lr-show`, `lr-hide` (cancelable format-menu visibility transitions;
-self-imposed closes caused by disablement, loading, or an unusable format list emit neither event)
+unknown }`, fires when a built-in export cannot be serialized or downloaded; the same failure is
+also shown via the trigger's `trigger-error` part and announced through the shared light-DOM live
+region, so a listener is needed only for additional handling; activation does not throw into
+consumer code), `lr-show`, `lr-hide` (cancelable format-menu visibility transitions; self-imposed
+closes caused by disablement, loading, or an unusable format list emit neither event)
 
 **Slots:** none.
 
-**CSS parts:** `trigger`, `menu`, `menu-item`, `format-label`, `format-description`
+**CSS parts:** `trigger`, `trigger-error` (present alongside `trigger` on the same button —
+`part="trigger trigger-error"` — after a built-in CSV/JSON export fails; cleared on the next export
+attempt regardless of outcome — style with `::part(trigger-error)`), `menu`, `menu-item`,
+`format-label`, `format-description`
 
 **Themeable custom properties:** shared tokens only, including `--lr-popover-viewport-clamp`
 (default `92vw`) — the shared narrow-viewport ceiling the `menu`'s max-inline-size is `min()`ed

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

@@ -193,7 +193,10 @@ abort stale contexts, whose callbacks become inert.
 
 The adapter's required `clearValue` is used when the active chip is removed. Its optional
 `isEmpty(value)` defines domain emptiness; without one, the bar compares against `clearValue`
-(including shallow string-array equality). Its optional `formatValue` controls chip display.
+(including shallow string-array equality). Its optional `formatValue(value, locale)` controls chip
+display; `locale` is the filter bar's `effectiveLocale`, the same value every built-in filter
+type's own chip formatting already receives, so an existing single-argument `formatValue`
+implementation keeps working unchanged — JS simply ignores a second parameter it never declared.
 Consequently `false` remains a meaningful active value unless the adapter explicitly declares it
 empty. Custom values may be strings, string arrays, booleans, or `undefined`, so controls such as
 `lr-time-range`, `lr-checkbox`, and an async-backed `lr-combobox` can participate in the same

package/llms/components/lr-flow-minimap.md

@@ -28,12 +28,18 @@ disagree.
   is used (the slotted-into-a-corner-slot case, the primary wiring)
 - `label: string = ''` — accessible name for the map region. A host `aria-label` takes precedence,
   followed by `label`, then the localized default
+- `frame: 'card' | 'plain' = 'card'` (reflected) — container treatment, on the library-wide `frame`
+  vocabulary. `'plain'` removes `[part="base"]`'s border, background and corner radius, for a
+  minimap placed in a host panel or toolbar that already draws its own surface, so the frame isn't
+  doubled. The map's own hover/click affordances and the viewport rect stay either way — only the
+  outer `base` decoration goes. Mirrors `lr-flow-controls`'/`lr-flow-run-status`'s identical `frame`.
 
 **Events:** none.
 
 **Slots:** none.
 
-**CSS parts:** `base`, `map` (the scaled SVG), `node` (one rect per node), `viewport` (the
+**CSS parts:** `base` (the root wrapper; drops its border, background and corner radius under
+`frame="plain"`), `map` (the scaled SVG), `node` (one rect per node), `viewport` (the
 exact visible view rectangle), `viewport-hit-area` (the transparent draggable/focusable target),
 `instructions` (visually hidden keyboard help), and `live-region` (the `aria-hidden` mirror of the
 latest viewport-change text).

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

@@ -55,7 +55,12 @@ app-wide with `registerLyraLocale()` (see `llms/shared.md`); don't rely on the f
 button whose purpose isn't generic.
 
 Host `aria-haspopup` and `aria-expanded` values are forwarded reactively to the shadow-internal
-native button. Host `aria-describedby` targets in the host's own root are resolved through
+native button. `aria-pressed` (`true`, `false`, `mixed`) supports icon-only toggle actions such as
+mute, favorite, or pin; `aria-current` (`page`, `step`, `location`, `date`, `time`, `true`, `false`)
+supports current-item icon buttons such as an active nav/pagination target. Both follow attribute
+changes, removal, and button/link replacement without changing the native role; an empty or
+unsupported token is omitted — mirroring `lr-button`'s own `aria-pressed`/`aria-current`
+forwarding. Host `aria-describedby` targets in the host's own root are resolved through
 `ariaDescribedByElements`. Host `aria-controls` targets use the corresponding
 `ariaControlsElements` API, so using `<lr-icon-button slot="trigger">` inside `<lr-menu>` exposes
 the menu relationship and expanded state on the element that actually receives focus. Supporting

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

@@ -28,7 +28,8 @@ passthrough). Not a subclass of `LyraChart`.
 - `labels: readonly string[] = []` (attribute: false)
 - `datasets: readonly LyraLiteChartSeries[] = []` (attribute: false) —
   `LyraLiteChartSeries { readonly label: string; readonly data: readonly (number|null)[];
-  readonly color?: string }`; the deprecated `LiteSeries` name remains an alias for migration.
+  readonly color?: string }`. The legacy `LiteSeries` name was removed in 9.0.0 — import
+  `LyraLiteChartSeries` instead.
   `color` accepts a valid CSS `color`, while invalid values,
   declaration-breaking input, and `url()` paint servers fall back to the built-in palette. A
   runtime entry whose required `data` member is not an array is dropped while valid siblings

package/llms/components/lr-markdown.md

@@ -19,7 +19,7 @@
 Sanitized Markdown-to-HTML rendering (GFM tables, fenced code blocks, links, blockquotes) built on
 two optional peer dependencies — `marked` (parsing) and `dompurify` (sanitizing) — both lazy-loaded
 independently via `markdown-loader.ts`'s `loadMarkdownDeps()` on first connect, cached per page the
-same way `chart-loader.ts`/`map-loader.ts` cache their load promise so every `<lr-markdown>`
+same way `chart-core-loader.ts`/`map-loader.ts` cache their load promise so every `<lr-markdown>`
 instance on a page shares one load. `heading`/`code`/`blockquote`/`table`/`link`/`image` tokens are
 rendered through a `marked` renderer override that injects `part="..."` attributes directly into the
 produced HTML in a single pass (no second DOM walk after insertion).
@@ -180,7 +180,7 @@ rendered fenced or indented `code-block`), plus shared tokens `--lr-space-xs/-s/
 `--lr-radius`.
 
 **Optional peer deps:** `marked`, `dompurify` (both lazy-loaded via `markdown-loader.ts`'s
-`loadMarkdownDeps()`, mirroring `chart-loader.ts`'s two-independent-optional-peers shape). Each half
+`loadMarkdownDeps()`, mirroring `chart-core-loader.ts`'s two-independent-optional-peers shape). Each half
 is loaded and caught independently — a consumer who installs only `marked` and explicitly sets
 `html-mode="trusted"` (so `dompurify` is never needed) is a valid, supported combination. Also `shiki`,
 the same optional peer `<lr-code-block>` uses, for `highlightCode`'s fenced-block syntax

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

@@ -100,6 +100,23 @@ A focusable action row owned by `<lr-menu>`. The host itself carries `role="menu
 - `type: 'normal' | 'checkbox' = 'normal'`
 - `checked: boolean = false` — meaningful only for `type="checkbox"`
 - `loading: boolean = false`
+- `href?: string` — when set to a safe link URL (`http:`/`https:`/`blob:`/`mailto:`/relative; see
+  `safeLinkHref`, or `safeDownloadHref` when `download` is set, which drops `mailto:`),
+  `[part="base"]` renders as a real `<a href=…>` instead of a `<span>`, and activation (click, or
+  the owning menu's Enter/Space handling, which forwards through `click()` for a link item so the
+  anchor's own native default action runs) navigates there in addition to firing the usual
+  `select()`/`lr-select` contract. An unsafe/unparseable value falls back to the plain `<span>`,
+  matching `lr-button`'s identical fallback
+- `target?: string` — native anchor `target`, used only while `href` resolves to a link. Setting it
+  (e.g. `'_blank'`) always force-adds `noopener noreferrer` to the rendered anchor's `rel`,
+  matching `lr-button`'s identical pattern
+- `rel?: string` — independently settable author relationship tokens, no default. Author tokens are
+  merged rather than replaced: `opener` is always stripped, and whenever `target` is set the
+  non-removable `noopener noreferrer` floor is added, so a same-tab link (no `target`) keeps
+  exactly the author's tokens while a link opening a new context can never lose the guard
+- `download?: string` — native anchor `download` attribute, used only while `href` resolves to a
+  link. Presence narrows the safe-URL allowlist to `safeDownloadHref`'s, which drops `mailto:` — a
+  mail handoff names no retrievable bytes, so it cannot be a download target
 - `hasSubmenu: boolean` (read-only)
 - `submenuOpen: boolean = false` — transient live state; assigning it drives an existing submenu
   without moving focus and disconnect resets it
@@ -190,6 +207,13 @@ properties, slots, parts, methods, checkbox/state events, roving focus, and cano
 `lr-select` behavior. Its host also exposes native, non-bubbling, composed `focus` and `blur`
 events.
 
+**Attributes:** `href`, `target`, `rel`, and `download` — the same link-rendering properties
+documented above for `<lr-menu-item>`, settable directly in markup
+(`<lr-dropdown-item href="/settings" target="_blank">`). The `rel` guard is identical: author
+tokens merge rather than get replaced, `opener` is always stripped, and setting `target` force-adds
+the non-removable `noopener noreferrer` floor, so a same-tab link keeps exactly the author's tokens
+while a link opening a new context can never lose the guard.
+
 **Events:** native, non-bubbling, composed, non-cancelable `focus` and `blur` (`FocusEvent`) when
 the focusable host gains or loses focus, plus the shared menu-item events above.
 

package/llms/components/lr-menu.md

@@ -100,6 +100,23 @@ A focusable action row owned by `<lr-menu>`. The host itself carries `role="menu
 - `type: 'normal' | 'checkbox' = 'normal'`
 - `checked: boolean = false` — meaningful only for `type="checkbox"`
 - `loading: boolean = false`
+- `href?: string` — when set to a safe link URL (`http:`/`https:`/`blob:`/`mailto:`/relative; see
+  `safeLinkHref`, or `safeDownloadHref` when `download` is set, which drops `mailto:`),
+  `[part="base"]` renders as a real `<a href=…>` instead of a `<span>`, and activation (click, or
+  the owning menu's Enter/Space handling, which forwards through `click()` for a link item so the
+  anchor's own native default action runs) navigates there in addition to firing the usual
+  `select()`/`lr-select` contract. An unsafe/unparseable value falls back to the plain `<span>`,
+  matching `lr-button`'s identical fallback
+- `target?: string` — native anchor `target`, used only while `href` resolves to a link. Setting it
+  (e.g. `'_blank'`) always force-adds `noopener noreferrer` to the rendered anchor's `rel`,
+  matching `lr-button`'s identical pattern
+- `rel?: string` — independently settable author relationship tokens, no default. Author tokens are
+  merged rather than replaced: `opener` is always stripped, and whenever `target` is set the
+  non-removable `noopener noreferrer` floor is added, so a same-tab link (no `target`) keeps
+  exactly the author's tokens while a link opening a new context can never lose the guard
+- `download?: string` — native anchor `download` attribute, used only while `href` resolves to a
+  link. Presence narrows the safe-URL allowlist to `safeDownloadHref`'s, which drops `mailto:` — a
+  mail handoff names no retrievable bytes, so it cannot be a download target
 - `hasSubmenu: boolean` (read-only)
 - `submenuOpen: boolean = false` — transient live state; assigning it drives an existing submenu
   without moving focus and disconnect resets it
@@ -190,6 +207,13 @@ properties, slots, parts, methods, checkbox/state events, roving focus, and cano
 `lr-select` behavior. Its host also exposes native, non-bubbling, composed `focus` and `blur`
 events.
 
+**Attributes:** `href`, `target`, `rel`, and `download` — the same link-rendering properties
+documented above for `<lr-menu-item>`, settable directly in markup
+(`<lr-dropdown-item href="/settings" target="_blank">`). The `rel` guard is identical: author
+tokens merge rather than get replaced, `opener` is always stripped, and setting `target` force-adds
+the non-removable `noopener noreferrer` floor, so a same-tab link keeps exactly the author's tokens
+while a link opening a new context can never lose the guard.
+
 **Events:** native, non-bubbling, composed, non-cancelable `focus` and `blur` (`FocusEvent`) when
 the focusable host gains or loses focus, plus the shared menu-item events above.
 

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

@@ -27,6 +27,13 @@ allocating every preceding part for each citation in a citation-heavy or growing
 **Properties:** `parts: MessagePart[] = []` (attribute: false); `contentMode: MessagePartsContentMode =
 'markdown'` (attribute `content-mode`, reflected) and `showReasoning: boolean = true` (attribute
 `show-reasoning`, reflected, with string-aware true-default conversion);
+`maxRenderedParts: number = 0` (attribute `max-rendered-parts`) — `0` (the default) renders every
+part, unbounded, matching every prior release; a positive value windows rendering to the newest N
+parts without touching the host's `parts` data. Citation ranks are unaffected by the window: they
+are still derived from the full sequence first, in the same linear prepass, so a badge's number
+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`).
 

package/llms/components/lr-model-settings-panel.md

@@ -88,7 +88,10 @@ The internal `lr-slider` renders with its own value readout suppressed (`.showVa
 the current temperature is instead shown via this component's own `[part="temperature-value"]` span,
 which formats `temperature` through the cached `Intl.NumberFormat` for the effective locale with up
 to 20 fractional digits, matching `lr-slider`'s own numeric readout. For example, `temperature="0.7"`
-under `locale="de-DE"` displays `0,7`.
+under `locale="de-DE"` displays `0,7`. When the full decimal expansion would exceed 24 characters —
+reachable only through an extreme `temperatureMin`/`temperatureMax`/`temperatureStep` combination —
+the readout switches to bounded scientific notation at up to 6 significant digits instead, so
+`1e308` renders as `7E+307` rather than a 300-digit string that would overflow the label.
 
 The panel's own `temperature` property mirrors the nested slider's _live_ value on every one of its
 `lr-input` events (drag/key-repeat), not just its committed `lr-change` — so `temperature` (and

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

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 10 parts, 0 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 12 parts, 0 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -66,9 +66,10 @@ re-rendered group order confirms the host applied it.
 **Slots:** `header` (content above the search field, e.g. a heading or tabs), `footer` (content
 below the list).
 
-**CSS parts:** `base`, `search`, `list` (the listbox), `group-header`, `item`, `item-icon`,
-`item-label`, `item-description`, `empty` (no-results message), `live-region` (result-count
-announcement).
+**CSS parts:** `base`, `search-field` (wrapper around the search input and its clear button),
+`search`, `search-clear` (clears the query; rendered only while the field has text), `list` (the
+listbox), `group-header`, `item`, `item-icon`, `item-label`, `item-description`, `empty`
+(no-results message), `live-region` (result-count announcement).
 
 **Themeable custom properties:** shared tokens only.
 

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

@@ -129,6 +129,13 @@ span boundary that `Range.surroundContents()` can't wrap stays unpainted (still
 localized label; later loading and error transitions use the shared document-level polite and
 assertive sinks, respectively, without adding live semantics inside the viewer shadow.
 
+**Known capability boundaries** — deliberate, not defects, and stated here so they need not be
+rediscovered: text search and `LyraAnchor` text-quote resolution match **exact** text only, after
+whitespace and soft-hyphen normalization, with no fuzzy or approximate mode. Non-Latin
+cMap-encoded fonts get no special handling beyond whatever the `pdfjs-dist` peer resolves on its
+own — no `cMapUrl`/`cMapPacked` is configured. A scanned or image-only PDF has no text layer at
+all, so it has nothing to select, search or anchor into; it still renders and paginates normally.
+
 `page`, `page-canvas`, `text-layer`, `text-span`, `search-match` and `search-match-active` are
 rendered inside the virtualizing `lr-virtual-list`'s own shadow root and forwarded out through
 `exportparts`, so `lr-pdf-viewer::part(page)` (and each of the others) works from a consumer

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

@@ -28,7 +28,7 @@ invention (no `wa-*`/`sl-*` counterpart).
   against the component's allocation; `'inline'`/`'overlay'` force that presentation.
 - `effectiveMode: LyraResponsivePanelEffectiveMode` (readonly) — the currently resolved
   `'inline'|'overlay'` presentation.
-- `variant: LyraResponsivePanelVariant = 'fullscreen'` (reflected) — only affects the overlay
+- `shape: LyraResponsivePanelShape = 'fullscreen'` (reflected) — only affects the overlay
   presentation's visual treatment: `'fullscreen'` covers the whole viewport; `'bottom-sheet'`
   anchors to its block-end edge and does not cover the full height. Has no visual effect while the effective
   presentation resolves to `'inline'`.
@@ -115,7 +115,7 @@ presentation participates in the shared modal stack rather than nesting a `<lr-d
 The granular route exports the pure
 `resolveResponsivePanelEffectiveMode(mode: LyraResponsivePanelMode,
 belowBreakpoint: boolean): LyraResponsivePanelEffectiveMode` resolver alongside the
-`LyraResponsivePanelMode`/`LyraResponsivePanelEffectiveMode`/`LyraResponsivePanelVariant`/
+`LyraResponsivePanelMode`/`LyraResponsivePanelEffectiveMode`/`LyraResponsivePanelShape`/
 `LyraResponsivePanelCloseReason`/`LyraResponsivePanelModeChangeDetail` types. It's the same logic
 the element's allocation observer calls: `'inline'`/`'overlay'` pass straight through
 unchanged; `'auto'` resolves to `'overlay'` when `belowBreakpoint` is true, `'inline'` otherwise —

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

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 16 parts, 3 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 16 parts, 7 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -23,7 +23,14 @@ parents remain renderable instead of recursing forever.
 **Properties:** `runs: SubagentRun[] = []` (attribute: false);
 `selectedRunId: string | null = null` (attribute `selected-run-id`); `label?: string` — an
 accessible-name override for the `role="tree"` element, where omission reads back `undefined` and
-localizes the default while any supplied string, including `''`, renders verbatim.
+localizes the default while any supplied string, including `''`, renders verbatim; `compact: boolean
+= false` (reflected) — tighter run-row padding/gaps and smaller task/model text, the same density
+convention `lr-task-list`/`lr-stack-trace`/`lr-thinking-panel`/`lr-terminal` already pair with
+`frame`; purely a density knob, since each run's own border stays, so reach for `frame="plain"` to
+drop the chrome entirely; `frame: LyraFrame = 'card'` (reflected) — container treatment for each run
+row, in the library-wide `frame` vocabulary (`'card' | 'plain'`). `'card'` keeps each run's own
+border/radius; `'plain'` drops it, for a transcript or message-bubble context that already draws its
+own border around a nested `<lr-subagent-panel>` and would otherwise double it.
 `SubagentRun = { id: string; parentId?: string; label: string; status: AgentStatusKind; task?:
 string; model?: string; readonly progressRatio?: number; startedAt?: number; endedAt?: number;
 metadata?: Record<string, unknown> }`. `progressRatio` represents completion from `0` to `1`,
@@ -56,3 +63,11 @@ import "@aceshooting/lyra-ui/components/agent-tools/subagent-panel/subagent-pane
 - `--lr-subagent-panel-selected-border` — Selected run border. Default: `var(--lr-color-brand)`.
 - `--lr-subagent-panel-progress-track` — Progress track. Default: `var(--lr-color-border)`.
 - `--lr-subagent-panel-progress-fill` — Progress fill. Default: `var(--lr-color-brand)`.
+- `--lr-subagent-panel-compact-trigger-padding` — `[part="run-trigger"]` padding while `compact`.
+  Default: `var(--lr-space-2xs) var(--lr-space-s)`.
+- `--lr-subagent-panel-compact-trigger-gap` — Gap between `[part="run-trigger"]`'s
+  label/status/task/model/progress while `compact`. Default: `var(--lr-space-2xs)`.
+- `--lr-subagent-panel-compact-font-size` — `[part="task"]`/`[part="model"]` font size while
+  `compact`. Default: `var(--lr-font-size-2xs)`.
+- `--lr-subagent-panel-compact-action-padding` — `[part="cancel"]`/`[part="retry"]` padding while
+  `compact`. Default: `var(--lr-space-2xs)`.

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

@@ -42,6 +42,10 @@ plain text) — this component has no dependency on either.
   behavior differences, see prose below.
 - `durationMs?: number` (attribute `duration-ms`) — how long the reasoning took. Omitted entirely
   (nothing rendered in `'post-hoc'`, a pulsing placeholder in `'live'`) while unset.
+- `follow: boolean = true` (reflected) — whether live, expanded content follows the transcript tail.
+  A user scroll updates this property and emits `lr-follow-change`; a direct assignment is
+  controlled input and emits nothing. Being a `true`-defaulting boolean, `follow="false"` in plain
+  HTML is honoured (it uses `trueDefaultBooleanConverter`), so the attribute form is load-bearing.
 
 **Methods:** `scrollToBottom(): void` — scrolls `[part="body"]` to its current bottom immediately
 (no smooth-scroll animation). Safe to call directly, e.g. from a host that wants to force a