@aceshooting/lyra-ui 23.0.0 → 24.0.0

package/llms/components/lr-streaming-text-core.md

@@ -63,7 +63,8 @@ share one implementation.
 `<lr-streaming-text>`'s own, including the markdown-mode double-fire avoidance (here the composed
 `<lr-markdown-core>` emits it instead of `<lr-markdown>`).
 The forwarded Markdown surface also emits `lr-copy` and `lr-copy-error` for code-block clipboard
-outcomes.
+outcomes. With `internal-link-prefix` set, its intercepted links also pass through
+`lr-link-activate` (`detail: { href: string }`); navigation is prevented.
 
 **Slots:** none — content renders from `content`, not a slot.
 

package/llms/components/lr-streaming-text.md

@@ -97,7 +97,8 @@ listener either way. A consumer composing this element inside a free-form contai
 renders into its own shadow root and a plain light-DOM `MutationObserver` on the container can
 never see that update happen. See `<lr-thinking-panel>`'s own reference at `llms/components/lr-thinking-panel.md`.
 The forwarded Markdown surface also emits `lr-copy` and `lr-copy-error` for code-block clipboard
-outcomes.
+outcomes. With `internal-link-prefix` set, its intercepted links also pass through
+`lr-link-activate` (`detail: { href: string }`); navigation is prevented.
 
 **Slots:** none — content renders from `content`, not a slot.
 
@@ -137,7 +138,7 @@ sets `math` here.
   code-block-header
 ></lr-streaming-text>
 <script type="module">
-  import "@aceshooting/lyra-ui/components/conversation/streaming-text/streaming-text.js";
+  import "@aceshooting/lyra-ui/components/lr-streaming-text.js";
 
   const out = document.getElementById("out");
   let text = "";

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

@@ -58,7 +58,7 @@ and clamped. **Slots:** none.
 **Optional peer deps:** none.
 
 ```ts
-import "@aceshooting/lyra-ui/components/agent-tools/subagent-panel/subagent-panel.js";
+import "@aceshooting/lyra-ui/components/lr-subagent-panel.js";
 ```
 
 **Additional API surface:**

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

@@ -143,7 +143,7 @@ do not need to load Lit. The consumer still owns localized labels, display order
 value:
 
 ```ts
-import "@aceshooting/lyra-ui/components/forms/swatch-picker/swatch-picker.js";
+import "@aceshooting/lyra-ui/components/lr-swatch-picker.js";
 import { GEMSTONES } from "@aceshooting/lyra-ui/theme/gemstones-data.js";
 
 const order = ["emerald", "ruby", "sapphire", "hematite"] as const;
@@ -227,9 +227,9 @@ The consuming Lit component imports these granular entries and lists
 button in the application uses `icon` or `src`:
 
 ```ts
-import '@aceshooting/lyra-ui/components/forms/icon-button/icon-button.js';
-import '@aceshooting/lyra-ui/components/overlays/overlay/popover.js';
-import '@aceshooting/lyra-ui/components/forms/swatch-picker/swatch-picker.js';
+import '@aceshooting/lyra-ui/components/lr-icon-button.js';
+import '@aceshooting/lyra-ui/components/lr-popover.js';
+import '@aceshooting/lyra-ui/components/lr-swatch-picker.js';
 import {
   GEMSTONE_KEYS,
   GEMSTONES,

package/llms/components/lr-switch.md

@@ -163,7 +163,7 @@ Plus shared tokens
 ```html
 <lr-switch name="notifications" checked>Enable notifications</lr-switch>
 <script type="module">
-  import "@aceshooting/lyra-ui/components/forms/switch/switch.js";
+  import "@aceshooting/lyra-ui/components/lr-switch.js";
   const sw = document.querySelector("lr-switch");
   sw.addEventListener("lr-change", (e) => console.log(e.detail.checked)); // prefixed alias
   sw.addEventListener("change", (e) => console.log(e.target.checked)); // native-style, no detail
@@ -187,3 +187,5 @@ checkbox and does not emit `lr-change`.
   neither that nor slotted label text, the control has no accessible name.
 
 ---
+
+<a id="range-controls"></a>

package/llms/components/lr-table.md

@@ -7,9 +7,7 @@
 - **Family** `components/data/` — see `llms/index.md` for its siblings
 - **Status** `stable` since `4.0.0` — see the maturity and deprecation policy in `llms/shared.md`
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [data](https://github.com/aceshooting/lyra-ui/blob/main/packages/lyra-ui/llms/data.md)
-- **Deprecated attribute** `accessible-label` since `22.0.0`; use attribute `Use element.ariaLabel or setAttribute('aria-label', label); host attribute presence takes precedence over the compatibility fallback.`; removal not before `24.0.0` — The native host accessible-name API replaces the component-specific fallback while preserving its existing runtime behavior throughout the compatibility window.
-- **Deprecated event** `lr-retry` since `22.0.0`; use event `addEventListener('lr-retry-request', event => { /* Call preventDefault() to veto the proposed action. */ })`; removal not before `24.0.0` — Cancelable proposals use request event names. The historical event remains a veto alias during its compatibility window.
-- **Deprecated property** `accessibleLabel` since `22.0.0`; use attribute `Use element.ariaLabel or setAttribute('aria-label', label); host attribute presence takes precedence over the compatibility fallback.`; removal not before `24.0.0` — The native host accessible-name API replaces the component-specific fallback while preserving its existing runtime behavior throughout the compatibility window.
+- **Deprecations** none
 - **Optional peers** none
 - **Themeable via** 46 parts, 25 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`
@@ -18,15 +16,10 @@
 
 ## `lr-table`
 
-Sort/select-aware data table with a bounded 100-row default projection. A sortable header first
-emits cancelable `lr-sort-request`; accepted transactions emit `lr-sort` with the same canonical
-`sortKey`/`sortDir`. Client mode updates sort state and orders rows; server mode leaves sort state
-controlled. Optional filtering, bounded pagination, and loading chrome are built in. A
-`columns[].heatValue`-opted-in heat-tint mode paints a shared, normalized color-mix background across
-every tinted cell (auto-derived domain, or overridden via `heatTintScale`); `rowTotal`/`grandTotal`
-add a trailing totals column mirroring `expandedContent`'s leading one — `rowTotal(row)` renders
-per-row, `grandTotal(rows)` renders at its intersection with the footer row — both sharing `footer`'s
-own "consumer computes/renders" contract rather than assuming addition.
+Sort/select-aware table with a bounded 100-row default page, filtering, pagination, and loading
+states. Sort requests are cancelable; accepted client requests update `sortKey`/`sortDir` and order
+rows, while server mode leaves that state controlled. `columns[].heatValue` opts into a shared heat
+scale; `rowTotal`/`grandTotal` position caller-computed totals in a trailing column.
 
 Effective locale changes recollate and filter the current view while keeping activation and edit
 lookups aligned with the rendered page. Direct row focus uses the same stable-key restoration rules;
@@ -38,15 +31,8 @@ it survives and otherwise clamps focus to the nearest surviving index. Moving fo
 table before the update is applied always wins; nested editors and controls keep their independent
 focus contracts.
 
-**9.0 migration:** replace `selectedKey = key` with `selectedRowKeys = new Set([key])`; both single
-and multiple modes now use that one store. Replace `columnsHidden` with read-only
-`hasHiddenPriorityColumns`, `showAllColumns` with `priorityColumnsVisible`, and the two former
-column-visibility events with `lr-priority-columns-visibility-change { visible }`. Column
-`sticky: true` becomes `sticky: 'start'`; `editable: true` becomes
-`editTrigger: 'double-click'`, and `editable: 'always'` becomes `editTrigger: 'always'`. Sort
-listeners now receive phased readonly `{ phase, sortKey, sortDir }` details from
-`lr-sort-request`/`lr-sort`. A bare table now projects 100 rows per page (with inputs bounded to
-1..500); set an explicit finite `page-size` when a different window is required.
+For historical migration mappings, see the [release history archive](https://github.com/aceshooting/lyra-ui/tree/main/docs/changelog).
+Current property and event contracts follow.
 
 **TypeScript:** `LyraTable<T, K extends string | number = string | number>` takes a second type
 parameter for the row-key type. `K` types `rowKey`'s return value,
@@ -306,7 +292,8 @@ cell: (row) => unknown }` — `cell` is required for every `editTrigger` except
   grouped table on a column unrelated to the group key reorders rows inside their groups and
   leaves the grouping intact. The one exception: when the sorted column's value is constant inside
   every group — the group column itself, most obviously — there is nothing to reorder within a
-  group, so the **groups** are ordered by that value instead.
+  group, so the **groups** are ordered by that value instead. To force another group order,
+  pre-sort `rows` or use `sort-mode="server"`.
 - `groupLabel?: (key: string | number, rows: readonly T[]) => unknown` (attribute: false) — custom group
   header content; without it, the group key is rendered as text
 - `expandedContent?: (row: T) => unknown` (attribute: false) — enables a leading expand toggle and
@@ -489,13 +476,10 @@ The internal filter input's composed native `input`/`change` events are containe
 `lr-filter-change` crosses the host boundary. Cell-editor `input`/`change` events are likewise
 contained while an accepted edit publishes `lr-cell-edit`. Internal filter/cell-editor native
 `focus` and `blur` are re-dispatched from the host as bubbling, composed events (the native ones
-are neither). `lr-retry-request` and `lr-retry` — the built-in `[part='retry-button']` was activated, only rendered while
+are neither). `lr-retry-request` — the built-in `[part='retry-button']` was activated, only rendered while
 `error` is set. **Cancelable**: the default action clears `error`; calling `preventDefault()` leaves
 it set, for a consumer that owns its own retry timing (e.g. it wants to keep the banner up until a
 fresh load has actually started, or failed again immediately).
-`lr-retry` is the deprecated cancelable alias, dispatched after `lr-retry-request` with the same
-null detail. Either event can veto clearing the error; subscribe to one spelling. Removal of the
-alias is not before 24.0.0.
 
 **Slots:** `empty` — replaces the built-in empty state on the two _data_-empty branches (no rows at
 all, and filtered/paginated down to zero). Left unfilled, the built-in `[part='empty']` `<lr-empty>`
@@ -579,41 +563,33 @@ body's `max-block-size`). `--lr-table-heat-tint-lo` (default `var(--lr-color-bra
 `--lr-table-heat-tint-hi` (default `var(--lr-color-brand)`) — the `color-mix()` ramp endpoints
 for heat-tint mode's per-cell background, consulted only on columns/rows that define `heatValue`;
 `--lr-table-resize-min-width` (default `var(--lr-size-3rem)`) and
-`--lr-table-resize-handle-opacity` (default `0.12`) control resizable-column behavior. The latter
-remains the legacy shared opacity fallback; `--lr-table-resize-handle-hover-bg` (default
-`var(--lr-color-brand)`), `--lr-table-resize-handle-hover-opacity` (defaulting to the legacy
+`--lr-table-resize-handle-opacity` (default `0.12`) control resizable-column behavior.
+`--lr-table-resize-handle-hover-bg` (default
+`var(--lr-color-brand)`), `--lr-table-resize-handle-hover-opacity` (defaulting to that
 opacity), `--lr-table-resize-handle-active-bg` (defaulting to the hover background), and
 `--lr-table-resize-handle-active-opacity` (defaulting to twice the hover opacity) independently
 retune the rendered interaction states. These heat-tint/resize hooks are not redeclared on the component host: set them on
 `lr-table` or on a theme ancestor, and a table-level value wins through the normal cascade.
-`--lr-table-row-selected-bg` (default `var(--lr-color-brand-quiet)`) — the background of a row whose
-`aria-selected` is `true`, including that row's own `sticky` column cell. Like every state-scoped
-custom property in this library it is an inline
-`var()` fallback at its point of use and is **not** declared on `:host`, so it can be set on the
-element _or on any ancestor_ and still reach the rule that reads it. It exists because Shadow Parts
-forbids an attribute selector after `::part()` — `::part(row)[aria-selected='true']` is invalid CSS —
-so the only prior lever for restyling the selected row was overriding the library-wide
-`--lr-color-brand-quiet` token, which repaints everything else reading it.
+State-scoped hooks below use inline `var()` fallbacks, so values on `lr-table` or an ancestor remain
+effective. Shadow Parts cannot select an attribute after `::part()`.
+`--lr-table-row-selected-bg` (default `var(--lr-color-brand-quiet)`) paints a selected row and its
+own `sticky` cell when `aria-selected="true"`.
 `--lr-table-row-stripe-bg` (default `transparent`) — the background of alternating body rows,
 including each row's own `sticky` column cell. The
-component marks the alternating rows itself, so this works without an invalid `::part(row)` attribute
-or structural-pseudo-class selector and does not affect group, expanded, hover, or selected rows. A
+component marks the alternating rows itself; this does not affect group, expanded, hover, or selected rows. A
 row's hover and pressed fills reach its `sticky` column cell the same way, through an internal
 custom property rather than a themeable token, since neither state has a public hook today.
 `--lr-table-header-sorted-bg` (default `var(--lr-color-surface)`) and `--lr-table-header-sorted-color` (default
 `inherit`) restyle the **currently-sorted** column's header cell (`[aria-sort]` other than `none`),
 including a `sticky` column's own header cell. The opaque surface default prevents body rows from
 showing through the sticky header while it scrolls.
-Same shape and rationale as `--lr-table-row-selected-bg`: inline `var()` fallbacks, not on `:host`,
-because `::part(header-cell)[aria-sort]` is invalid CSS. The `sort-icon` part styles only the
-indicator; these tokens style the header cell itself. Use `::part(sort-icon-inactive)` and
+The `sort-icon` part styles only the indicator; these tokens style the header cell. Use `::part(sort-icon-inactive)` and
 `::part(sort-icon-active)` to style the two indicator states without private selectors.
 `--lr-table-sticky-offset` (default `0`) is measured and written inline per column by the component
 so multiple `sticky` columns stack instead of overlapping; it is a read-out, not a knob you set.
 `--lr-table-heat-t` is likewise component-written (each `[data-heat]` cell's position on the ramp).
 `[part="base"]`, the table's own scroll container, 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
+`--lr-theme-scrollbar-width`/`--lr-theme-scrollbar-gutter` hooks (defaults `auto`/`auto`) — set either on `:root` or any ancestor for one
 declaration to retheme every internal scroll container in the library, including
 `lr-virtual-list`, `lr-scroller`, `lr-carousel`, `lr-code-block`, and `lr-code-editor`.
 
@@ -660,31 +636,18 @@ declaration to retheme every internal scroll container in the library, including
 
 **Known gotchas:**
 
-- accepted sortable-header activation writes `sortKey`/`sortDir` only in client mode. Server mode
-  keeps those properties controlled and reports the accepted proposal in `lr-sort`; veto
-  `lr-sort-request` to suppress both state change and commit. The built-in transaction toggles only
-  between two directions, so a tri-state header (asc → desc → unsorted) remains consumer-owned.
+- The built-in sort transaction toggles between `asc` and `desc`; a tri-state header with an
+  unsorted state remains consumer-owned. Veto `lr-sort-request` to suppress state change and commit.
 - `sortValue`/`cell` are read off the column object by identity. Mutating a column **in place**
   (`t.columns[0].sortValue = …`) neither re-renders nor re-sorts; assign a new `columns` array.
-- `groupBy` + client sorting are **not** in conflict: the sort runs per group, not across the whole
-  set, so group rows stay contiguous. The consequence is that the group order is normally yours to
-  control — it follows first appearance in `rows`. The single exception is a sort on a column whose
-  value is constant inside every group (the group column itself, a column functionally determined
-  by the group key, or any column at all when every group holds one row): the within-group sort
-  would be a provable no-op, so the groups are ordered by that constant value instead. That is what
-  keeps `aria-sort` and the header chevron honest — otherwise clicking the group column would flip
-  both while changing nothing. To force a group order in any other case, sort `rows` into it before
-  assigning them (or set `sort-mode="server"` and own the whole ordering).
 - both single and multiple row selection use `selectedRowKeys`; the component does not synthesize a
   checkbox column, so a bulk-select UI still belongs in `headerCell()`/`cell()` callbacks.
 - A host `aria-label` (or native `ariaLabel` property) names the internal `<table role="grid">`.
-  Presence wins, including an explicitly empty string. `accessibleLabel?: string` (attribute
-  `accessible-label`) remains a deprecated fallback, with removal not before 24.0.0; an explicit
-  empty fallback stays empty when the host name is absent. Caller text bypasses localization.
+  Presence wins, including an explicitly empty string. Caller text in the host `aria-label` bypasses localization.
 - `caption: string = ''` — an optional visible `<caption>` (exposed as the `caption` CSS part). When
-  no `accessibleLabel`/host `aria-label` is present the caption also names the grid via
+  no host `aria-label` is present the caption also names the grid via
   `aria-labelledby`.
-- A grid with **none** of `accessibleLabel`, host `aria-label`, or `caption` logs a one-time
+- A grid with **none** of host `aria-label` or `caption` logs a one-time
   `console.warn` on first render in development builds only — an unnamed grid is an accessibility
   defect that otherwise renders silently. Production and unknown/unbundled runtimes do not log it.
 - `revealColumnsLabel`/`columnsHideLabel` only ever reach the DOM on
@@ -692,11 +655,10 @@ declaration to retheme every internal scroll container in the library, including
   `priority`. Setting either label with no `priority` column is therefore always inert — it logs
   the same shape of one-time, development-only, production-silent `console.warn` as the missing
   accessible-name check above, rather than failing silently.
-- Full roving-tabindex grid keyboard pattern (one `tabindex="0"` stop among header cells, one among
-  body rows) — Left/Right/Home/End move within the header row, Up/Down/Home/End move within the
-  body, Down from the header enters the body's roving stop and Up from the body's first row returns
-  to the header, Enter/Space still only sort/activate — a genuine strength versus most siblings in
-  this family. A `priority`-hidden header/cell is skipped when computing the visible header stops,
+- The grid has one roving `tabindex="0"` stop among header cells and one among body rows.
+  Left/Right/Home/End navigate headers; Up/Down/Home/End navigate rows. Down from a header enters
+  the body, Up from its first row returns to the header, and Enter/Space sort or activate.
+  A `priority`-hidden header/cell is skipped when computing visible header stops,
   so arrow-key navigation never strands the roving stop on a hidden column.
 - a `cell()` template can render its own interactive content without it being swallowed by
   row/column activation. Delegated clicks and Enter/Space inspect the event's composed path for
@@ -730,23 +692,9 @@ declaration to retheme every internal scroll container in the library, including
   as the cell's accessible _name_, replacing the cell's content rather than supplementing it (the
   same caveat `lr-stat`'s `exactValue` carries). Use it for a longer form of what the cell already
   shows, never for information that exists nowhere else.
-- `editTrigger: 'always'` deliberately does not re-assert a `'text'`/`'number'` cell's source value
-  once the user has typed into it. That is the native dirty-value-flag behavior the attribute
-  binding buys, and it is the point: a background `rows` refresh cannot silently overwrite an
-  in-progress edit. If you need the
-  opposite — an authoritative external value that always wins — do not use `'always'`; re-key the
-  row (`rowKey`) so the editor is recreated rather than updated, or use `editTrigger: 'double-click'` and let
-  the short-lived double-click editor's property binding re-assert. Also note the two things
-  `'always'` intentionally does _not_ do: it never sets the roving `tabindex` (its editors are
-  ordinary tab stops, so Tab order in that column interleaves with the grid's two roving stops,
-  the same way the row-expand toggle's already does), and it never cancels Escape.
-- `editType: 'select'` renders a native `<select>`, populated from `columns[].editOptions`
-  (`{ value: string; label: string }[]`, one `<option>` per entry in order); a `'select'` column
-  with no `editOptions` renders an empty, valueless `<select>` rather than throwing. Unlike the
-  `'text'`/`'number'` editors, `<select>`/`<option>` carry no native dirty-value flag, so the
-  protection described above for a persistent `'always'` editor does not extend to a `'select'`
-  one — a background `rows` refresh re-applies the selection to a persistent select editor even
-  after the user has picked a different, uncommitted option. The double-click flavor is unaffected
-  by this distinction either way, since it is always short-lived.
+- For an externally authoritative value, re-key the row (`rowKey`) to recreate an `'always'`
+  editor, or use the transient `editTrigger: 'double-click'` editor. Persistent text/number editors
+  otherwise retain dirty drafts; persistent select editors re-apply refreshed selections, as
+  described under `columns[].editTrigger` above.
 
 ---

package/llms/components/lr-terminal.md

@@ -7,7 +7,7 @@
 - **Family** `components/agent-tools/` — see `llms/index.md` for its siblings
 - **Status** `stable` since `4.0.0` — see the maturity and deprecation policy in `llms/shared.md`
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [agent-tools](https://github.com/aceshooting/lyra-ui/blob/main/packages/lyra-ui/llms/agent-tools.md)
-- **Deprecated event** `lr-download` since `22.0.0`; use event `addEventListener('lr-download-request', event => { /* Call preventDefault() to veto the proposed action. */ })`; removal not before `24.0.0` — Cancelable proposals use request event names. The historical event remains a veto alias during its compatibility window.
+- **Deprecations** none
 - **Optional peers** none
 - **Themeable via** 16 parts, 18 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`
@@ -65,7 +65,7 @@ plain text of the whole buffer.
 
 **Events:** `lr-copy` (`detail: { ok: true, text }`, emitted only after a successful clipboard write),
 `lr-error` (no detail) and `lr-copy-error` (`detail: { ok: false, text, reason, error }`) on clipboard failure,
-`lr-download-request` and `lr-download` (`detail: { filename }`, cancelable — by
+`lr-download-request` (`detail: { filename }`, cancelable — by
 default the component creates a plain-text `Blob`/object URL and activates a synthetic
 `<a download>`; `preventDefault()` suppresses that built-in download so the host can substitute
 server-side or other handling),
@@ -74,9 +74,6 @@ matchCountExact, activeIndex }`; `matchCountExact` is `false` once a search hits
 ceiling, marking `matchCount` as a lower bound rather than an exact total),
 `lr-highlight-activate` (`detail: { highlightId }`), and `lr-text-select` (`detail: {
 text, anchor, rects }`).
-`lr-download` is the deprecated cancelable alias, dispatched after `lr-download-request` with the
-same filename detail. Either event can suppress the built-in download; it is not a completion
-notification. Subscribe to one spelling.
 
 
 **CSS parts:** `base`, `toolbar` (only rendered when copy/download are enabled), `copy-button`,

package/llms/components/lr-textarea.md

@@ -41,7 +41,7 @@ disabled state.
   resize="auto"
 ></lr-textarea>
 <script type="module">
-  import "@aceshooting/lyra-ui/components/forms/textarea/textarea.js";
+  import "@aceshooting/lyra-ui/components/lr-textarea.js";
   const bio = document.querySelector('lr-textarea[label="Bio"]');
   await bio.updateComplete; // both calls are no-ops before the first render
   bio.scrollPosition({ top: 0 }); // pin a restored draft back to the top

package/llms/components/lr-thread-list.md

@@ -7,8 +7,7 @@
 - **Family** `components/conversation/` — see `llms/index.md` for its siblings
 - **Status** `stable` since `4.0.0` — see the maturity and deprecation policy in `llms/shared.md`
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [conversation](https://github.com/aceshooting/lyra-ui/blob/main/packages/lyra-ui/llms/conversation.md)
-- **Deprecated event** `lr-retry` since `22.0.0`; use event `addEventListener('lr-retry-request', event => { /* Call preventDefault() to veto the proposed action. */ })`; removal not before `24.0.0` — Cancelable proposals use request event names. The historical event remains a veto alias during its compatibility window.
-- **Deprecated property** `compact` / `compact` since `22.0.0`; use property `Use size="s" for compact rows and size="m" for the default row density.`; removal not before `24.0.0` — The shared size vocabulary describes row density and search-control scale together. The boolean compatibility spelling remains mapped to the small and medium size tiers throughout its deprecation window.
+- **Deprecations** none
 - **Optional peers** none
 - **Themeable via** 42 parts, 20 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`
@@ -42,9 +41,9 @@ string | number; pinned?: boolean; archived?: boolean }`; `ThreadRowAction = 'pi
 'delete'`; `ThreadListGrouping = 'date' | 'custom' | 'none'`; `ThreadBucketKey = 'pinned' |
 'today' | 'yesterday' | 'previous7' | 'previous30' | `month:${string}` | 'archived'`;
 `ThreadGroupContext { id: string; threads: readonly LyraChatThread[]; bucket?: ThreadBucketKey;
-date?: Date }`; and `ThreadGroupToggleDetail { groupId: string; expanded: boolean; collapsed:
-boolean }` (the shared payload type for the `lr-group-toggle-request`/`lr-group-toggle` pair;
-`collapsed` is the deprecated inverse of `expanded`, removed in 23.0.0). `LyraThreadList` and
+date?: Date }`; and `ThreadGroupToggleDetail { groupId: string; expanded?: boolean }` (the shared
+payload type for the `lr-group-toggle-request`/`lr-group-toggle` pair; this component supplies
+`expanded` on emitted events, though the type keeps it optional). `LyraThreadList` and
 `LyraThreadListEventMap` are exported alongside them. The class
 module, normal and stable tag-shaped registration entries, conversation family entry, and package
 root all retain this complete thread-list surface; the former `ChatThread` name is not retained.
@@ -92,9 +91,7 @@ data mode only: built-in icon buttons rendered into each row's `actions` slot. `
 = false` (attribute `with-archived`, reflected) — data mode: include `archived` threads (in their own
 trailing group). `withoutRename: boolean = false` (attribute `without-rename`, reflected) — forwarded to
 each data-mode row, turning its inline rename off.
-`compact: boolean = false` (reflected, deprecated; removal not before 24.0.0) — compatibility
-alias of `size="s"` when true and `size="m"` when false. Use `size` for both search and data rows;
-slotted rows retain their own size. `stickyGroups: boolean = false` (attribute `sticky-groups`, reflected) — data mode: pins
+`stickyGroups: boolean = false` (attribute `sticky-groups`, reflected) — data mode: pins
 the current date/custom group's header to the top of the scroll viewport while its rows are in view,
 pushing it off as the next group's header arrives. Group headers are ordinary virtualized rows, so
 this renders an `aria-hidden` copy of the header into the internal `lr-virtual-list`'s sticky layer:
@@ -172,11 +169,10 @@ including its retry button, while `error` is set.
 built-in confirmation), `lr-thread-rename` (`detail: { conversationId, label }`, correlated and
 re-emitted from the owned row), `lr-filter-change` (`detail: { text, matchCount }`). Slotted mode
 instead emits `lr-query-change` (`detail: { text }`) and never claims a match count it cannot own.
-`lr-group-toggle-request` (`detail: { groupId, expanded, collapsed }`, cancelable; `expanded` is
-the canonical key and the deprecated `collapsed` its inverse) — proposed before a
+`lr-group-toggle-request` (`detail: { groupId, expanded }`, cancelable) — proposed before a
 custom/date group's collapse state changes; calling `preventDefault()` skips the built-in
 `collapsedGroupIds` write and suppresses the following `lr-group-toggle`, leaving the group's
-collapse state fully controlled. `lr-group-toggle` (`detail: { groupId, expanded, collapsed }`) — the
+collapse state fully controlled. `lr-group-toggle` (`detail: { groupId, expanded }`) — the
 change was accepted and, unless `lr-group-toggle-request` was prevented, already applied to
 `collapsedGroupIds`; native group buttons provide Enter/Space activation and explicit
 `aria-expanded="true"|"false"` regardless. A consumer that already listens for `lr-group-toggle`
@@ -186,9 +182,7 @@ assignment simply wins last. `searchable` only: `blur`/`focus` (no detail) — r
 the internal search `<input>`'s own `blur`/`focus`, bubbling and composed unlike the native events,
 which are neither. `lr-retry-request` (`detail: null`, cancelable) — the built-in `[part='retry-button']`
 was activated, only rendered while `error` is set; the default action clears `error`,
-`preventDefault()` leaves it set instead. `lr-retry` is its deprecated cancelable veto alias,
-emitted after `lr-retry-request` and before the default action; canceling either event keeps the
-error state.
+`preventDefault()` leaves it set instead.
 **CSS parts:** `base`, `search`/`search-input` (the search field wrapper and `<input
 type="search">`), `clear-button` (clears the search field; rendered only while it has a value,
 mirroring `<lr-input>`'s own `clearable` contract's part name), `list` (the list region), `empty`,

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

@@ -195,6 +195,6 @@ ancestor to change every unset time input beneath it.
 ></lr-time-input>
 <lr-time-input label="Precise time" step="15" value="09:30:15"></lr-time-input>
 <script type="module">
-  import "@aceshooting/lyra-ui/components/forms/input/time-input.js";
+  import "@aceshooting/lyra-ui/components/lr-time-input.js";
 </script>
 ```

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

@@ -116,8 +116,8 @@ toggles join, and `var(--lr-space-2xs)` when vertical) and `--lr-toggle-group-wr
 
 ```html
 <script type="module">
-  import '@aceshooting/lyra-ui/components/forms/toggle-group/toggle-group.js';
-  import '@aceshooting/lyra-ui/components/forms/toggle/toggle.js';
+  import '@aceshooting/lyra-ui/components/lr-toggle-group.js';
+  import '@aceshooting/lyra-ui/components/lr-toggle.js';
 </script>
 
 <lr-toggle-group label="Text formatting" appearance="outlined">

package/llms/components/lr-toggle.md

@@ -115,7 +115,7 @@ and press get outline affordances, and disabled toggles read as `GrayText` at fu
 
 ```html
 <script type="module">
-  import '@aceshooting/lyra-ui/components/forms/toggle/toggle.js';
+  import '@aceshooting/lyra-ui/components/lr-toggle.js';
 </script>
 
 <lr-toggle value="bold">Bold</lr-toggle>

package/llms/components/lr-tool-approval-dialog.md

@@ -7,8 +7,7 @@
 - **Family** `components/agent-tools/` — see `llms/index.md` for its siblings
 - **Status** `stable` since `4.0.0` — see the maturity and deprecation policy in `llms/shared.md`
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [agent-tools](https://github.com/aceshooting/lyra-ui/blob/main/packages/lyra-ui/llms/agent-tools.md)
-- **Deprecated event** `lr-approve` since `22.0.0`; use event `addEventListener('lr-approve-request', event => { /* Call preventDefault() to veto the proposed action. */ })`; removal not before `24.0.0` — Cancelable proposals use request event names. The historical event remains a veto alias during its compatibility window.
-- **Deprecated event** `lr-deny` since `22.0.0`; use event `addEventListener('lr-deny-request', event => { /* Call preventDefault() to veto the proposed action. */ })`; removal not before `24.0.0` — Cancelable proposals use request event names. The historical event remains a veto alias during its compatibility window.
+- **Deprecations** none
 - **Optional peers** none
 - **Themeable via** 22 parts, 4 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`
@@ -83,10 +82,10 @@ renders at the start of the action row, before Deny/Edit/Approve.
 void` and `close(reason = 'api'): void` close through the same reasoned lifecycle, emit `lr-close`,
 and return focus to whatever had it before opening; all are no-ops when already in the target state.
 
-**Events:** `lr-approve-request` and `lr-approve` (`detail: { args: unknown }` — the current, already-parsed arguments: the
+**Events:** `lr-approve-request` (`detail: { args: unknown }` — the current, already-parsed arguments: the
 original `args` prop, or the user's edited-and-validated version if an edit was in progress.
 Cancelable: a listener calling `preventDefault()` sets `pendingAction` to `'approve'` instead of
-closing; otherwise followed by `lr-close` with reason `'approve'`), `lr-deny-request` and `lr-deny`
+closing; otherwise followed by `lr-close` with reason `'approve'`), `lr-deny-request`
 (`detail: null`, cancelable, with the same `pendingAction` mechanism,
 setting `pendingAction` to `'deny'`; otherwise followed by `lr-close` with reason `'deny'`), `lr-close`
 (`detail: { reason: ToolApprovalDialogCloseReason }` — fired exactly once per dismissal, via Escape, an opted-in
@@ -95,9 +94,7 @@ dialog inside a consumer's own `<lr-dialog>` means that dialog's `lr-close` list
 this event, see `<lr-dialog>`'s `lr-close` section in `overlays.md` for the full list of emitters
 and the target-filtering guard), and no-detail `focus`/`blur` events
 re-dispatched when the raw-JSON editor gains or loses focus.
-`lr-approve` and `lr-deny` are deprecated cancelable aliases of their respective requests. Each
-follows its request with the same detail; preventing either spelling holds that decision pending.
-Subscribe to one spelling per action. `lr-close` remains the non-cancelable dismissal notification.
+`lr-close` remains the non-cancelable dismissal notification.
 
 `waitUntil()` is `<lr-confirm-bar>`-only and this dialog does not carry it. The two components share
 the `lr-approve-request`/`lr-deny-request` event *names*, so the generated `HTMLElementEventMap['lr-approve-request']` is the

package/llms/components/lr-tool-call-block.md

@@ -106,7 +106,7 @@ The running glyph spins and the pending glyph pulses at `--lr-transition-ambient
 
 ```html
 <script type="module">
-  import '@aceshooting/lyra-ui/components/agent-tools/tool-call-block/tool-call-block.js';
+  import '@aceshooting/lyra-ui/components/lr-tool-call-block.js';
 </script>
 
 <lr-tool-call-block name="web_search" call-id="call-1" status="success" duration-ms="1450"></lr-tool-call-block>

package/llms/components/lr-tool-timeline.md

@@ -7,7 +7,7 @@
 - **Family** `components/agent-tools/` — see `llms/index.md` for its siblings
 - **Status** `stable` since `4.1.0` — see the maturity and deprecation policy in `llms/shared.md`
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [agent-tools](https://github.com/aceshooting/lyra-ui/blob/main/packages/lyra-ui/llms/agent-tools.md)
-- **Deprecated event** `lr-tool-approval-decide` since `22.0.0`; use event `addEventListener('lr-tool-approval-decide-request', event => { /* Call preventDefault() to veto the proposed action. */ })`; removal not before `24.0.0` — Cancelable proposals use request event names. The historical event remains a veto alias during its compatibility window.
+- **Deprecations** none
 - **Optional peers** none
 - **Themeable via** 17 parts, 14 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`
@@ -73,7 +73,7 @@ data or exhausting the page.
 non-approval entry activation and `lr-tool-render-error` (`detail: { invocationId: string;
 sourceKey?: string; toolName: string; error: unknown }`) for a contained nested renderer failure.
 The raw child chip-selection, renderer-error, details, and dialog events do not leak across the
-timeline boundary. `lr-tool-approval-decide-request` and `lr-tool-approval-decide` (`detail: ToolTimelineApprovalDetail` =
+timeline boundary. `lr-tool-approval-decide-request` (`detail: ToolTimelineApprovalDetail` =
 `ToolApprovalEventDetail & { args?: unknown; sourceKey?: string }` = `{ invocationId: string;
 approved: boolean; args?: unknown; sourceKey?: string }`, extending the shared detail from
 `@aceshooting/lyra-ui/ai`). `args` is present only when
@@ -88,9 +88,6 @@ A host may instead resolve the decision synchronously by reassigning `entries` (
 `finalizePendingApproval()`: the entry's live state is re-checked immediately after dispatch, so
 `pendingApproval` — and the shared dialog's pending presentation — is never set or left set for
 an entry that no longer needs a decision.
-`lr-tool-approval-decide` is the deprecated cancelable alias, dispatched after its request with
-the same detail. Either spelling can hold the pending decision; subscribe to one spelling. It is
-not a completed-decision notification.
 
 ```ts
 timeline.addEventListener("lr-tool-approval-decide-request", async (event) => {

package/llms/components/lr-video-playlist.md

@@ -19,7 +19,7 @@
 Experimental direct-child `<lr-video>` playlist with a visible current-video stage and
 keyboard-navigable item list. It mirrors the public Web Awesome Video Playlist API under the `lr-`
 prefix. Import the granular registration entry with
-`import '@aceshooting/lyra-ui/components/media/video-playlist/video-playlist.js'`.
+`import '@aceshooting/lyra-ui/components/lr-video-playlist.js'`.
 
 **Properties:** `controls: 'none' | 'standard' | 'full' = 'full'` (reflected and forwarded to every
 direct child), and `iconLibrary: string = 'system'` (attribute `icon-library`, non-reflected and

package/llms/components/lr-video.md

@@ -19,7 +19,7 @@
 Experimental inline native video player with custom controls, safe declarative sources/tracks,
 selectable captions, and bounded WebVTT thumbnail previews. It mirrors the public Web Awesome Video
 API under the `lr-` prefix. Import the granular registration entry with
-`import '@aceshooting/lyra-ui/components/media/video/video.js'`.
+`import '@aceshooting/lyra-ui/components/lr-video.js'`.
 
 When progress is unavailable, the disabled native range input and its visible timeline track retain
 resting paint under hover and press. Once media duration makes progress available, the track retains

package/llms/components/lr-widget-renderer.md

@@ -58,9 +58,10 @@ readonly slot?: string; readonly actionId?: string; readonly payload?: unknown }
   structure throws `TypeError`. Node records, child arrays, and prop records are copied and frozen,
   while opaque prop values and action payloads intentionally retain caller identity.
 
-The package root and the normal `widget-renderer.js` registration entry expose the renderer
-`LyraWidgetRenderer`/`LyraWidgetRendererEventMap` together with the complete stable authoring
-surface: `LyraWidgetNode`, `LyraWidgetBinding`, `LyraWidgetDocument`, `createWidgetDocument`,
+The `widget-renderer.class.js` class entry and stable `components/lr-widget-renderer.js` registration
+entry expose `LyraWidgetRenderer`; its event-map type and stable authoring contracts remain available from
+the curated package root: `LyraWidgetRendererEventMap`, `LyraWidgetNode`, `LyraWidgetBinding`,
+`LyraWidgetDocument`, `createWidgetDocument`,
 `LyraWidgetPropType`, `LyraWidgetInteraction`, `LyraWidgetTypeDefinition`,
 `LyraWidgetTypeRegistry`, `createWidgetTypeRegistry`, `isWidgetTypeRegistry`, and
 `DEFAULT_WIDGET_TYPE_REGISTRY`. Advanced consumers that need `resolveTree`, `ResolveContext`,
@@ -145,8 +146,8 @@ import {
   createWidgetDocument,
   createWidgetTypeRegistry,
   DEFAULT_WIDGET_TYPE_REGISTRY,
-} from "@aceshooting/lyra-ui/components/conversation/widget-renderer/widget-renderer.js";
-import "@aceshooting/lyra-ui/components/data/sparkline/sparkline.js";
+} from "@aceshooting/lyra-ui/components/lr-widget-renderer.js";
+import "@aceshooting/lyra-ui/components/lr-sparkline.js";
 import { tag } from "@aceshooting/lyra-ui/utilities/prefix.js";
 
 const registry = createWidgetTypeRegistry([
@@ -180,7 +181,7 @@ import { LyraWidgetRenderer } from "@aceshooting/lyra-ui/components/conversation
 import { createWidgetDocument } from "@aceshooting/lyra-ui/components/conversation/widget-renderer/resolve.js";
 import { createWidgetTypeRegistry } from "@aceshooting/lyra-ui/components/conversation/widget-renderer/registry.js";
 import { defineElement, tag } from "@aceshooting/lyra-ui/utilities/prefix.js";
-import "@aceshooting/lyra-ui/components/forms/input/input.js";
+import "@aceshooting/lyra-ui/components/lr-input.js";
 
 defineElement("widget-renderer", LyraWidgetRenderer);
 

package/llms/components/lr-zoomable-frame.md

@@ -107,7 +107,7 @@ attributes, and inline properties Lyra changed, preserving any later iframe-owne
 a watched host-page theme attribute syncs again.
 
 ```js
-import "@aceshooting/lyra-ui/components/media/zoomable-frame/zoomable-frame.js";
+import "@aceshooting/lyra-ui/components/lr-zoomable-frame.js";
 ```
 
 ```html