@aceshooting/lyra-ui 23.0.0 → 24.1.0

package/llms/components/lr-dialog.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** 15 parts, 21 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`
@@ -44,8 +44,6 @@ read, and neither is deprecated.
   the generated visible title (string property or rich `label` slot) at that semantic level;
   invalid untyped values retain level 3, while `none` keeps visual title text without heading
   semantics. A direct light-DOM heading retains its own native/ARIA level.
-- `accessibleLabel: string = ''` (property only) — explicit accessible-only name; unlike `label`,
-  it never renders visible text. In markup, use the host `aria-label`.
 - `heading?: string` — legacy visible-title fallback, after the `label` slot and `label` property;
   it has no effect when a direct light-DOM heading already supplies custom chrome
 - `withoutCloseButton: boolean = false` (attribute `without-close-button`, reflected) — removes the
@@ -274,7 +272,7 @@ from).
   </div>
 </lr-dialog>
 <script type="module">
-  import "@aceshooting/lyra-ui/components/overlays/dialog/dialog.js";
+  import "@aceshooting/lyra-ui/components/lr-dialog.js";
 
   const dlg = document.getElementById("dlg");
   // Listeners first: `lr-show` is emitted synchronously inside show().
@@ -312,8 +310,8 @@ A dialog with no chrome of Lyra's own, animating faster and blurring the page be
 ```
 
 Accessible naming and visible title are separate. Naming precedence is: (1) host `aria-label`, by
-attribute presence including an explicitly empty value, (2) `accessibleLabel`, (3) the copied text
-of an unslotted direct light-DOM heading, then (4) the shadow-owned visible title wrapper.
+attribute presence including an explicitly empty value, (2) the copied text of an unslotted direct
+light-DOM heading, then (3) the shadow-owned visible title wrapper.
 Visible-title precedence is the rich `label` slot, then the mapped `label` property, then legacy
 `heading`. The direct-heading case copies text because an IDREF cannot cross from the panel's shadow
 tree to a light-DOM heading; the mapped title wrapper can use `aria-labelledby` because it lives in

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

@@ -53,8 +53,7 @@ renders at the `280px` default, and `event.detail.size` reads `undefined`.
 
 **Exported types:** `LyraDockPanelEdge = 'start' | 'end' | 'top' | 'bottom'`, readonly
 `LyraDockPanelResizeDetail = { extent: string }`, readonly
-`LyraDockPanelCollapseChangeDetail = { expanded: boolean, collapsed: boolean }` (the `collapsed`
-key remains emitted but is deprecated; use its inverse, `expanded`), and `LyraDockPanelEventMap`.
+`LyraDockPanelCollapseChangeDetail = { expanded: boolean }`, and `LyraDockPanelEventMap`.
 The former dock-specific `parseLengthPx()` export is removed; dock length resolution is now a
 private adapter over the library's canonical CSS-length resolver, with container/viewport units
 resolved in the host's owner realm.
@@ -74,10 +73,10 @@ resolved in the host's owner realm.
   after each genuine keyboard step whose own `lr-resize-request` was not prevented. `pointercancel`,
   lost capture, disconnect/adoption, live policy/geometry mutation, no-op attempts, and a prevented
   `lr-resize-request` all emit nothing.
-- `lr-collapse-request` (cancelable; `detail: { expanded, collapsed }` is the state proposed by the
-  built-in collapse toggle — `expanded` is the proposed state and the deprecated `collapsed` key its
-  inverse. Call `preventDefault()` to leave `collapsed` unchanged. Not fired when a consumer assigns
-  `collapsed` directly), `lr-collapse-change` (non-cancelable; `detail: { expanded, collapsed }` is
+- `lr-collapse-request` (cancelable; `detail: { expanded }` is the state proposed by the
+  built-in collapse toggle. Call `preventDefault()` to leave the host `collapsed` property
+  unchanged. Not fired when a consumer assigns `collapsed` directly), `lr-collapse-change`
+  (non-cancelable; `detail: { expanded }` is
   the accepted built-in-toggle state. Not fired when a consumer assigns `collapsed` directly). Both
   details are fresh readonly/frozen snapshots.
 

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

@@ -7,7 +7,7 @@
 - **Family** `components/data/` — 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: [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** 21 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`
@@ -62,12 +62,10 @@ the nested table.
 - `lr-sort` — non-cancelable; an accepted sort commits the same fields with `phase: 'commit'`.
 - `lr-selection-change` — non-cancelable; fresh frozen readonly `{ documentIds }`.
 - `lr-open` — non-cancelable; frozen readonly `{ documentId }`.
-- `lr-retry-request` and `lr-retry` — cancelable, `detail: null`; the nested table's built-in retry
-  button was activated, only rendered while `error` is set. The library contains the child's request
-  and compatibility alias, then emits its own canonical `lr-retry-request` followed by the deprecated
-  `lr-retry` alias. Preventing either parent event leaves both library and table errors set;
-  otherwise the default clears them. Subscribe to one spelling. The alias is a veto point, not a
-  completion notification, and its removal is not before 24.0.0.
+- `lr-retry-request` — cancelable, `detail: null`; the nested table's built-in retry button was
+  activated, only rendered while `error` is set. The library contains the child's request, then
+  emits its own canonical request. Preventing it leaves both library and table errors set; otherwise
+  the default clears them.
 
 **Slots:** `error` — replaces the nested table's built-in failed-load state, including its retry
 button, while `error` is set.

package/llms/components/lr-drawer.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** 15 parts, 26 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`
@@ -34,7 +34,7 @@ the slide animation are its own.
 - `contained: boolean = false` (attribute `contained`, reflected) — position within the nearest
   containing block without a backdrop, page inerting, focus trap, scroll lock, top-layer
   promotion, or global Escape ownership
-- `heading?: string`, `label: string`, `accessibleLabel: string = ''` (property only),
+- `heading?: string`, `label: string`,
   `withoutCloseButton: boolean = false` (attribute `without-close-button`, reflected),
   `noHeader: boolean = false` (attribute `no-header`, Shoelace's spelling, reflected),
   `withoutHeader: boolean = false` (attribute `without-header`, Web Awesome's spelling, reflected;
@@ -42,7 +42,7 @@ the slide animation are its own.
   hint), and `lightDismiss: boolean = false` (attribute `light-dismiss`) — inherited dialog naming,
   chrome and dismissal options. A plain `aria-label` attribute on the host names the panel, inherited
   unchanged from `lr-dialog`: it is the strongest naming override, by attribute presence including
-  an explicitly empty value, ahead of `accessibleLabel` and any slotted heading.
+  an explicitly empty value, ahead of any slotted heading.
 - `headingLevel: LyraHeadingLevel = '3'` (attribute `heading-level`, reflected) — semantic level of
   the generated title, from `1` through `6`, or `none` for visual-only title text. A direct slotted
   heading retains its own native level.

package/llms/components/lr-dropdown.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** `arrow` / `arrow` since `22.0.0`; use property `Set withoutArrow to the inverse of arrow; use without-arrow to preserve the former arrow-free default.`; removal not before `24.0.0` — The shared negative arrow switch resolves conflicting arrow inputs and defaults to false. The retained positive alias has the inverse value and remains functional throughout the compatibility window.
+- **Deprecations** none
 - **Optional peers** none
 - **Themeable via** 13 parts, 11 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`
@@ -101,10 +101,9 @@ its surface.
 - `containingElement?: HTMLElement` (property only) — an external element that counts as inside for
   light-dismiss handling.
 - `withoutArrow: boolean = false` (attribute `without-arrow`, reflected) — suppresses the
-  pointer. `arrow: boolean = true` remains its deprecated inverse alias (removal not before
-  24.0.0). Set `without-arrow` to preserve the previous omitted-arrow appearance.
-- `arrowPlacement`, `arrowPadding`, and `accessibleLabel` (`aria-label`) are retained from
-  `lr-popover` for existing Lyra consumers.
+  pointer. Set `without-arrow` to preserve the previous omitted-arrow appearance.
+- `arrowPlacement`, `arrowPadding`, and `accessibleLabel` (`aria-label`) are inherited from
+  `lr-popover`.
 - `popupRole: 'menu'` (attribute `popup-role`) is the narrowed inherited surface. Dropdowns cannot
   be changed into dialogs; use `lr-popover popup-role="dialog"` for arbitrary dialog-like content.
 

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

@@ -7,7 +7,7 @@
 - **Family** `components/agent-tools/` — see `llms/index.md` for its siblings
 - **Status** `stable` since `9.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-example-tool-approval-decide` since `22.0.0`; use event `addEventListener('lr-example-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** `dompurify`, `katex`, `marked`, `shiki` — see `llms/peers.md`
 - **Themeable via** 25 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`
@@ -54,7 +54,7 @@ active? }`. `label` and `variant` customize application-defined lifecycle displa
 **Events:** `lr-example-toggle` (`detail: EvalExampleToggleDetail` = `{ exampleId: string; expanded:
 boolean }`), `lr-example-citation-select` (`detail: EvalCitationSelectDetail` = `{ exampleId:
 string; citation: Citation }` — the nested `lr-grounding-summary`'s own `{ citation }` correlated
-with the example it came from, so a host needn't walk the DOM), `lr-example-tool-approval-decide-request` and `lr-example-tool-approval-decide`
+with the example it came from, so a host needn't walk the DOM), `lr-example-tool-approval-decide-request`
 (`detail: EvalToolApprovalDetail` = `ToolTimelineApprovalDetail & { exampleId: string }` =
 `{ invocationId: string; approved: boolean; args?: unknown; sourceKey?: string; exampleId: string
 }`). The approval
@@ -64,9 +64,7 @@ host resolves asynchronous validation. The component also contains and correlate
 child events as `lr-example-claim-select` (`{ exampleId, claim }`),
 `lr-example-tool-activate` (`{ exampleId, invocationId, sourceKey? }`), and
 `lr-example-tool-render-error` (`{ exampleId, invocationId, sourceKey?, toolName, error }`).
-`lr-example-tool-approval-decide` is the deprecated cancelable alias, dispatched after its request
-with the same correlated detail. Preventing either spelling propagates the nested approval veto;
-subscribe to one spelling.
+The cancelable `lr-example-tool-approval-decide-request` propagates its veto to the nested approval.
 
 
 **CSS parts:** `base`, `header`,

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

@@ -7,7 +7,7 @@
 - **Family** `components/utility/` — 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: [utility](https://github.com/aceshooting/lyra-ui/blob/main/packages/lyra-ui/llms/utility.md)
-- **Deprecated event** `lr-export` since `22.0.0`; use event `addEventListener('lr-export-request', event => { /* Review the request detail and call preventDefault() to veto. */ })`; removal not before `24.0.0` — The request event identifies the veto phase; the legacy event preserves its equal detail and cancellation behavior.
+- **Deprecations** none
 - **Optional peers** none
 - **Themeable via** 6 parts, 16 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`
@@ -79,7 +79,7 @@ extension?: string }`. Descriptor labels/descriptions are consumer-supplied, alr
 
 **Methods:** `focus(options?)`, `blur()`, and `click()` forward to the native trigger button.
 
-**Events:** `lr-export-request` and `lr-export` (`detail: { format: string }`, **cancelable** — call `preventDefault()` to
+**Events:** `lr-export-request` (`detail: { format: string }`, **cancelable** — call `preventDefault()` to
 substitute your own server-generated download instead of the built-in client-side one; the rows a
 non-prevented built-in download serializes are read **after** this dispatch, so `.rows` assigned from
 inside the listener still reaches it, and `getRows` is consulted at the same point),
@@ -90,9 +90,6 @@ also shown via the trigger's `trigger-error` part and announced through the shar
 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).
-`lr-export` is the deprecated cancelable alias, dispatched after `lr-export-request` with equal
-detail. Either event can veto the export; subscribe to one spelling. Removal of the alias is not
-before 24.0.0.
 
 **Slots:** none.
 
@@ -140,7 +137,7 @@ change every unset export button beneath it.
     { key: "value", label: "Value" },
   ];
   exp.formats = ["csv", "json"]; // shows a format-choice menu instead of exporting immediately
-  exp.addEventListener("lr-export", (e) =>
+  exp.addEventListener("lr-export-request", (e) =>
     console.log("exporting", e.detail.format)
   );
 
@@ -154,7 +151,7 @@ change every unset export button beneath it.
       extension: "xlsx",
     },
   ];
-  exp.addEventListener("lr-export", async (e) => {
+  exp.addEventListener("lr-export-request", async (e) => {
     if (e.detail.format !== "xlsx") return;
     e.preventDefault();
     exp.loading = true;

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

@@ -9,7 +9,6 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [media](https://github.com/aceshooting/lyra-ui/blob/main/packages/lyra-ui/llms/media.md)
 - **Deprecated part** `base` since `8.2.3`; use part `::part(file-input)`; removal not before `10.0.0` — The file-input part names the interactive picker surface; base remains on that same node during the compatibility window. That version is a policy floor, not a plan: `wa-file-input` still publishes its own deprecated `base` part, so this alias is removed only when upstream's is.
 - **Deprecated part** `label` since `8.2.3`; use part `::part(form-control-label)`; removal not before `10.0.0` — The form-control-label part follows the shared form-control vocabulary; label remains on that same node during the compatibility window. That version is a policy floor, not a plan: `wa-file-input` still publishes its own deprecated `label` part, so this alias is removed only when upstream's is.
-- **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.
 - **Optional peers** none
 - **Themeable via** 22 parts, 21 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`
@@ -132,10 +131,6 @@ enabled buttons retain pointer feedback.
 - `validationTarget: HTMLElement | undefined` — the focusable base of the dropzone control after
   first render. Assign another shadow descendant to override where native constraint-validation UI
   is anchored; assign `undefined` to restore the default focusable base
-- `accessibleLabel: string = ''` (property only, deprecated; removal not before 24.0.0) — accessible name forwarded to the semantic
-  dropzone and native file input, without changing visible copy. A host `aria-label` wins over it.
-  When neither is set, the form label (`label` or the `label` slot) names the dropzone, then the
-  localized instruction. In markup, name the dropzone with the host `aria-label`.
 - `acceptedMessage?: string` (attribute `accepted-message`) — live-region message after an
   accepted selection; `{count}` is replaced with the accepted count. Absence uses the localized
   singular/plural `fileInputAcceptedOne`/`fileInputAcceptedMany` default. Every explicit string,

package/llms/components/lr-funnel.md

@@ -78,7 +78,7 @@ shown when `stages` exceeds the 500-stage render ceiling)
 
 ```html
 <script type="module">
-  import '@aceshooting/lyra-ui/components/data/funnel/funnel.js';
+  import '@aceshooting/lyra-ui/components/lr-funnel.js';
 </script>
 
 <lr-funnel id="signup" label="Self-serve signup" share-precision="1"></lr-funnel>

package/llms/components/lr-graph.md

@@ -7,8 +7,7 @@
 - **Family** `components/retrieval/` — 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: [retrieval](https://github.com/aceshooting/lyra-ui/blob/main/packages/lyra-ui/llms/retrieval.md)
-- **Deprecated event** `lr-link-click` since `22.0.0`; use event `lr-edge-activate`; removal not before `24.0.0` — Activation covers pointer and keyboard gestures. The old event remains available with its original detail; edge activation names its optional identifier edgeId.
-- **Deprecated event** `lr-node-click` since `22.0.0`; use event `lr-node-activate`; removal not before `24.0.0` — Activation covers pointer and keyboard gestures. The old event remains available with its original detail; edge activation names its optional identifier edgeId.
+- **Deprecations** none
 - **Optional peers** `d3-drag`, `d3-force`, `d3-selection`, `d3-zoom` — see `llms/peers.md`
 - **Themeable via** 19 parts, 17 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`
@@ -153,10 +152,7 @@ edgeId? }`; the optional `edgeId` is the stable `LyraGraphEdge.id` supplied by t
 Enter/Space activations within 500ms — regardless of `LyraGraphNode.expandable`), `lr-community-activate`
 (`detail: { communityId }`, a hull was activated by pointer or keyboard), `lr-selection-change`
 (`detail: { selectedNodeIds, selectedEdgeIds }`, a controlled selection intent), and `lr-viewport-change`
-(`detail: { k, x, y }`, a frame-coalesced camera/layout signal). Deprecated aliases, each fired
-right after its canonical event: `lr-node-click` (use `lr-node-activate`, equal detail),
-`lr-link-click` (use `lr-edge-activate`, renaming detail.linkId to detail.edgeId); these aliases
-remain through v23.
+(`detail: { k, x, y }`, a frame-coalesced camera/layout signal).
 
 **Slots:** none.
 
@@ -217,7 +213,7 @@ localized `part="error"` alert. Install with
 ```html
 <lr-graph style="display:block;height:500px"></lr-graph>
 <script type="module">
-  import "@aceshooting/lyra-ui/components/retrieval/graph/graph.js";
+  import "@aceshooting/lyra-ui/components/lr-graph.js";
 
   const g = document.querySelector("lr-graph");
   g.nodes = [

package/llms/components/lr-icon.md

@@ -130,7 +130,7 @@ fetch allowlist, the response is still byte-capped, and the markup is still sani
 cannot widen what an icon is allowed to render.
 
 ```ts
-import "@aceshooting/lyra-ui/components/utility/icon/icon.js"; // registers <lr-icon>
+import "@aceshooting/lyra-ui/components/lr-icon.js"; // registers <lr-icon>
 import {
   registerIconLibrary,
   unregisterIconLibrary,

package/llms/components/lr-include.md

@@ -121,7 +121,7 @@ retried; a stale response never paints over a newer `src`.
   Loading navigation…
 </lr-include>
 <script type="module">
-  import "@aceshooting/lyra-ui/components/viewers/include/include.js";
+  import "@aceshooting/lyra-ui/components/lr-include.js";
 
   const include = document.querySelector("#navigation");
   include.addEventListener("lr-include-error", (event) => {

package/llms/components/lr-input.md

@@ -21,23 +21,15 @@ form-associated via the same `FormAssociated` mixin as `lr-textarea`. Ships the
 `label`/`hint`/`errorText` form-control chrome as `lr-textarea`/`lr-select`, and the same
 `size` scale as `lr-select`/`lr-combobox`.
 
-`stepUp()` and `stepDown()` use the current `value`, `step`, `min`, and `max` properties in the same
-synchronous call, including changes made immediately beforehand. They preserve native step alignment
-and bounds, update form submission silently, and remain no-ops before the native input has rendered
-or while disabled/readonly. Native `step="any"` remains a non-steppable no-op.
-
-Removing `label`, `hint`, `help-text`, or `error-text` safely omits that content while retaining
-native `null` property readback. Explicit empty strings remain empty and later supplied text renders
-normally. The same inherited behavior applies to `lr-number-input` and `lr-native-time-input`.
+Removing `label`, `hint`, `help-text`, or `error-text` omits that content while retaining native
+`null` property readback. Explicit empty strings remain empty. `lr-number-input` and
+`lr-native-time-input` inherit this behavior.
 
 Changing own `disabled` from true to false in the same task that disables an ancestor fieldset keeps
 the native editing control effectively disabled. The enabled first-legend exception and explicit
 own-disabled state retain their native meaning; validity and form submission follow the effective
 disabled state.
 
-Pressing Enter submits the ancestor `<form>` — the implicit submission a native `<input>` performs;
-see "Enter-to-submit" below for the exact rules and for which controls deliberately opt out.
-
 Public `--lr-input-*` theme inputs stay undeclared on the host, so an ancestor theme wrapper can
 override size, appearance, and pill fallbacks; a value set directly on the element still wins.
 When a clear or password action is present, `2xs` through `m` grow only enough to contain its
@@ -65,12 +57,9 @@ shared hit target (42px including the row border at the default theme); `l` and
 - `value: string = ''` (from `FormAssociated`)
 - `defaultValue: string = ''` — reset value, backed by the standard `value` content attribute;
   `default-value` is accepted as a Shoelace attribute alias
-- `name: string` (from `FormAssociated`) and the plain inherited `id` are both forwarded to the
-  internal native `<input>` (previously the internal input carried neither, only a fixed
-  `id="input"`), so shadow-DOM-aware password managers that key field detection off the actual
-  control's own `name`/`id` — not `autocomplete` alone — recognize `<lr-input>` fields. The
-  internal `<label for>` tracks whichever id is in use. Leaving `id` unset on the host keeps the
-  internal input at `id="input"`, identical to before
+- `name: string` (from `FormAssociated`) and inherited `id` are forwarded to the native input for
+  password-manager field detection. The internal `<label for>` tracks that id; without a host `id`,
+  the input uses `id="input"`
 - `placeholder: string = ''`
 - `clearable: boolean = false` (reflected) — shows a localized clear action while a `text` or
   `search` input has a value; clearing preserves input focus
@@ -89,7 +78,7 @@ shared hit target (42px including the row border at the default theme); `l` and
 - `title: string = ''` — forwarded to the native input
 - `spellcheck: boolean = true` — forwarded to the native input, including `spellcheck="false"`
 - `autocapitalize: string = ''` / `autocorrect` (read: `boolean = true`; write:
-  `boolean | 'off' | 'on'`; attribute values `on`/`off`)
+  `boolean | 'off' | 'on'`; markup `autocorrect="on"`/`autocorrect="off"`)
 - `inputMode: string = ''` (attribute `inputmode`) / `enterKeyHint: string = ''` (attribute
   `enterkeyhint`) — `autocapitalize`, `inputMode`, and `enterKeyHint` are forwarded verbatim to the
   native input and an empty string omits them; `autocorrect` is normalized to canonical `on`/`off`
@@ -97,11 +86,6 @@ shared hit target (42px including the row border at the default theme); `l` and
   native properties; `autocorrect` reads as boolean while accepting both Web Awesome's boolean
   writes and Shoelace's `'off'`/`'on'` writes
 
-**8.0 migration:** the former camel-case string property `autoCorrect` is not retained as a public
-alias. Prefer boolean `autocorrect` writes in new code; migrated Shoelace `'off'`/`'on'` property
-writes remain valid and read back as booleans. Markup uses `autocorrect="on"` /
-`autocorrect="off"`.
-
 - `min?: number | string` / `max?: number | string` (attributes `min`/`max`) /
   `step?: number | 'any'` (attribute `step`, accepts the native `'any'` value alongside a number)
   — forwarded verbatim to the native
@@ -118,10 +102,7 @@ writes remain valid and read back as booleans. Markup uses `autocorrect="on"` /
   forwarded to the native input and reported as `validity.patternMismatch`. Anchored to the whole
   value by the platform, so no `^`/`$` is needed; an empty value never violates it
 - `passwordToggle: boolean = false` (attribute `password-toggle`, reflected — `type="password"`
-  only) — renders the built-in show/hide-password button. **Breaking in 8.0.0: this is now opt-in.**
-  Before, `type="password"` always rendered the toggle and there was no way to remove it; a consumer
-  whose threat model or visual design excludes one had to hide it with CSS. Add `password-toggle`
-  to keep the old rendering
+  only) — opt-in built-in show/hide-password button
 - `passwordVisible: boolean = false` (attribute `password-visible` — `type="password"` only) —
   whether the field currently reveals its raw text. Toggled by the built-in button, and also
   settable up front with or without that button being rendered
@@ -142,10 +123,8 @@ writes remain valid and read back as booleans. Markup uses `autocorrect="on"` /
   referenced element only needs a string `.value`, so a native `<input>`/`<textarea>` works the
   same as another `lr-input`; see "A new-password field" below for the password-confirmation shape
 - `withoutSpinButtons: boolean = false` (attribute `without-spin-buttons`, reflected —
-  `type="number"` only) — suppresses the browser's own increment/decrement spin buttons.
-  **Breaking in 8.0.0:** `type="number"` used to hide them unconditionally; left unset, the
-  platform's spinners now render exactly as they do on a bare `<input type="number">`.
-  `<lr-number-input>` defaults this the other way (`true`), so its rendering is unchanged
+  `type="number"` only) — suppresses native spin buttons; unset leaves them visible.
+  `<lr-number-input>` defaults this to `true`
 - `noSpinButtons: boolean = false` (attribute `no-spin-buttons`) — Shoelace alias for
   `withoutSpinButtons`; either suppresses native number spinners
 - `debounce?: number` (attribute `debounce`, ms) — how long to wait after the last keystroke
@@ -195,7 +174,8 @@ Three more native passthroughs:
   non-finite `steps` falls back to `1`; `0` is a no-op, as is `step="any"`, as is any `type` the
   platform gives no allowed value step (it throws `InvalidStateError` for those, which is swallowed
   here), and as is `disabled` or `readonly`. `type="number"` and `type="time"` are the two that step
-  — on a time field the unit is seconds, matching its `step`.
+  — on a time field the unit is seconds, matching its `step`. They use the current properties in
+  that synchronous call and are also no-ops before the native input renders.
   `<lr-number-input>`'s stepper buttons build on these and _do_ emit, because a button press is a
   user edit.
 
@@ -281,10 +261,8 @@ what is specific to it.
 
 - **`size` accepts both spellings of every tier.** The canonical ladder is
   `2xs`/`xs`/`s`/`m`/`l`/`xl`, and `small`/`medium`/`large` — Web Awesome's and Shoelace's names —
-  are accepted as exact synonyms for `s`/`m`/`l`. Nothing is normalized away in JS: the shared
-  stylesheet matches both spellings in the same selector list, so `size="small"` costs nothing and
-  `el.size` reads back whatever you wrote. A migration off either upstream is a tag rename with no
-  attribute rewrite. One ladder now drives `lr-button`, `lr-input`, `lr-select`, `lr-combobox`,
+  are accepted as exact synonyms for `s`/`m`/`l`. `el.size` reads back the spelling supplied.
+  One ladder drives `lr-button`, `lr-input`, `lr-select`, `lr-combobox`,
   `lr-date-input`, `lr-textarea`, `lr-checkbox`, `lr-radio`, `lr-switch` and `lr-slider`, so
   same-`size` controls line up in a toolbar row by construction. Retune a whole tier from one place
   with `--lr-theme-form-control-height-*` rather than per component. Set
@@ -293,9 +271,8 @@ what is specific to it.
   radius.
 - **`appearance` is the fill vocabulary and nothing else.** `accent` (the loud semantic fill),
   `filled` (a quiet tint of the same tone), `outlined` (a border, no fill), `filled-outlined`
-  (both) and `plain` (neither). It used to double as a _container_ treatment on other components;
-  that meaning moved to `frame` (`card`/`plain`) in 8.0.0, so `appearance` means one thing
-  library-wide. `lr-button` adds two tiers of its own on top (`quiet` and `link`). Text fields
+  (both) and `plain` (neither). Container treatment uses `frame` (`card`/`plain`).
+  `lr-button` adds `quiet` and `link`. Text fields
   (`lr-input`, `lr-textarea`, and `lr-select`) default to `outlined`; `lr-button` defaults to `accent`.
 - **`pill` rounds the control's ends.** Available on `lr-input`, `lr-number-input`, `lr-time-input`,
   `lr-textarea`, `lr-select`, `lr-combobox`, `lr-date-input`, `lr-phone-input`, `lr-token-input`,
@@ -303,13 +280,9 @@ what is specific to it.
   component's own `--lr-*-radius` knob to `--lr-radius-pill` — rather than declaring a radius on a
   part, so the knob stays the single corner-radius override point and a consumer's own value still
   wins over it.
-- **`setCustomValidity(message)` and `resetValidity()` are on every form-associated _value_ control
-  here** — every one
-  that submits something, whether it drives `ElementInternals` through the shared mixin or by hand.
-  (`lr-button` is a form-associated submitter, so an ancestor `<fieldset disabled>` and
-  `form.elements` reach it, but it carries no value or validity and therefore has no such method;
-  `lr-icon-button` is deliberately not form-associated.) It is the standard channel for a rejection
-  no client-side constraint can express — a server-side
+- **`setCustomValidity(message)` and `resetValidity()` are on every form-associated value control
+  here and on the form-associated `lr-button` submitter.** `lr-icon-button` is not form-associated.
+  These methods handle a rejection no client-side constraint can express — a server-side
   "that email is already registered". A non-empty message raises `customError` and becomes
   `validationMessage`, so the control fails `checkValidity()`, blocks submission, and matches
   `:invalid`/`:state(invalid)`.
@@ -398,7 +371,7 @@ Several controls expose the same pair: a per-`size` `*-min-height` **floor**, an
 <lr-input type="time" label="Reminder" id="reminder"></lr-input>
 <button type="button" id="open-picker">Pick a time</button>
 <script type="module">
-  import "@aceshooting/lyra-ui/components/forms/input/input.js";
+  import "@aceshooting/lyra-ui/components/lr-input.js";
   const time = document.getElementById("reminder");
   // showPicker() needs user activation, so drive it from a real click.
   document
@@ -411,14 +384,8 @@ Several controls expose the same pair: a per-`size` `*-min-height` **floor**, an
 attribute form is enough to turn each on. `autofocus` is likewise `false`-defaulting — none of
 these four needs the property form to be reset.
 
-**A new-password field.** There is no dedicated password-purpose preset — a deliberate decision,
-not an omission: the only thing such a preset would actually save is `autocomplete`, and that value
-has no single correct default for "a password field" (`new-password` on a set/change/reset flow,
-`current-password` on a login one, and one is never derivable from the other), so a `purpose`
-property would still need a second parameter carrying that same distinction, in exchange for a
-non-standard vocabulary a migrating `wa-`/`sl-`/native `<input type="password">` author would have
-to learn instead of carrying over unchanged. Compose the existing primitives directly, the same way
-a plain native `<input type="password">` does:
+**A new-password field.** Set `autocomplete` explicitly: use `new-password` for set/change/reset
+flows and `current-password` for login. A confirmation pair can use `match`:
 
 ```html
 <lr-input
@@ -440,12 +407,8 @@ a plain native `<input type="password">` does:
 ></lr-input>
 ```
 
-`autocomplete="new-password"` (rather than the bare `password` token, and never `current-password`
-on a set/change/reset flow) is the platform contract that keeps a browser's or password manager's
-own generator and save prompt from cross-contaminating a change/reset flow with the account's
-existing credential; set it explicitly on every field in the pair, since `autocomplete` has no
-purpose-derived default here. `match` (above) is what makes the second field fail validity —
-`customError`, with a localized mismatch message — for as long as its value disagrees with the
+Set `autocomplete="new-password"` on both fields in the pair; there is no purpose-derived default.
+`match` makes the second field fail with a localized `customError` while its value differs from the
 first field's, referenced here by id.
 
 **Known gotchas:**
@@ -465,24 +428,13 @@ first field's, referenced here by id.
   value, and the localized `valueInvalid` string when only the script-value check did.
 - An empty value is never `tooShort` and never a `patternMismatch` — both native constraints skip
   the empty string, and `required` is what rejects it.
-- **The `password-toggle` button is opt-in as of 8.0.0.** A bare `type="password"` now ships no
-  toggle at all, and the `password-toggle` part is absent from the shadow tree with it — a
-  `::part(password-toggle)` rule, or a test that queries for it, silently matches nothing until the
-  attribute is set. The toggle never renders for a non-password `type`, opted in or not.
-- **`type="number"` no longer hides the native spin buttons on its own.** Set
-  `without-spin-buttons` (or use `<lr-number-input>`, which defaults it to `true` and draws its own
-  stepper pair) to get the previous rendering back.
-- `showPicker()` swallows every platform failure by design, so it returns without telling you the
-  picker didn't open. Don't build a flow that assumes a picker is now on screen.
-- `stepUp()`/`stepDown()` are silent — they emit no `input`/`change`. Emit your own, or drive the
-  value through a real user affordance, if downstream state depends on those events.
-- **A `match` id reference resolves in this element's own root, not the whole document.** Two
-  fields inside two different shadow roots (a confirm field composed by one component, the field it
-  should match composed by an unrelated one) must pair through a direct element reference
-  (`confirm.match = passwordEl`) instead of an id string — exactly like every other idref this
-  library resolves, `aria-describedby` included. An id that does not resolve at all (a typo, or an
-  element removed later) is inert rather than a permanent block on submission: `match` stops
-  applying, it does not fail closed.
+- `password-toggle` and its CSS part render only for `type="password"` with the opt-in attribute.
+  Native number spinners remain visible unless `without-spin-buttons` is set; `lr-number-input`
+  defaults to its own stepper pair.
+- `showPicker()` can return without opening a picker. `stepUp()`/`stepDown()` emit no `input` or
+  `change`; downstream observers needing those events should use a user affordance or emit them.
+- A `match` id resolves in this element's own root. Use a direct element reference
+  (`confirm.match = passwordEl`) across shadow roots. An unresolved id makes the constraint inert.
 
 **Additional API surface:**
 

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

@@ -122,7 +122,7 @@ tokens `--lr-color-border-subtle`,
 
 ```ts
 import { html } from "lit";
-import "@aceshooting/lyra-ui/components/utility/json-viewer/json-viewer.js";
+import "@aceshooting/lyra-ui/components/lr-json-viewer.js";
 
 html`<lr-json-viewer
   .data=${apiResponse}

package/llms/components/lr-knowledge-base.md

@@ -7,7 +7,7 @@
 - **Family** `components/retrieval/` — 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: [retrieval](https://github.com/aceshooting/lyra-ui/blob/main/packages/lyra-ui/llms/retrieval.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** 29 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`
@@ -62,11 +62,9 @@ before 9.0.0 — the library's only abbreviated event prefix. `<lr-knowledge-bas
 re-emitted them under the `lr-source-*` names, so a host listening on the admin shell needs no
 change; a host listening directly on `<lr-knowledge-base>` renames its four listeners.
 `lr-retry-request` (`detail: null`, cancelable) proposes a retry when the nested table's built-in
-retry button is activated. It fires before the deprecated cancelable `lr-retry` alias (also
-`detail: null`); preventing either event keeps both the parent and table in the error state.
-Without a veto, the default action clears `error`. The alias remains supported until removal no
-earlier than 24.0.0 and warns only when vetoed. This component contains both nested table retry
-events and re-proposes its own pair, so hosts receive each parent event once.
+retry button is activated. Preventing it keeps both the parent and table in the error state.
+Without a veto, the default action clears `error`. This component contains the nested table request
+and re-proposes its own canonical request, so hosts receive the parent event once.
 
 **Slots:** `error` — replaces the nested table's built-in failed-load state, including its retry
 button, while `error` is set.

package/llms/components/lr-knowledge-graph-explorer.md

@@ -7,8 +7,7 @@
 - **Family** `components/retrieval/` — 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: [retrieval](https://github.com/aceshooting/lyra-ui/blob/main/packages/lyra-ui/llms/retrieval.md)
-- **Deprecated event** `lr-link-click` since `22.0.0`; use event `lr-edge-activate`; removal not before `24.0.0` — Activation covers pointer and keyboard gestures. The old event remains available with its original detail; edge activation names its optional identifier edgeId.
-- **Deprecated event** `lr-node-click` since `22.0.0`; use event `lr-node-activate`; removal not before `24.0.0` — Activation covers pointer and keyboard gestures. The old event remains available with its original detail; edge activation names its optional identifier edgeId.
+- **Deprecations** none
 - **Optional peers** `d3-drag`, `d3-force`, `d3-selection`, `d3-zoom` — see `llms/peers.md`
 - **Themeable via** 13 parts, 1 custom property — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
@@ -132,8 +131,6 @@ filtered-out id). None change `selectedNodeId` or filters.
   (`detail: { nodeId, x, y }`), `lr-edge-activate` (`detail: { sourceNodeId, targetNodeId, edgeId? }`), `lr-community-activate`
   (`detail: { communityId }`), `lr-node-expand` (`detail: { nodeId }`, from `lr-graph` and/or `lr-neighbor-list`),
   `lr-relation-activate` (`detail: { relation, sourceNodeId?, targetNodeId?, occurrenceIndex }`, from `lr-path-strip`).
-- `lr-node-click` — deprecated alias emitted after `lr-node-activate` with the same detail.
-  `lr-link-click` follows `lr-edge-activate`, retaining its legacy `linkId` detail field.
 
 **Slots:** `details` — overrides the details popover's default content (an `lr-entity-card` with a
 nested `lr-neighbor-list` and a pin toggle) entirely, including the two additive slots below.
@@ -176,7 +173,7 @@ the composed graph too. Retheme the composed graph through `lr-graph`'s own cust
   resolves `LyraGraphNode.label || LyraGraphNode.accessibleLabel || LyraGraphNode.id` — a node with
   only a spoken `accessibleLabel` (no visible `label`) still shows that text instead of falling
   straight through to its raw id.
-- `lr-graph.getNodePosition()` and `lr-node-click`'s `{ x, y }` are graph-_local_ drawing
+- `lr-graph.getNodePosition()` and `lr-node-activate`'s `{ x, y }` are graph-_local_ drawing
   coordinates, never viewport pixels. For `renderer="svg"` this component resolves the real viewport
   rect from `event.composedPath()`'s `[part="node"]` element; for `renderer="canvas"` (no per-node
   DOM) it uses the click's `clientX`/`clientY`. While an svg-click popover stays open it re-anchors

package/llms/components/lr-known-date.md

@@ -77,7 +77,7 @@ Each access returns a fresh `LyraFormValidator<LyraKnownDate>[]`; its entry obse
 element's current `ValidityState` into `{ isValid, message, invalidKeys }` without changing it.
 
 ```ts
-import { LyraKnownDate } from "@aceshooting/lyra-ui/components/utility/known-date/known-date.js";
+import { LyraKnownDate } from "@aceshooting/lyra-ui/components/lr-known-date.js";
 
 const knownDate = document.querySelector("lr-known-date")!;
 const result = LyraKnownDate.validators[0].checkValidity(knownDate);