@aceshooting/lyra-ui 23.0.0 → 24.1.0

package/llms/components/lr-button.md

@@ -16,44 +16,21 @@
 
 ## `lr-button`
 
-Host `aria-keyshortcuts` is forwarded reactively to the internal native button or link, including
-attribute removal and button/link presentation changes.
-
-A generic action-button primitive. Renders an internal native `<button>`; `type="submit"`/
-`type="reset"` are handled by the component itself via its browser-resolved form owner (including
-an external owner named by `form`), since a shadow-internal native button doesn't participate in a
-light-DOM form's submission on its own. They remain default actions of the composed native
-`click`: `preventDefault()` from any listener on that click path vetoes submit/reset before it
-runs, while `stopPropagation()` alone does not. Canceling the form's later `submit` or `reset`
-event remains an independent veto point.
-
-External descriptions follow the current source element identity when an element with the same ID
-replaces it, when a source is removed or reinserted, and when the control reconnects or moves to
-another document. Host-root lookup and ordering follow the current `aria-describedby` list,
-including unresolved IDs and duplicates. Switching between native button and anchor modes keeps the
-relationship on the current action. Existing accessible names and `aria-controls` relationships
-retain their separate contracts.
-
-Set `href` to a safe link URL and the root renders as a real `<a part="base" href=…>` instead — a
-link styled as a button (e.g. a CTA). Native navigation is then the activation, so the submit/reset
-handling and `type` have no effect in that mode. A disabled link button (its own `disabled` or an
-ancestor `<fieldset disabled>`) renders the anchor with `aria-disabled="true"` and **no `href`**, so
-it is neither focusable nor navigable; it also dims to `--lr-opacity-disabled` with a `not-allowed`
-cursor and no hover/press feedback, exactly like the disabled `<button>` path (an `<a>` can never
-match `:disabled`, so that arm of the styling keys off `aria-disabled` instead). An
-unsafe/unparseable `href` falls back to the native `<button>`.
-
-The label does **not** grow to fill a stretched button. `[part="label"]` shrink-wraps its text and
-the whole icon+label pair centres under `--lr-button-justify`, so the icon-to-text distance is
-exactly `--lr-button-gap`. Before 16.0.0 the label was `flex: 1 1 auto`, which parked every spare
-pixel inside the label box and — because the native `<button>` UA stylesheet centres text, which the
-label wrapper inherited — floated the text in the middle of a wide empty row. A `with-caret` button,
-and one with an `end`/`suffix` adornment, keep the growing label so that trailing affordance stays
-pinned to the trailing content edge. `--lr-button-label-grow: 1` restores the old stretch and `0`
-opts a caret/end-adornment row out of pinning. The label is also `text-align: start` now, which
-fixes two side effects of the inherited centring: a label narrower than its own text centred the
-overflow so the ellipsis appeared at the end while the start of the word was clipped, and the `<a>`
-root (which never inherited the centring) disagreed with the `<button>` root across a mode switch.
+Renders a native `<button>` or, with a safe `href`, a native `<a>`. Submit/reset use the
+browser-resolved form owner, including an external `form` owner, and run as default actions of the
+composed `click`; `preventDefault()` vetoes them, while `stopPropagation()` alone does not. The
+form's later `submit`/`reset` event can be canceled separately. Link mode navigates instead, and a
+disabled link has `aria-disabled="true"` with no `href`, focus, or navigation.
+
+Host `aria-keyshortcuts` and `aria-describedby` follow the internal button or link reactively.
+Description IDs resolve in the host root, preserving order, unresolved IDs, and duplicates; source
+replacement, removal, reconnection, and adoption update the relationship. Accessible names and
+`aria-controls` have separate contracts below.
+
+`[part="label"]` shrink-wraps with `text-align: start`, keeping ellipsis at the trailing edge.
+The icon and label stay centered under `--lr-button-justify`, separated by `--lr-button-gap`.
+`with-caret` or an `end`/`suffix` adornment makes the label grow to pin trailing content; use
+`--lr-button-label-grow: 1` to opt into that stretch or `0` to opt out.
 
 **Properties:**
 
@@ -63,7 +40,8 @@ root (which never inherited the centring) disagreed with the `<button>` root acr
   so a `mailto:` href paired with `download` falls back to the native `<button>`. Unset (the default)
   renders a plain `<button>`, unchanged. `type` (submit/reset) has no effect while the anchor
   renders. While the button is disabled the anchor is rendered **without** `href` (keeping
-  `aria-disabled="true"`), so a disabled link button cannot navigate. An unsafe/unparseable value
+  `aria-disabled="true"`), so it cannot navigate; it also uses `--lr-opacity-disabled`, a
+  `not-allowed` cursor, and no hover/press feedback. An unsafe/unparseable value
   falls back to the native `<button>`
 - `target?: string` — native anchor `target`, used only while `href` resolves to a link. Setting it
   (e.g. `'_blank'`) automatically force-adds `noopener noreferrer` to the rendered anchor's
@@ -81,15 +59,11 @@ root (which never inherited the centring) disagreed with the `<button>` root acr
   `primary` → `brand`, and `text` → neutral `appearance="plain"`. The Lyra/Web Awesome default is
   intentionally still `neutral`
 - `appearance: 'accent' | 'filled' | 'outlined' | 'filled-outlined' | 'plain' | 'quiet' | 'link' =
-'accent'` (reflected) — the library's shared fill vocabulary plus this component's own two extra
-  tiers. **Breaking in 8.0.0: the default moved from `'filled'` to `'accent'`**, so a bare
-  `<lr-button>` now paints the loud fill it used to need `appearance="accent"` for. The two are no
-  longer near-duplicates: `'accent'` takes the active `variant`'s **loud** fill
+'accent'` (reflected) — the shared fill vocabulary plus two button-specific tiers. `'accent'`
+  takes the active `variant`'s **loud** fill
   (`--lr-button-accent-fill`) with the foreground guaranteed legible on it, while `'filled'` takes
   that variant's **quiet** tint (`--lr-button-fill`) — a secondary-action fill that still reads as a
-  fill rather than as the page surface. Before 8.0.0 every chromatic variant's `'filled'` and
-  `'accent'` resolved to the same loud token and rendered identically, while `variant="neutral"`'s
-  `'filled'` was the page surface, i.e. no fill at all. `'filled-outlined'` is `'filled'`'s fill and
+  fill rather than as the page surface. `'filled-outlined'` is `'filled'`'s fill and
   foreground carrying the outlined tier's border colour, for a filled button that must still read as
   bounded on a same-toned surface. `'quiet'` is a de-emphasized tier:
   transparent background with a bordered, muted-text chrome; its text/border tokens are **not**
@@ -164,21 +138,12 @@ root (which never inherited the centring) disagreed with the `<button>` root acr
 - `formTarget?: string` (attribute `formtarget`) — overrides the form owner's `target`. Distinct
   from `target`, which is the anchor target used in link mode
 
-All five are `undefined`/`false` by default. When any of them — or `name`/`value` — is set, the
-submission runs through a **transient native `<button type="submit">`** inserted directly after the
-host, used as `requestSubmit()`'s submitter and removed again in the same synchronous step (in a
-`finally`, so a throwing or validation-blocked submission can't leave it behind). That is what makes
-the name/value pair reach the submitted `FormData` and the overrides reach the real submission:
-`requestSubmit()` only accepts a submitter the form actually owns, and a custom element is never
-one. While that stand-in exists it _is_ the form's submitter, so **`SubmitEvent.submitter` is the
-transient native button, not this host**. With none of those properties set, submission stays a
-plain `requestSubmit()` with a `null` submitter, and all of it is inert in link mode.
-For each string override, presence rather than truthiness chooses the transient path and its raw
-attribute is copied, so explicit empty values remain distinguishable from absence. Only the
-canonical native/upstream spellings are supported; the former hyphenated Lyra aliases were
-removed.
-
-Each size tier's `min-block-size` floor is exposed as its own token (see below).
+All five default to `undefined`/`false`. When one or `name`/`value` is set, the component inserts a
+transient native submit button after the host, passes it to `requestSubmit()`, and removes it in the
+same synchronous step even if submission fails. Its `name`/`value` reaches `FormData`, its `form*`
+overrides apply, and **`SubmitEvent.submitter` is that native button, not the host**. With none
+set, `requestSubmit()` has a `null` submitter. Presence, including an explicitly empty string,
+selects the transient path; string attributes are copied verbatim. Link mode ignores all of this.
 
 **Getters/methods:** `click()`, `focus(options?)`, and `blur()` — forwarded to the internal base
 element (the `<button>`, or the `<a>` in anchor mode); `click()` also runs the component's
@@ -189,9 +154,7 @@ consumer error and restores the current `required`/`value` constraint. `formStat
 restores `value` for session history/autofill without changing submitter-only form-data semantics.
 
 **Events:** a plain native `click` bubbles and composes through the shadow boundary unmodified
-(disabled while `disabled` or `loading`). In button mode, submit/reset runs only after that click's
-listener path has accepted the default action; calling `preventDefault()` on the host or an
-ancestor therefore vetoes it, while propagation control by itself does not. The internal button's
+(disabled while `disabled` or `loading`). The internal button's
 `focus` and `blur` — which do not
 cross the shadow boundary on their own — are re-dispatched from the host as bubbling, composed
 events. `lr-invalid` (no
@@ -220,9 +183,8 @@ set), `spinner` (present only while `loading`).
 **CSS custom states:** `disabled` (including fieldset-disablement and loading), `icon-button`
 (one text-free default-slot element), `link` (safe anchor mode), and `loading`.
 
-**Themeable custom properties.** The colour slots below are re-pointed at the active `variant`'s row
-of the library's shared semantic colour grid, so the component carries no `:host([variant='…'])`
-block of its own — the ones marked variant-independent are the exceptions:
+**Themeable custom properties.** Colour slots follow the active `variant`'s semantic colour row
+unless marked variant-independent:
 
 - `--lr-button-accent` (default `--lr-color-fill-loud`) — text/glyph colour for the chrome-less
   tiers (`outlined`, `plain`, `link`), i.e. the variant's loud fill borrowed as a foreground.
@@ -261,13 +223,9 @@ text/border counterparts, letting e.g. `appearance="quiet"` (which has its own r
 default**. Chromatic `plain` text moves toward body text during hover/press to retain contrast
 against the moving fill; the other appearances keep their resting text colour. The hover colour
 override also applies while pressed, and the border fallback remains the resting border colour.
-`appearance="link"` ignores `--lr-button-hover-color` (its own hover rule sets a higher-specificity
-colour mix) and renders with no border at any state, so `--lr-button-hover-border` has no visible
-effect there. **Breaking in 8.0.0:** this replaced `--lr-button-hover-brightness`,
-which no longer exists — a `filter: brightness()` multiplies every channel, so it moved a mid-toned
-fill but did nothing at all to a pure white or pure black one, and it dimmed the label and icons
-along with the box. Retuning `--lr-button-fill` or `--lr-button-accent-fill` now retunes that tier's
-hover and press with it.
+`appearance="link"` ignores `--lr-button-hover-color` and renders without a border, so
+`--lr-button-hover-border` has no effect there. Retuning either fill token also retunes its tier's
+hover and press. For removed historical tokens, see the [release history archive](https://github.com/aceshooting/lyra-ui/tree/main/docs/changelog).
 
 `--lr-button-width` (default `100%`) is the internal control's inline size, so it follows the host's
 own width; override it to `auto` for a compact inline composition. `--lr-button-active-scale`
@@ -279,11 +237,9 @@ the `loading` spinner's rotation period; that token itself collapses to `0.001ms
 The per-`size` `min-block-size` floors are `--lr-button-size-2xs`, `--lr-button-size-xs`,
 `--lr-button-size-s`, `--lr-button-size-m`, `--lr-button-size-l` and
 `--lr-button-size-xl`. Each defaults to the matching tier of the shared form-control ladder
-(`--lr-form-control-height-2xs` … `-xl`, i.e. 1.25rem, 1.5rem, 1.875rem, 2.5rem, 3rem, 3.5rem), so a
-button shares the same minimum-height ladder as sibling form controls rather than relying on a
-second hand-maintained list — which is exactly how the scales drifted apart before 8.0.0. This is
-density/floor parity, not guaranteed pixel-height parity: content and nested actions can make a
-composed control such as `lr-date-input` taller. Each token is read only by its own tier
+(`--lr-form-control-height-2xs` … `-xl`, i.e. 1.25rem, 1.5rem, 1.875rem, 2.5rem, 3rem, 3.5rem).
+These are minimum-height floors; content and nested actions can make a composed control taller.
+Each token is read only by its own tier
 (`--lr-button-size-s` also serves `size="small"`, and so on for the other two aliases), and all are
 ignored by `appearance="link"`.
 Retheming `--lr-theme-form-control-height-*` moves every control on the ladder together.
@@ -301,16 +257,14 @@ changes its private default to `--lr-radius-pill`. `--lr-button-caret-size` (def
 `var(--lr-size-0-75em)`) is the `with-caret`
 chevron's font size — declared in `em`, so it tracks every `size` tier through the button's own font
 size instead of needing a per-tier value.
-`--lr-button-shadow` is **undeclared by default**, so `box-shadow` falls back to `none` —
-byte-identical to before this property existed — set it to add a drop shadow (e.g. an
-elevated/floating action button) without a `::part(base)` rule. `appearance="link"` always renders
+`--lr-button-shadow` is **undeclared by default**, so `box-shadow` falls back to `none`; set it
+for a drop shadow without a `::part(base)` rule. `appearance="link"` always renders
 with no shadow regardless of this token — a zero-chrome inline link has no box to elevate.
 `--lr-button-justify` (default `center`) is the `justify-content` of the internal button's row. With
 the label no longer growing, this is what positions the icon+label pair inside a stretched control:
 `flex-start` packs it against the leading edge, `space-between` pushes the adornments apart.
-`--lr-button-label-grow` (default `0`) is the `flex-grow` of `[part="label"]`; `1` restores the
-pre-16.0.0 behaviour where the label absorbed every spare pixel of a stretched button, and it also
-overrides the automatic grow a `with-caret`/`end`-adornment button applies.
+`--lr-button-label-grow` (default `0`) is the `flex-grow` of `[part="label"]`; `1` fills spare
+space, and an explicit value overrides the grow applied by `with-caret`/`end` adornments.
 
 **Retuning one `size` tier's geometry, without a `::part(base)` rule.** Four more properties carry
 the active tier's geometry. Every `:host([size='…'])` rule changes only private defaults — no
@@ -376,10 +330,8 @@ box no matter what tier or override is in play.
 
 **Known gotchas:**
 
-- `accessibleLabel`/a host `aria-label` is forwarded reactively to the internal button or anchor as
-  a literal string (for an icon-only button). Host `aria-describedby` targets in the host's root
-  are resolved onto the focused internal control through `ariaDescribedByElements`; external
-  `aria-labelledby` is not copied across the shadow boundary.
+- Host `aria-describedby` targets resolve onto the focused internal control through
+  `ariaDescribedByElements`; external `aria-labelledby` is not copied across the shadow boundary.
 - For a toggle that owns its pressed state — a vetoable request, `lr-change`, and optional grouping
   behind one tab stop — use `lr-toggle` / `lr-toggle-group` rather than flipping host `aria-pressed`
   in a click handler.
@@ -387,13 +339,12 @@ box no matter what tier or override is in play.
   For toggle buttons, host `aria-pressed="true|false|mixed"` reaches the focused native button —
   BUTTONS only. A link button (`href` set) never receives it, because `role="link"` does not support
   `aria-pressed`; remove `href` and the same host attribute starts reaching the `<button>` that
-  replaces the anchor. That link carve-out arrived in **16.0.0** — before it, `aria-pressed` was
-  forwarded onto the anchor as well, asserting a state `role="link"` does not have. Navigation can
+  replaces the anchor. Navigation can
   use the global `aria-current="page|step|location|date|time|true|false"`, which does reach the
   anchor. Both states update reactively, including native `ariaPressed`/`ariaCurrent` property
   assignments, attribute removal and `href` changes. Empty or unsupported tokens are omitted. The native button/link role
   remains unchanged for an enabled control: use pressed state for button toggles and current state
-  for navigation links. A DISABLED link button drops `href` (so it genuinely cannot navigate) and
+  for navigation links. A disabled link button drops `href` and
   therefore also drops the anchor's implicit role, so it renders an explicit `role="link"` — without
   it, the forwarded `aria-label`/`aria-haspopup`/`aria-expanded`/`aria-current` would sit on a
   role-less generic element, which is prohibited.
@@ -406,12 +357,7 @@ box no matter what tier or override is in play.
 - Is form-associated (`static formAssociated = true` + `attachInternals()`), so it participates in
   an ancestor `<form>.elements` the same way `wa-button` does — a sibling text field's own
   Enter-to-submit lookup (which scans `form.elements` for a `type === 'submit'` control) finds it.
-- **`SubmitEvent.submitter` is not this element** whenever `name`/`value` or any `form*` override is
-  set: it is the transient native `<button>` described above. That native submitter remains
-  connected throughout synchronous `requestSubmit()` handling, so a `submit` listener can read
-  its `name`, `value` and `form*` fields and construct `FormData` with it. It is removed after
-  submission handling returns; its identity is distinct from the `lr-button` host.
-- The `form*` overrides and `type` are all inert while `href` renders the anchor — native navigation
-  is the activation there, and an anchor has no submit/reset concept.
+- A `submit` listener can read the transient native submitter's `name`, `value`, and `form*` fields
+  while it remains connected during synchronous `requestSubmit()` handling.
 
 ---

package/llms/components/lr-callout.md

@@ -7,7 +7,7 @@
 - **Family** `components/overlays/` — 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: [overlays](https://github.com/aceshooting/lyra-ui/blob/main/packages/lyra-ui/llms/overlays.md)
-- **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 this fallback property. The earlier accessible-label attribute deprecation has its own published release window; the programmatic property remains supported throughout its later window.
+- **Deprecations** none
 - **Optional peers** none
 - **Themeable via** 8 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`
@@ -40,8 +40,7 @@ property and rich-slot heading wrapper at that semantic level, invalid untyped v
 carries when it first mounts; see the announcement paragraph that closes this section),
 `open: boolean = true`
 (reflected as a presence attribute — `open="false"` is accepted in plain markup; `false` removes the
-semantic content and hides the host surface), and `accessibleLabel: string = ''` (property only;
-used only when the host has no `aria-label` attribute). In markup, name the callout with the host
+semantic content and hides the host surface). In markup, name the callout with the host
 `aria-label`, which has highest precedence by presence, including an explicitly empty value.
 
 Every reflected closed set normalizes identically from markup and untyped JavaScript writes:
@@ -132,7 +131,7 @@ any nested level. `display:none`/`content-visibility:hidden` prune a branch; a
 stay silent. Nested forwarding slots expose their flattened assigned text instead of fallback
 content, and later assignment plus assigned-node text/style/visibility mutations are observed.
 Mutations that leave that accessible text unchanged are deduplicated. A nonempty host
-`aria-label` (or `accessibleLabel` fallback) prefixes visible update text as context, with an
+`aria-label` prefixes visible update text as context, with an
 equality check preventing duplicate copy. The complete localized
 `calloutAnnouncementWithContext: '{context}: {content}'` message owns both fields, their order, and
 punctuation; override that key through `strings` rather than prejoining either field. An explicitly

package/llms/components/lr-carousel.md

@@ -7,7 +7,7 @@
 - **Family** `components/layout/` — see `llms/index.md` for its siblings
 - **Status** `stable` since `4.0.0` — see the maturity and deprecation policy in `llms/shared.md`
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [layout](https://github.com/aceshooting/lyra-ui/blob/main/packages/lyra-ui/llms/layout.md)
-- **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 this fallback property. The earlier accessible-label attribute deprecation has its own published release window; the programmatic property remains supported throughout its later window.
+- **Deprecations** none
 - **Optional peers** none
 - **Themeable via** 18 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`
@@ -62,10 +62,8 @@ slide itself; they do not change the active slide or move focus away from it.
   custom, shadow-wrapped, labelled, disabled, and editable controls retain their own pointer input.
 - `slides: number` (read-only) — live assigned-slide count, updated after dynamic child changes.
 - `aria-label` (host attribute) — names the carousel landmark, taking precedence by presence,
-  including an explicitly empty value.
-- `accessibleLabel?: string` (attribute: false) — fallback landmark name used while the host has no
-  `aria-label`. Omitting it reads back `undefined` and uses the localized `carouselLabel` default;
-  an explicitly empty value is used as-is.
+  including an explicitly empty value; when absent, the component uses the localized
+  `carouselLabel` default.
 
 **9.0 cleanup:** the redundant Lyra-only `index`, `showIndicators`, and `goTo()` aliases were
 removed. Use mapped `currentSlide`, `pagination`, and `goToSlide()`. The writable/reflected

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

@@ -63,8 +63,7 @@ after the write fulfills.
 
 **Events:** `lr-message-retry` (`detail: { messageId?: string }`; fired by the built-in retry button,
 only rendered when `status="failed"`). `lr-toggle-request` is cancelable and carries
-`{ expanded: boolean, collapsed: boolean }` (`ChatMessageToggleDetail`) — `expanded` is the
-proposed state; the deprecated `collapsed` key is its inverse and is removed in 23.0.0; preventing
+`{ expanded: boolean }` (`ChatMessageToggleDetail`) — `expanded` is the proposed state; preventing
 it vetoes the built-in collapse/expand transaction. `lr-toggle` carries that same detail after the
 accepted state is committed.
 

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

@@ -67,5 +67,5 @@ Selection is controlled: activation emits the complete claim but does not assign
 **Slots:** none. **Optional peer deps:** none.
 
 ```ts
-import "@aceshooting/lyra-ui/components/retrieval/claim-evidence/claim-evidence.js";
+import "@aceshooting/lyra-ui/components/lr-claim-evidence.js";
 ```

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

@@ -85,7 +85,7 @@ toggle, the loading-skeleton behavior while the fine-grained highlighter resolve
   If `languages` changes while highlighting is loading, only results for the current map can update
   the displayed code. For a
   TypeScript annotation, use `import type { ShikiLanguageSource } from
-'@aceshooting/lyra-ui/components/conversation/code-block/code-block-core.js'`; the type-only
+'@aceshooting/lyra-ui/components/lr-code-block-core.js'`; the type-only
   granular import emits no registration side effect.
 - `copyAppearance: 'text' | 'icon' = 'text'` (attribute `copy-appearance`, reflected) — identical to
   `<lr-code-block>`'s own property: `'text'` is the labelled button, `'icon'` swaps the visible label
@@ -138,7 +138,7 @@ constant also avoids repeated component snapshots.
 ```ts
 import { html } from "lit";
 import jsonGrammar from "shiki/langs/json.mjs";
-import "@aceshooting/lyra-ui/components/conversation/code-block/code-block-core.js";
+import "@aceshooting/lyra-ui/components/lr-code-block-core.js";
 
 const languages = { json: jsonGrammar };
 const view = html`<lr-code-block-core

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

@@ -83,7 +83,7 @@ highlighted markup.
   for that language — an additive, opt-in escape hatch for a build scoped to just the languages a
   consumer actually needs. A `language` absent from this map (or `languages` left unset) falls back
   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'`;
+  `import type { ShikiLanguageInput } from '@aceshooting/lyra-ui/components/lr-code-block.js'`;
   the type-only granular import emits no registration side effect.
   The map key need not be the grammar module's own registered name or one of its declared
   aliases — Lyra derives the Shiki `langAlias` mapping this needs automatically, so a key such as
@@ -104,10 +104,9 @@ when the anchor isn't a `line-range`, the id isn't found, or the start line is o
 was written successfully), `lr-error` (`detail: null` — generic notification when clipboard writing
 fails), `lr-copy-error` (frozen `detail: { ok: false, text, reason, error }`, where `reason` is
 `'unsupported' | 'denied' | 'failed'`), `lr-toggle-request` (cancelable;
-`detail: { expanded, collapsed }` is the proposed next state —
-`expanded` is the canonical key, the deprecated `collapsed` key is its inverse and is removed in
-23.0.0 — and canceling leaves `collapsed` unchanged), `lr-toggle` (`detail: { expanded: boolean,
-collapsed: boolean }` — the committed state after the request is accepted),
+`detail: { expanded }` is the proposed next state; canceling leaves the host `collapsed` property
+unchanged),
+`lr-toggle` (`detail: { expanded: boolean }` — the committed state after the request is accepted),
 `lr-line-activate` (`detail: { line: number }` — a gutter line number was activated while
 `activatableLines` is set),
 `lr-text-select` (`detail: { text, anchor, rects }` — a text selection inside the code body ended;
@@ -205,7 +204,7 @@ highlighting.
 
 ```ts
 import { html } from "lit";
-import "@aceshooting/lyra-ui/components/conversation/code-block/code-block.js";
+import "@aceshooting/lyra-ui/components/lr-code-block.js";
 
 const view = html`<lr-code-block
   language="typescript"

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

@@ -317,7 +317,7 @@ of authoring `positioning-strategy`/`hoist` on each instance.
   swatches="#e11d48;#2563eb;#16a34a"
 ></lr-color-picker>
 <script type="module">
-  import "@aceshooting/lyra-ui/components/forms/color-picker/color-picker.js";
+  import "@aceshooting/lyra-ui/components/lr-color-picker.js";
   const picker = document.querySelector("lr-color-picker");
   // Objects give each entry a real accessible name:
   picker.swatches = [

package/llms/components/lr-combobox.md

@@ -7,7 +7,7 @@
 - **Family** `components/forms/` — 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: [forms](https://github.com/aceshooting/lyra-ui/blob/main/packages/lyra-ui/llms/forms.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.
+- **Deprecations** none
 - **Optional peers** none
 - **Themeable via** 34 parts, 36 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Documented with** `lr-option` (same section below)
@@ -70,7 +70,7 @@ focus explicitly — the browser does not replay the focus event after custom-el
   input.addEventListener("focus", async () => {
     if (!combobox.hidden) return;
     registration ??= import(
-      "@aceshooting/lyra-ui/components/forms/combobox/combobox.js"
+      "@aceshooting/lyra-ui/components/lr-combobox.js"
     ).catch((error) => {
       registration = undefined; // let a later interaction retry
       throw error;
@@ -416,16 +416,13 @@ async `source` call plus the exact query string that call was made with (the rej
 query, not necessarily the live `query`/`inputValue`, which may have moved on — or been cleared by
 closing the listbox — by the time the rejection settles). The rendered copy stays localized and
 never shows the raw error.
-`lr-retry-request` and `lr-retry` are cancelable; the built-in failed-load action calls `refresh()`, and `preventDefault()`
+`lr-retry-request` is cancelable; the built-in failed-load action calls `refresh()`, and `preventDefault()`
 leaves the failure on screen. While the failure state is the only popup content, the popup swaps
 `role="listbox"` for `role="dialog"` (the input gains the matching `aria-haspopup="dialog"` and
 drops `aria-activedescendant`, and the popup carries the localized failure heading as its accessible
 name). `dialog` is one of the four popup roles WAI-ARIA lets a `role="combobox"` own, so the still
 expanded `aria-controls` target keeps a valid owner while holding a retry `button` that is not a
 legal listbox child. A successful retry restores `role="listbox"`.
-`lr-retry` is the deprecated cancelable alias, dispatched after `lr-retry-request` with the same
-null detail. Either event can veto the built-in refresh; subscribe to one spelling. Removal of the
-alias is not before 24.0.0.
 
 **The clear button covers two axes, and announces only the one that moved.** A combobox owns both a
 committed selection and an in-progress filter query, so the button renders whenever either has
@@ -732,3 +729,5 @@ synchronous and fires no `input`/`change`/`lr-change` event.
 - `part="tag-label"` — The selected-tag label. Kept on one line and truncated with an ellipsis at `--tag-max-size` (default `var(--lr-size-5rem)`), rather than wrapped. Note that `lr-select`'s tag of the same name defaults to `var(--lr-size-12rem)`, so the same `--tag-max-size` value yields a wider tag there.
 
 ---
+
+<a id="popup-select-keyboard"></a>

package/llms/components/lr-compare-panel.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-vote` since `22.0.0`; use event `addEventListener('lr-vote-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** 9 parts, 5 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,11 +42,9 @@ scroll position. `disabled: boolean = false` (reflected) disables every vote but
 **Slots:** `a` (the first output — any content, a chat message, markdown, a viewer), `b` (the second
 output), and `prompt` (optional shared-input header above both panes).
 
-**Events:** `lr-vote-request` and `lr-vote` — `detail: { choice: 'a' | 'b' | 'tie' | 'both-bad'; itemId: string }`.
+**Events:** `lr-vote-request` — `detail: { choice: 'a' | 'b' | 'tie' | 'both-bad'; itemId: string }`.
 This is a cancelable veto point emitted before `vote` changes; call `preventDefault()` to preserve
 the prior vote.
-`lr-vote` is the deprecated cancelable alias, dispatched after `lr-vote-request` with the same
-detail. Either event can veto the vote change; subscribe to one spelling, not both.
 
 
 **CSS parts:** `base` (the outer wrapper), `prompt` (the optional prompt header, hidden when the

package/llms/components/lr-confirm-bar.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** 19 parts, 5 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`
@@ -107,13 +106,10 @@ deliberately *not* affected: while a decision is awaiting resolution, focus stil
 **Slots:** default — supplementary body content between the heading and the actions (e.g. a
 `lr-diff-view`). `footer` — extra content at the start of the action row.
 
-**Events:** `lr-approve-request` and `lr-approve` (`detail: { args, waitUntil }` — `args` is the `args` prop as-is, matching
-`lr-tool-approval-dialog`'s own `args` detail; cancelable), `lr-deny-request` and `lr-deny` (`detail: { waitUntil }`, the
+**Events:** `lr-approve-request` (`detail: { args, waitUntil }` — `args` is the `args` prop as-is, matching
+`lr-tool-approval-dialog`'s own `args` detail; cancelable), `lr-deny-request` (`detail: { waitUntil }`, the
 same resolver and no denial data of its own; cancelable), `lr-decision-settled`
 (`detail: { decision }`; non-cancelable).
-`lr-approve` and `lr-deny` are deprecated cancelable aliases of their respective requests. Each
-follows its request with the same detail, including `waitUntil`; either spelling can veto.
-Subscribe to one spelling per action to avoid handling the same proposal twice.
 
 `waitUntil(promise: Promise<unknown>) => void` is ExtendableEvent-style. Calling it from the
 listener holds the bar in its `pendingAction` presentation — `loading` on the activated control,

package/llms/components/lr-context-inspector.md

@@ -49,8 +49,9 @@ end: number; reason?: string }` marks character ranges within `text` that are re
 **Events:** `lr-citation-activate` (`detail: { sourceId: string; index: number }`, surfaced by a
 segment's embedded `lr-citation-badge`), `lr-citation-open` (`detail: { sourceId: string; index:
 number; href?: string }`, the "full preview" signal), `lr-copy` (`detail: { ok: true; text: string }`, from the
-embedded `lr-copy-button`), `lr-export` (`detail: { format: string }`, from the embedded
-`lr-export-button`), `lr-export-complete` (`detail: { format: string }`, after a non-cancelled export
+embedded `lr-copy-button`), cancelable `lr-export-request` (`detail: { format: string }`, surfaced by
+the embedded `lr-export-button`; call `preventDefault()` to handle the request without its built-in
+download), `lr-export-complete` (`detail: { format: 'csv' | 'json' }`, after a non-cancelled export
 finishes), `lr-error` (the embedded clipboard write failed), `lr-copy-error` (`detail: { ok: false;
 text: string; reason: string; error: unknown }`, the detailed clipboard failure),
 `lr-toolbar-actions-change` (no detail, surfaced unchanged when the embedded copy button's logical

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

@@ -31,8 +31,8 @@ The menu content is exactly what `lr-dropdown` takes, so every row type composes
 
 ```html
 <script type="module">
-  import '@aceshooting/lyra-ui/components/overlays/context-menu/context-menu.js';
-  import '@aceshooting/lyra-ui/components/layout/menu/menu-label.js';
+  import '@aceshooting/lyra-ui/components/lr-context-menu.js';
+  import '@aceshooting/lyra-ui/components/lr-menu-label.js';
 </script>
 
 <lr-context-menu label="File actions">

package/llms/components/lr-context-meter.md

@@ -7,7 +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 event** `lr-segment-activate` since `22.0.0`; use event `addEventListener('lr-segment-activate-request', event => { /* Call preventDefault() to veto the proposed selection toggle. */ })`; 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`
@@ -87,9 +87,7 @@ library event. **Cancelable, and a real veto point**: the default action is this
 `index` in its own `selectedIndices`, so `preventDefault()` keeps the current selection and hands
 that state entirely to the consumer. Never emitted in the default presentational mode. Because the
 event dispatches synchronously *before* the write, a listener reading `selectedIndices` inside its
-own handler sees the pre-activation value. The deprecated cancelable `lr-segment-activate` alias fires
-after the request and before that write, with the same detail. Either event can veto; vetoing only
-the legacy alias issues a development warning. Reentrant activation during dispatch is ignored.
+own handler sees the pre-activation value. Reentrant activation during dispatch is ignored.
 Replacing the segment collection, disabling interaction, or disconnecting during dispatch cancels
 the default write.
 

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

@@ -138,7 +138,7 @@ for an application-level fallback:
   value="npm install @aceshooting/lyra-ui"
 ></lr-copy-button>
 <script type="module">
-  import "@aceshooting/lyra-ui/components/utility/copy-button/copy-button.js";
+  import "@aceshooting/lyra-ui/components/lr-copy-button.js";
 
   const button = document.getElementById("copy");
   button.addEventListener("lr-copy", (event) =>

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

@@ -7,7 +7,7 @@
 - **Family** `components/data/` — see `llms/index.md` for its siblings
 - **Status** `experimental` 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 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.
+- **Deprecations** none
 - **Optional peers** none
 - **Themeable via** 59 parts, 28 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`
@@ -27,7 +27,7 @@ shadow root, runs that control without also emitting `lr-cell-click`. Passive ce
 to activate the cell.
 
 ```js
-import "@aceshooting/lyra-ui/components/data/data-grid/data-grid.js";
+import "@aceshooting/lyra-ui/components/lr-data-grid.js";
 ```
 
 Give the grid an accessible name with `label` or a host `aria-label`; the host attribute wins.
@@ -216,17 +216,14 @@ 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); `lr-data-error` does NOT itself set the built-in
-`error` state (see `error` above); `lr-retry-request` and `lr-retry` (`detail: null`, cancelable) — the built-in
+`error` state (see `error` above); `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. Every library event bubbles and is
-composed; only `lr-cell-contextmenu`, `lr-sort-request`, `lr-retry-request`, and `lr-retry` are cancelable. Structured
+composed; only `lr-cell-contextmenu`, `lr-sort-request`, and `lr-retry-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.
-`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.
 
 **Row context menus with `lr-context-menu`.** Wrap the grid in an `lr-context-menu` region and
 leave `lr-cell-contextmenu` **un-prevented**: preventing it suppresses the native menu, and the

package/llms/components/lr-details.md

@@ -149,9 +149,9 @@ invariant.
 
 The Details events `lr-show` and `lr-hide` have no detail payload and are cancelable; preventing
 either leaves the panel in its previous state. Accepted changes emit `lr-toggle` with
-`detail: { expanded, open, source }` (`expanded` is the new state; the deprecated `open` key, removed
-in 23.0.0, carries the same value), then the non-cancelable `lr-after-show` or `lr-after-hide` once
-rendering and motion settle. `source` is `user` for a summary click or keyboard activation,
+`detail: { expanded, source }` (`expanded` is the new state), then the non-cancelable
+`lr-after-show` or `lr-after-hide` once rendering and motion settle. `source` is `user` for a
+summary click or keyboard activation,
 `programmatic` for `show()`, `hide()`, or assigning `open`, and `peer` when another Details with
 the same non-empty `name` closes this one. The full orders are `lr-show` → `lr-toggle` →
 `lr-after-show` and `lr-hide` → `lr-toggle` → `lr-after-hide`. Initially open markup emits