@aceshooting/lyra-ui 29.0.2 → 29.1.0

package/llms/shared/forms-and-accessibility.md

@@ -450,22 +450,8 @@ documented accessibility scope and how to report an accessibility issue, see
 
 Use the host `aria-label` attribute or native `ariaLabel` property to name a component. Where the
 component owns an internal role, it forwards that host name to the semantic element. An explicitly
-present host name, including `aria-label=""`, wins over the retained `accessibleLabel` fallback.
+present host name, including `aria-label=""`, is honored as given.
 This applies to `lr-table`'s grid and `lr-sequence-strip`'s list as well.
 
-On `lr-attachment-trigger`, `lr-callout`, `lr-carousel`, `lr-dialog`, `lr-drawer`, `lr-file-input`,
-`lr-lite-chart`, `lr-progress-bar`, `lr-progress-ring` and `lr-reorder-item`, the older
-`accessible-label` attribute was removed in 23.0.0 and no longer supplies an accessible name.
-Their `accessibleLabel` properties remain supported as deprecated fallbacks, with removal no
-earlier than 24.0.0. On `lr-table` and `lr-sequence-strip`, both `accessible-label` and
-`accessibleLabel` remain supported with removal no earlier than 24.0.0. These retained
-compatibility inputs can issue one-time development notices; use the native host name for new
-code. The migration reference lists each attribute and property independently.
-
-`lr-message-parts` retains a deprecated nullable `accessibleLabel` property, with removal no earlier
-than 24.0.0. It maps to the current `aria-label` attribute: authoring that attribute updates the
-property, and removing it restores `null` and the localized default name. Normal host attribute
-use and removal are supported without deprecation warnings. Assigning a non-null value directly to
-`accessibleLabel` while no host `aria-label` is present remains a working fallback and warns once
-in development. Use the host `aria-label` or native `ariaLabel` instead; an explicitly empty host
-name still takes precedence.
+Name components with the host `aria-label` / `ariaLabel`. The former `accessible-label` attribute and
+`accessibleLabel` property no longer exist (see the generated migration reference).

package/llms/shared/imports-and-registration.md

@@ -71,23 +71,9 @@ Family-wide breaking-change summaries open each authored `llms/<family>.md`, and
 `llms/components/<tag>.md` header links its family summary. `llms/migration.md` covers only
 `wa-*`/`sl-*` renames, not Lyra release history.
 
-The major-version landmarks after 9.0.0 are:
-
-- **10.0.0:** removed eligible members deprecated during 9.x and made the public-contract
-  corrections listed in its changelog entry; follow that entry's per-member migration guidance.
-- **11.0.0:** carried no known consumer-breaking change; consumers upgrading from 10.x were not
-  expected to change code.
-- **12.0.0:** removed the inherited static `LyraElement.getPropertyDescriptor()` surface after Lit
-  deprecated that finalization hook. Ordinary component consumers need no migration; only subclasses
-  that themselves overrode the hook are affected. Collection snapshot enforcement moved to a
-  decorator-agnostic accessor seam instead.
-
-- **24.0.0:** removed eligible v22 compatibility routes, including package-root component
-  constructors, duplicate nested registration entries, the combined `ssr-loader.js` entry, and the
-  retired theme/preset facade. Use stable tag-shaped registration entries, a component's
-  registration-free `.class.js` subpath, the split SSR/hydration entries, and the current style API.
-  The [v23-to-v24 migration guide](v23-to-v24-migration.md) gives the removed routes, ordered
-  consumer cleanup and retained-profile instructions.
+The [v23-to-v24 migration guide](v23-to-v24-migration.md) gives the removed routes, ordered consumer
+cleanup and retained-profile instructions. Use stable tag-shaped registration entries, a component's
+registration-free `.class.js` subpath, the split SSR/hydration entries, and the current style API.
 
 ### The support window
 

package/llms/shared/localization-and-rtl.md

@@ -61,8 +61,6 @@ The side-effect-free `@aceshooting/lyra-ui/localization.js` entry exports
 `LyraPluralMessage`, `LyraPluralCategory`, `LyraLocaleBridgeOptions` and `LyraLocaleBridgeCleanup`.
 The package root continues to re-export the runtime for compatibility and remains registration-free;
 use the dedicated entry when the application only needs locale setup and the narrower import graph.
-The former utility-scoped entry point was removed in 23.0.0. Change that import specifier to
-`@aceshooting/lyra-ui/localization.js`; the helper contracts are unchanged.
 **`LYRA_DEFAULT_STRINGS` is the authoritative key list** (matching the `LyraMessageKey` union) —
 read it to find the key to override rather than guessing one. Date, number, byte, relative-time and
 calendar output goes through `Intl`.

package/llms/shared/styles-and-tokens.md

@@ -272,9 +272,9 @@ server-rendered pages and for application elements that paint before any Lyra el
 `tokens-root.css` is the same layer alone, as a static stylesheet, for pages that do not use
 `theme.css`:
 
-- **Server-rendered pages.** Declarative shadow roots no longer carry the layer, so link
-  `theme.css` (or `tokens-root.css`) for a correct first paint before hydration (see
-  [Theme scopes](#theme-scopes) for application shadow roots).
+- **Server-rendered pages.** See
+  [SSR and declarative shadow DOM](./frameworks-and-ssr.md#ssr-and-declarative-shadow-dom) and
+  [Theme scopes](#theme-scopes) for application shadow roots.
 - **Application elements that paint before the first Lyra element is registered**, for example
   ahead of a lazily loaded route; otherwise they change value when the layer is adopted.
 - **Large pages that load Lyra late.** Without a static copy, the layer is adopted when the first
@@ -381,8 +381,7 @@ and the mode it sees. The list is closed: `:root`; the mode scopes `.lr-light`,
   outer scope reaches a marked region exactly as it reaches an unmarked one, and adding a marker
   where nothing needs it changes nothing. With `theme.css`, mode scopes and the style-axis
   boundaries also re-resolve the inputs from the selected look, accent and mode, so an input set
-  above one of them stops there (set it on that boundary, or below it). A scope costs a little less
-  than one component did before 28.0.0, so put inputs on a common ancestor rather than marking every
+  above one of them stops there (set it on that boundary, or below it). A scope is cheap, so put inputs on a common ancestor rather than marking every
   row of a list.
 - **`applyLyraStyleScope()`** writes the marker whenever it writes inline inputs.
 - **Brand regions in the default look.** The marker re-derives outputs but is not a style boundary,
@@ -703,7 +702,6 @@ Override the look through an unlayered application rule or the lr-overrides laye
 }
 ~~~
 
-The former global themes/shadcn.css facade and its data-lr-theme-preset behavior have been removed.
 Use theme.css and the data-lr-look axis for new styling; looks/shadcn.css is needed only for the
 compatibility aliases above.
 
@@ -799,8 +797,7 @@ code. See each control's own reference page for its exact pair.
   takes precedence, and it has to: the shipped `design-tokens.css` declares
   `--lr-theme-icon-button-size` on `:root`, and a `var()` chain only falls through for a property
   that is unset *everywhere*, not merely shadowed nearer the element. Reading the theme tier first
-  therefore made this knob inert for anyone loading that stylesheet (a real 18.1.0 defect, fixed in
-  18.2.0). `--lr-icon-button-size`
+  therefore made this knob inert for anyone loading that stylesheet. `--lr-icon-button-size`
   is **element-scoped on purpose** and is not a wrapper knob: every component re-declares it on its
   own host so the touch-target floor can apply per element, so a value set on a wrapper is replaced
   at the first component in between and never reaches anything nested inside one. That behaviour is
@@ -876,8 +873,7 @@ sets `color-scheme`. **Every engine follows the nearest mode scope, with or with
 document layer carries mode to every scope through two inherited private switches, so a `.lr-light`
 island inside a `.lr-dark` region is light, a mode-neutral scope keeps its ancestor's mode, and the
 OS preference decides the root unless the root carries an explicit mode. A real `--lr-theme-*` value
-still wins over the built-in light or dark default. (Before 28.0.0 an ancestor mode reached
-components without `theme.css` only in Chromium, through `:host-context()`.)
+still wins over the built-in light or dark default.
 
 Each component host also keeps `:host([hidden]) { display: none !important; }` and an inherited
 `box-sizing: border-box` reset.
@@ -1218,32 +1214,27 @@ resolve again at each preference boundary, including a nested look or a local `s
 
 ### Compatibility and saved preferences
 
-When upgrading from v21, these component rendering changes also apply without opting into a style
-axis. `lr-button-group` sizes to its content in narrow allocations and no longer reserves an
-artificial intrinsic width. An explicit host width remains respected; set
-`lr-button-group::part(base) { inline-size: 100%; }` when the internal row should fill that width.
-The attachment menu inside `lr-prompt-input` now follows its explicit surrounding light/dark mode;
-WebKit previously could use operating-system colors when that scheme disagreed with the surrounding
-mode. Remove any application workaround that depended on that mismatch.
-Menus also clamp their minimum width to the containing allocation and viewport, and positioned
-submenus respect the positioner's available width. This prevents the former minimum from forcing
-overflow in narrow spaces or with enlarged text; it remains effective when sufficient space exists.
-The default Lyra dark control boundary changes from `#6b6b74` to `#787881` so it clears 3:1 on the
-dark overlay `#2b3038` (3.034:1); the previous value failed on raised and overlay surfaces. This
-changes `--lr-theme-color-surface-border` and its shared fallback only, keeping light boundaries,
-other looks and semantic palettes intact. Plain chromatic button text moves toward body text on
-hover/press, and selected tree rows use on-quiet text in those states, retaining 4.5:1 as their fills
-change. Resting plain-button/selected-row text and explicit component foreground overrides remain
-unchanged. Step numbers and interactive context-meter legend rows use matching semantic fill/text
-pairs; control-border colors no longer act as their text backgrounds. Material uses 8% hover and
-12% press state layers with its `currentColor` mix partner, keeping filled-action labels at 4.5:1.
-
-Runtime custom accents, including `setLyraStyle({ accent })` and legacy gemstone presets, now
-floor the loud fill to 4.5:1 against its quiet fill and the built-in reference surfaces because the
-same token paints accent text. Its on-loud foreground follows the corrected fill. For example,
-light shadcn emerald changes from `#34d399` with black on-loud text to `#1a6a4d` with white text
-(6.537:1). Checked controls, brand text and streaming accents follow that loud token; secondary
-neutral controls stay unchanged. The requested and persisted accent color is retained.
+Component rendering contracts that apply without opting into a style axis: `lr-button-group` sizes to
+its content in narrow allocations and reserves no artificial intrinsic width. An explicit host width
+remains respected; set `lr-button-group::part(base) { inline-size: 100%; }` when the internal row
+should fill that width. The attachment menu inside `lr-prompt-input` follows its explicit
+surrounding light/dark mode. Menus clamp their minimum width to the containing allocation and
+viewport, and positioned submenus respect the positioner's available width, so the minimum never
+forces overflow in narrow spaces or with enlarged text; it remains effective when sufficient space
+exists. The default Lyra dark control boundary (`--lr-theme-color-surface-border` and its shared
+fallback) clears 3:1 on raised and overlay surfaces; light boundaries, other looks and semantic
+palettes are unaffected. Plain chromatic button text moves toward body text on hover/press, and
+selected tree rows use on-quiet text in those states, retaining 4.5:1 as their fills change.
+Resting plain-button/selected-row text and explicit component foreground overrides are unchanged.
+Step numbers and interactive context-meter legend rows use matching semantic fill/text pairs;
+control-border colors do not act as their text backgrounds. Material uses 8% hover and 12% press
+state layers with its `currentColor` mix partner, keeping filled-action labels at 4.5:1.
+
+Runtime custom accents, including `setLyraStyle({ accent })` and legacy gemstone presets, floor the
+loud fill to 4.5:1 against its quiet fill and the built-in reference surfaces because the same token
+paints accent text. Its on-loud foreground follows the corrected fill. Checked controls, brand text
+and streaming accents follow that loud token; secondary neutral controls are unchanged. The
+requested and persisted accent color is retained.
 
 The runtime and no-flash bootstrap still read v1 records written by the retired theme API. On
 read, auto becomes system and the old accent reference surface becomes accentBackground. A saved

package/llms/shared/testing-and-utilities.md

@@ -297,8 +297,8 @@ they carry no `tag`: `components/media/flag/flag-peer.js`,
 stand in for. They are a separate array rather than tag-less rows mixed into `entries`, so a reader
 that keys `entries` by `tag` keeps working; `integrations`, `distModule` and `localeKeys` are all
 additive, which is why the schema version is unchanged. `registrationModule` is the `src/` path used
-internally; `distModule` is a retained published specifier and equals the stable `entry` for v24
-per-tag registrations and integration bridges. `registers` is every `lr-*` tag
+internally; `distModule` is a retained published specifier and equals the stable `entry` for per-tag
+registrations and integration bridges. `registers` is every `lr-*` tag
 importing `entry` defines, direct or transitive, derived from the same transitive-import analysis
 `scripts/check-component-dependencies.mjs` already performs against the real registration graph
 (not a second hand-maintained list). `localeKeys` is every `LyraMessageKey` the registered tags can
@@ -341,8 +341,7 @@ same way `all.js` registers its root-included tags (the package root itself regi
 and want a single import; reach for the granular
 `@aceshooting/lyra-ui/components/<tag>.js` path when you do not, because a barrel cannot be
 tree-shaken down to the two elements you actually render. The tag-shaped path remains stable if a
-component moves between Lyra's internal family folders. Duplicate nested registration paths were
-removed in v24; family barrels remain supported.
+component moves between Lyra's internal family folders.
 
 ```js
 import "@aceshooting/lyra-ui/components/forms"; // every form control
@@ -780,7 +779,7 @@ number; clearTimeout(handle: number): void }`.
 - **`localization` → `subscribeLyraLocale(listener): () => void` and
   `bridgeLyraLocale(options?): () => void`** — the _active-locale_ half of the locale runtime.
   Import these helpers from the side-effect-free `@aceshooting/lyra-ui/localization.js` entry.
-  The former `utilities/localization.js` route was removed in 23.0.0. The extensionless `@aceshooting/lyra-ui/utilities`
+  The extensionless `@aceshooting/lyra-ui/utilities`
   barrel keeps exporting them. `subscribeLyraLocale()` is distinct from
   `subscribeLyraLocaleRegistry()`, which answers a different question — see "Localization".
   `subscribeLyraLocale()` fires whenever the active selection changes, and when a newly registered