@aceshooting/lyra-ui 21.0.0 → 21.1.0

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

@@ -9,129 +9,6 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 2 parts, 2 custom properties — see this component's own `@csspart`/`@cssprop` list below
-- **Documented with** `lr-menubar` (same section below)
+- **Themeable via** 2 parts, 2 custom properties — see `lr-menubar.md`
+- **Documented with** `lr-menubar`: see [lr-menubar.md](./lr-menubar.md).
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
-
----
-
-## `lr-menubar` / `lr-menubar-item`
-
-A horizontal application menubar following the APG menubar pattern. Import
-`@aceshooting/lyra-ui/components/lr-menubar.js`; it registers the item and menu dependencies.
-Use only `lr-menubar-item` elements in the default slot. A title's `menu` slot takes exactly one
-`lr-menu`; without it the title is a plain action that dispatches native `click`.
-
-```html
-<lr-menubar label="Application">
-  <lr-menubar-item>
-    File
-    <lr-menu slot="menu">
-      <lr-menu-item value="new-tab" aria-keyshortcuts="Control+T Meta+T">
-        New tab <lr-kbd slot="details" keys="mod+t"></lr-kbd>
-      </lr-menu-item>
-      <lr-menu-item>Share<lr-menu slot="submenu"><lr-menu-item>Email link</lr-menu-item></lr-menu></lr-menu-item>
-      <hr />
-      <lr-menu-item value="print">Print…</lr-menu-item>
-    </lr-menu>
-  </lr-menubar-item>
-  <lr-menubar-item>Edit<lr-menu slot="menu"><lr-menu-item>Undo</lr-menu-item></lr-menu></lr-menubar-item>
-  <lr-menubar-item>Help</lr-menubar-item>
-</lr-menubar>
-```
-
-Import `@aceshooting/lyra-ui/components/lr-kbd.js` separately for shortcut chips. Displaying a
-shortcut does not bind it. `Control+T Meta+T` describes a handler accepting either `ctrlKey` or
-`metaKey`. If the app binds only its platform modifier, keep the ARIA value aligned with the chip:
-`item.setAttribute('aria-keyshortcuts', kbd.effectivePlatform === 'mac' ? 'Meta+T' : 'Control+T')`.
-The chip's decorative `details` subtree is hidden from assistive technology.
-
-### `lr-menubar`
-
-**Properties:**
-
-- `label?: string` — accessible name of the menubar. The host `aria-label` wins, including `""`;
-  an explicit `label=""` stays empty. When both are absent, no name attribute is rendered.
-- `size: LyraSize = 'm'` — shared control ladder, inherited by the titles.
-- `frame: LyraFrame = 'card'` — surface, subtle border and shadow; `'plain'` makes the same
-  geometry transparent. Other values use the card appearance.
-
-**Events:** `lr-select`, cancelable `CustomEvent<MenuItemSelectDetail>`, bubbles once from the
-owning menu with `detail.item`. Prevent default to keep the menu open. Checkbox/radio
-`lr-menu-item-change` also bubbles from its item. There are no menubar lifecycle events or public
-open/close methods.
-
-**Slots:** default, containing only `lr-menubar-item` elements. **CSS parts:** `base`.
-The menu width hooks `--lr-menu-min-inline-size` and `--lr-menu-max-inline-size` inherit from the
-menubar or an ancestor and apply to every slotted menu.
-
-### `lr-menubar-item`
-
-**Properties:** `disabled: boolean = false` — removes the title from traversal, closes its menu,
-and suppresses mouse, touch, keyboard and programmatic activation. Disabled `mousedown` does not
-move focus. Consumer capture listeners on a further ancestor can still observe a dispatched
-click, but listeners on the item and bubbling ancestor listeners do not receive it.
-
-**Slots:** default, the visual label; `menu`, exactly one `lr-menu` (the first assigned menu wins;
-other elements are ignored). **CSS parts:** `base`, `label`. No own custom events. Native `click`
-is the action contract for a title without a menu. **Methods:** `click(): void` does nothing while
-disabled, otherwise dispatches a native host click.
-
-The host owns `role="menuitem"`, literal `aria-disabled`, and, only with a menu,
-`aria-haspopup="menu"` plus literal `aria-expanded`. Its accessible name comes from the default
-slot, so open menu contents never leak into it; author `aria-label` or `aria-labelledby` wins.
-Menus inherit the title's name unless given their own `aria-label` or `label`. An empty title
-leaves the menu's localized `menuLabel` fallback intact.
-
-**Themeable custom properties:**
-
-- `--lr-menubar-item-hover-bg` (default `var(--lr-color-brand-quiet)`) paints hover, focus-visible
-  and the open title.
-- `--lr-menubar-item-active-bg` (default
-  `color-mix(in oklab, var(--lr-menubar-item-hover-bg, var(--lr-color-brand-quiet)), var(--lr-color-mix-partner) var(--lr-color-mix-active))`)
-  paints the pressed title, including when already open.
-
-Both hooks inherit from the item, menubar or any ancestor. Open titles receive an outline in
-forced colors. Reduced motion removes menu transitions and minimizes title transitions.
-
-### Keyboard and pointer behavior
-
-| Focus | Key | Result |
-|---|---|---|
-| Title | Left/Right | Previous/next enabled title, wrapping; directions reverse in RTL |
-| Title | Home/End | First/last enabled title |
-| Title | Down, Enter, Space | Open and focus first menu item; Enter/Space click a plain action |
-| Title | Up | Open and focus last menu item; unhandled on plain actions |
-| Title | Printable character | Case-insensitive typeahead with a 500ms buffer |
-| Expanded title | Traversal or matching typeahead | Carry the open menu along; focus stays on the title |
-| Menu leaf | Inline forward/back arrow | Carry to next/previous title; nested back closes only that submenu |
-| Menu | Up/Down, Home/End, Enter/Space | Existing menu navigation and activation |
-| Open menu/title | Escape | Close the innermost menu; menu focus returns to its title |
-| Open menu/title | Tab | Close and continue native traversal; Shift+Tab from the menu returns to its title |
-
-Handled keys prevent page scrolling. Escape/Tab while collapsed and unmatched typeahead remain
-unhandled. Header/footer inputs retain their own arrow behavior. Disabled, hidden, aria-hidden and
-inert titles are skipped. Moving onto a plain action collapses an open menu.
-
-Clicking a menu title toggles its menu and keeps focus on the title. While one menu is open,
-hovering another enabled menu title carries the menu immediately; hovering while collapsed,
-hovering plain actions, and touch pointer-over events do nothing. Clicking a title that hover just
-opened closes it. Outside pointers, focus leaving the menubar, removal or disablement close the
-menu. Selection closes and focuses its title unless canceled. Reconnecting resumes collapsed.
-Closing preserves the current focus even with another overlay beneath; if nothing remains focused
-because the menubar was removed, the shared overlay stack may focus its previous entry.
-
-### Sizing and narrow allocations
-
-Titles wrap, with no horizontal scrollbar or automatic overflow menu. The keyboard order stays
-linear. Long titles ellipsize while retaining their full accessible name. A single row measures
-`max(H, 24px + 2P + 2B)`, where H is `--lr-form-control-height`, P is
-`--lr-form-control-padding-block`, and B is `--lr-border-width-thin`. With default tokens this is
-26px at `xs`, 30px at `s`, 40px at `m`, and 48px at `l`; each title is at least 24px in both axes.
-Font, inline padding and radius follow the shared size ladder. Coarse-pointer size floors still
-apply. The shadcn theme gives 32px at `s` and 36px at `m`. Additional wrapped rows add their title
-height plus the shared gap. No container containment is imposed, so intrinsic sizing in a centered
-grid or shrink-to-fit header remains content-based. Both tags render and hydrate on the server;
-menu wrappers begin hidden and inert until connected client behavior attaches their menus.
-
----

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

@@ -47,7 +47,10 @@ MessageFeedbackValue = null` (attribute `feedback-rating`) — forwarded to the
 opens). `feedbackPending: boolean` (read-only, nonreflecting) — true only while the current built-in
 feedback control awaits settlement; it has no `feedback-pending` attribute or change event.
 `revealOnInteraction: boolean = false` (reflected, attribute `reveal-on-interaction`) — hides
-the bar until the closest `lr-chat-message` ancestor is hovered, or the toolbar contains focus.
+the bar until the closest `lr-chat-message` ancestor is hovered, or the toolbar contains focus. It
+also stays revealed while an `lr-dropdown`, `lr-popover` or `lr-context-menu` opened from a slotted
+control is open, since that menu sits in the browser top layer, where focus inside it does not
+count as focus within the toolbar in Chromium and WebKit.
 `label?: string` — accessible name override for the toolbar. Omitting it localizes the default
 `messageActionsLabel` message; an explicit empty string suppresses that default and renders no
 label. `accessibleLabel: string | null =

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

@@ -7,7 +7,7 @@
 - **Family** `components/conversation/` — see `llms/index.md` for its siblings
 - **Status** `stable` since `7.0.0` — see the maturity and deprecation policy in `llms/shared.md`
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
-- **Deprecations** none
+- **Deprecated property** `codeBlockChrome` / `code-block-chrome` since `21.1.0`; use property `code-block-header`; removal not before `23.0.0` — code-block-chrome is a second spelling of code-block-header with identical behavior: either one enables the code-block headers of the built-in text and reasoning Markdown parts, which now always receive code-block-header. One name per concept removes a choice with no difference. It keeps enabling the headers through the 22.x line, and setting it logs a one-time development warning.
 - **Optional peers** `dompurify`, `katex`, `marked`, `shiki` — see `llms/peers.md`
 - **Themeable via** 21 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`
@@ -37,7 +37,9 @@ and `codeBlockHeader: boolean = false` (attribute `code-block-header`) — forwa
 and reasoning Markdown parts while `contentMode="markdown"`. Progressive mode renders settled
 blocks during a streaming part and preserves the `plain` fallback by default; the header adds the
 source language label and localized copy action to built-in code blocks.
-`codeBlockChrome: boolean = false` (attribute `code-block-chrome`) is an equivalent enabling alias. These settings do not replace
+`codeBlockChrome: boolean = false` (attribute `code-block-chrome`) is a deprecated equivalent
+enabling alias (removal not before 23.0.0; setting it logs a one-time development warning), and the
+parts' Markdown elements receive either option as `codeBlockHeader`. These settings do not replace
 the `MessagePart.state` lifecycle or affect `contentMode="plain"`.
 `maxRenderedParts: number = 0` (attribute `max-rendered-parts`) — `0` (the default) renders every
 part, unbounded, matching every prior release; a positive value windows rendering to the newest N
@@ -75,17 +77,24 @@ duration; expanding shows arguments, error and result in place) and pairs it wit
 - Everything else renders as in chip display: unpaired results, a result whose call is outside the
   rendered window, duplicate results after the first, and custom-rendered calls or results. A
   second call part with the same invocation id renders its own unpaired block.
-- The block binds `name`, `callId` and `args` from the invocation, and `redactedFields` from the
+- The block binds `name`, `displayName`, `callId` and `args` from the invocation, and `redactedFields` from the
   invocation-level paths described under redaction below; `result` from
   the paired part (else `invocation.result`); `error` from the paired part when it carries one (else
   `invocation.error`); and `durationMs = endedAt - startedAt` when both are set (else no duration).
   `expanded` is never bound, so a user-expanded block stays open across `parts` updates.
-- Block status, first match wins: invocation `denied` → `denied`; invocation `error` or a paired
-  error result → `error`; a paired result still `streaming` → `running`; any paired result →
+- Block status, first match wins: invocation `denied` → `denied`; invocation `incomplete` (a call
+  that ended without a result, 21.1.0) → `incomplete`, whatever result part is paired; invocation
+  `error` or a paired error result → `error`; a paired result still `streaming` → `running`; any paired result →
   `success`; otherwise the invocation's own status (an unknown value → `pending`), so a call still
   waiting on its result keeps showing `pending`/`running`.
 - The tool-call wrapper stretches to the message width in block display.
 
+**Display name in both displays** (21.1.0). An invocation's `displayName` (the application's own,
+already-translated tool label) is bound to the chip's or the block's `displayName`, so the visible
+and announced tool name is the translated one while `name` still selects the result renderer and
+is still what `lr-tool-call-chip-select` and `lr-render-error` report. A non-string value is not
+forwarded.
+
 **Redaction in both displays.** An invocation's `redactedFields` (dotted paths rooted at
 `args`/`result`/`error`, see `<lr-tool-call-block>`) masks every built-in rendering of its payload
 with the localized `Value hidden`: in block display the block's details; in chip display, and for

package/llms/components/lr-mutation-observer.md

@@ -7,7 +7,8 @@
 - **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: [llms-full.txt](../../llms-full.txt)
-- **Deprecations** none
+- **Deprecated property** `characterData` / `character-data` since `21.1.0`; use property `char-data`; removal not before `23.0.0` — character-data is a Lyra-only spelling of the mirrored char-data attribute (the Web Awesome and Shoelace name) with identical behavior. It keeps reflecting and enabling character-data observation through the 22.x line, and setting it logs a one-time development warning.
+- **Deprecated property** `observeAttributes` / `attributes` since `21.1.0`; use property `attr="*" (or just remove it where attr, attr-old-value or a non-empty attributeFilter is also set)`; removal not before `23.0.0` — attributes is a Lyra-only boolean spelling of the mirrored attr="*" (observe every attribute). Where attr, attr-old-value or a non-empty attributeFilter is also set, attribute observation is already on, so remove attributes instead: adding attr="*" would replace an attributeFilter. It keeps reflecting and enabling attribute observation through the 22.x line, and setting it logs a one-time development warning.
 - **Optional peers** none
 - **Themeable via** 1 part, 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`
@@ -25,11 +26,16 @@ adds no layout.
 needed; reflected), `attr: string | null = null` (reflected; `*` observes every attribute; otherwise a
 space-separated filter), `attrOldValue: boolean = false` (`attr-old-value`), `charData: boolean =
 false` (`char-data`), and `charDataOldValue: boolean = false` (`char-data-old-value`); all four
-mapped attributes reflect. Lyra's
-existing aliases remain and also reflect: `observeAttributes` (`attributes`; unfiltered boolean
-form of `attr`, equivalent to `attr: '*'`) and `characterData` (`character-data`, equivalent to
-`charData`). Plus `subtree: boolean = true`, and programmatic `attributeFilter: string[] = []`
-(neither reflects).
+mapped attributes reflect. Plus `subtree: boolean = true`, and programmatic
+`attributeFilter: string[] = []` (neither reflects).
+
+**Deprecated aliases** (still functional and still reflecting until their removal, no earlier than
+23.0.0; setting either logs a one-time development warning): `observeAttributes` (`attributes`)
+turns on attribute observation, and `characterData` (`character-data`) is identical to `charData`.
+Replace `character-data` with `char-data`. Replace `attributes` with `attr="*"` only when `attr`,
+`attr-old-value` and `attributeFilter` are all unset; otherwise just remove it. Those already turn
+attribute observation on, and a non-null `attr` ignores `attributeFilter`, so adding `attr="*"` next
+to a filter would widen the observer to every attribute.
 
 The browser capability is optional. A missing or throwing owner-window lookup, or an unavailable or
 throwing constructor, leaves that rebuild inert rather than leaking an exception. Individual

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

@@ -9,241 +9,6 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 8 parts, 22 custom properties — see this component's own `@csspart`/`@cssprop` list below
-- **Documented with** `lr-navigation-menu` (same section below)
+- **Themeable via** 8 parts, 22 custom properties — see `lr-navigation-menu.md`
+- **Documented with** `lr-navigation-menu`: see [lr-navigation-menu.md](./lr-navigation-menu.md).
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
-
----
-
-## `lr-navigation-menu`
-
-Site-header navigation following the WAI-ARIA **disclosure navigation** pattern (first-party, no
-`wa-*`/`sl-*` counterpart): a `nav` landmark holding a `role="list"` row of
-`<lr-navigation-menu-item>` links and disclosure buttons. A disclosure's flyout panel opens in one
-shared region below the bar. It never uses `menu`/`menubar` roles — application menus belong to
-`lr-menu`, and no arrow key ever opens or closes a panel.
-
-- **Opening.** Hovering a trigger opens its panel after `showDelay` (mouse only; touch and pen never
-  open on hover). While a panel is open, hovering another trigger switches immediately and the
-  shared region resizes to the new content. A click, Enter or Space opens a panel too. A click on a
-  hover-opened trigger *pins* it, so leaving no longer closes it; the next click closes it.
-  Opening one panel closes the other (`lr-toggle` with `source: 'peer'`).
-- **Hover grace.** A hover that arrives within `skipDelay` ms of a panel closing opens immediately.
-- **Closing.** Escape (focus returns to the trigger only when focus was inside the item), a press
-  outside the open item or on a non-trigger item, focus leaving the item, a hover-opened panel losing
-  the pointer after `hideDelay`, and activating a link — a plain primary click on an `a[href]` inside
-  a panel or on a link item, even when a router calls `preventDefault()`. Ctrl, Meta, Shift and
-  middle clicks close nothing. A panel that holds focus never switches away on hover.
-- **Focus repair.** Whenever a close or collapse would hide the focused element, focus first moves
-  to that item's trigger, or to the toggle when the collapsed list hides.
-- **Keyboard (bar layout).** Every top-level link or button stays in the Tab order and Tab from an
-  open trigger enters its panel. ArrowRight/ArrowLeft move to the next/previous item without
-  wrapping (swapped under right-to-left text); Home/End jump to the first/last. Hidden, `inert`
-  and `aria-hidden` items are skipped. ArrowDown on an *open* trigger focuses the first control in
-  its panel; on a closed trigger, a link or a plain button it does nothing. Inside a panel,
-  ArrowDown/ArrowUp/Home/End move between its links and buttons (text fields and composite widgets
-  keep their own keys). Keys with Alt, Ctrl or Meta are never handled.
-
-**Properties:**
-
-- `accessibleLabel?: string` (attribute `aria-label`) — names the `nav` landmark by attribute
-  presence; an explicitly empty `aria-label=""` leaves it unnamed. Unset, the landmark is named with
-  the localized `navigation` string ("Navigation"). Several menus on one page (for example a header
-  and a footer) need distinct labels, or axe reports `landmark-unique`.
-- `mobileBreakpoint?: string` (attribute `mobile-breakpoint`) — a bare number or a `px`, `rem` or
-  `em` length. The menu collapses while its own content-box inline size is at or below it (the same
-  `<=` comparison and name as `lr-page`). Unlike `lr-page` and `lr-app-rail` there is no default:
-  unset or unresolvable means the menu never collapses and its row wraps instead.
-- `expanded: boolean = false` (reflected) — whether the list shows in the collapsed layout. Kept
-  while the bar layout is active and applied at the next collapse; reset to `false` (with
-  `lr-expanded-change`, source `programmatic`) when the menu leaves the collapsed layout.
-- `indicator: boolean = false` (reflected) — shows a decorative notch under the trigger whose panel
-  is open.
-- `panelAnchor: LyraNavigationMenuPanelAnchor = 'menu'` (attribute `panel-anchor`, reflected) —
-  `menu` aligns every panel with the start edge of the item row, so switching panels resizes one
-  region in place; `item` aligns each panel with its own trigger (no resize animation). Unsupported
-  values, including untyped property writes, normalize to `menu` and repair the attribute.
-- `showDelay: number = 200` (attribute `show-delay`) — hover-open delay in ms.
-- `hideDelay: number = 150` (attribute `hide-delay`) — delay before a hover-opened panel closes once
-  the pointer leaves the item.
-- `skipDelay: number = 300` (attribute `skip-delay`) — the hover grace window; `0` disables it.
-- `distance: number = 6` — gap in px between the anchor and a floating panel.
-- `collapsed` (read-only boolean getter) — whether the collapsed layout is active; `false` on the
-  server and until the first measurement. Mirrored to the `collapsed` custom state.
-
-The three delays are JavaScript timer inputs, not CSS custom properties, and use the same
-`show-delay`/`hide-delay` vocabulary as `lr-tooltip`/`lr-popover`. Non-finite values fall back to
-the defaults and negative values clamp to `0` (a `0` show delay opens in the same turn).
-
-**Methods:** `close(): void` closes the open panel and collapses an expanded list (both announced
-with source `programmatic`), for single-page route changes. Focus moves only when the close would
-hide the focused element; a router's own later `focus()` still wins.
-
-**Events:** `lr-expanded-change` — `detail: LyraNavigationMenuExpandedChangeDetail`
-(`{ expanded, source: 'user' | 'programmatic' }`), not cancelable, fired after a change to
-`expanded` renders. `user` covers the toggle, Escape in the collapsed list, and a link or
-plain-button activation that collapses it. The menu never emits `lr-toggle` itself.
-
-**Slots:** default — `lr-navigation-menu-item` children only; `toggle-icon` — replaces the hamburger
-glyph (inert, `aria-hidden`). Every default-slot child renders inside the `role="list"`, so a
-non-item child fails axe and draws a one-time development warning: keep header chrome such as a
-logo, search or actions *outside* the menu.
-
-**CSS parts:** `base` (the `nav`), `list`, `toggle` (collapsed layout only), `toggle-icon`,
-`toggle-label`, `indicator` (with `indicator`, bar layout only) and `indicator-arrow`.
-
-**Custom state:** `collapsed`.
-
-**Custom properties:** `--lr-navigation-menu-gap` (default `var(--lr-space-xs)`, both layouts),
-`--lr-navigation-menu-indicator-size` (default `var(--lr-size-0-375rem)`),
-`--lr-navigation-menu-indicator-color` (default
-`var(--lr-overlay-border, var(--lr-color-border-subtle))`, matching the panel edge), and
-`--lr-navigation-menu-toggle-active-color` (default `var(--lr-color-text)`), and
-`--lr-positioning-strategy` (read by the items when positioning their panels). All are read through
-inline fallbacks, so they can be set on the menu or any ancestor.
-
-**Collapsed layout.** A "Menu" toggle (`aria-expanded`/`aria-controls` pointing at the list; the
-visible text is the localized `menuLabel`) shows and hides the items as a column. Items stretch to
-the full width and each panel opens in flow below its trigger, indented with a decorative subtle
-rule. Hover and arrow keys are off; Escape first closes an open panel (focus to its trigger), then
-collapses the list (focus to the toggle). The same nodes serve both layouts; nothing moves between
-containers, so the collapse never drops focus. Crossing the breakpoint closes the open panel
-(source `programmatic`) and repairs focus. For a drawer, place the menu inside `lr-drawer` or
-`lr-page`'s `navigation` slot.
-
-**Host allocation.** The host defaults to `display: block; flex: 1 1 0%; min-inline-size: 0`. In a
-flex-row header (including `lr-page`'s header) the menu therefore takes the remaining space rather
-than its content size; a content-sized collapsed menu could otherwise shrink to its toggle and never
-measure wide enough to leave the collapsed layout. Outside a flex parent the declaration is inert.
-In a column flex parent (for example `lr-page`'s navigation region) the host grows in the block axis
-instead — set `flex: none` there. Shrink-to-fit contexts (an `auto` grid track, inline-flex, floats,
-absolute positioning) can still latch collapsed: give the menu a definite inline size there.
-
-**Motion.** Panels open and close through the `navigation-menu.show` and `navigation-menu.hide`
-registry animations; a switch between panels resizes the shared region (timed by
-`--lr-navigation-menu-switch-duration`) while the new content slides in through
-`navigation-menu.enter-from-start` or `navigation-menu.enter-from-end`. The menu is the registry host
-for every owned item, so `setAnimation(menu, 'navigation-menu.show', null)` applies to all of them.
-Reduced motion flattens every transition and skips the resize.
-
-**SSR and hydration.** The server renders the bar layout with the landmark named. Every link item is
-an `<a>`; every other item renders as a trigger (caret visible, `aria-expanded="false"`) because slot
-content cannot be inspected on the server, and every panel renders hidden, even for `open` markup.
-The first browser update drops the caret and ARIA from plain buttons, sets `role="listitem"` on the
-item hosts, keeps only the first `open` item, and reveals and positions its panel.
-
-```html
-<script type="module">
-  import '@aceshooting/lyra-ui/components/layout/navigation-menu/navigation-menu.js';
-</script>
-
-<header style="display: flex; align-items: center; justify-content: space-between">
-  <a href="/">Acme</a>
-  <lr-navigation-menu aria-label="Main" mobile-breakpoint="40rem">
-    <lr-navigation-menu-item>
-      Products
-      <ul slot="panel">
-        <li><a href="/analytics">Analytics</a></li>
-        <li><a href="/billing">Billing</a></li>
-      </ul>
-    </lr-navigation-menu-item>
-    <lr-navigation-menu-item href="/docs" current>Docs</lr-navigation-menu-item>
-    <lr-navigation-menu-item href="/pricing">Pricing</lr-navigation-menu-item>
-  </lr-navigation-menu>
-  <a href="/sign-in">Sign in</a>
-</header>
-```
-
-The registration module also registers `lr-navigation-menu-item`.
-
-### `lr-navigation-menu-item`
-
-One entry of the bar. The kind follows from the markup:
-
-1. A safe `href` makes a **link item**: a native `<a>` with `aria-current="page"` while `current`
-   (otherwise `"false"`). Its `panel` slot is never displayed. This is decided from attributes alone,
-   so it is stable without JavaScript. An unsafe scheme such as `javascript:` renders a button.
-2. Otherwise the item is a native `<button type="button">`: a **disclosure trigger** when the `panel`
-   slot has content (it gains `aria-expanded` in both states, `aria-controls` pointing at the panel
-   in the same shadow root, and the caret), or a **plain button** with no disclosure state when it
-   does not — useful for single-page routers. Activating a plain button closes the open panel (and
-   collapses the collapsed list).
-
-The panel has no role and no name; the lists and links inside own the semantics. Outside an
-`lr-navigation-menu` the item works as a plain in-flow disclosure: no positioning, no overlay, no
-hover opening.
-
-**Properties:**
-
-- `accessibleLabel?: string` (attribute `aria-label`) — forwarded by presence to the link or button,
-  including an explicitly empty value.
-- `href: string = ''` — link URL, sanitized; a safe value makes a link item.
-- `target: string = ''` — native link target. Any non-empty value forces `noopener noreferrer`.
-- `rel: string = ''` — author tokens are kept, `opener` is dropped in any letter case, duplicates
-  collapse, and `noopener noreferrer` is added whenever `target` is set; nothing left omits the
-  attribute.
-- `current: boolean = false` (reflected) — on a link, `aria-current="page"`; on a trigger or plain
-  button, only the `base-current` part (a disclosure is not the page — mark the current link inside
-  the panel instead).
-- `open: boolean = false` (reflected) — whether the panel is shown. A write is refused silently only
-  when the item cannot disclose: it is a link item, or its `panel` slot is empty once slot content can
-  be inspected. Within one menu only one item is open at a time.
-
-**Methods:** `focus(options?)` and `click()` forward to the link or button.
-
-**Events:** `lr-toggle` — `detail: LyraNavigationMenuToggleDetail` (`{ open, source }`, where
-`source` is `'user' | 'programmatic' | 'peer'`, the same vocabulary as `lr-details`), not cancelable,
-fired after an accepted change renders and never for initial markup. `user` covers click, Enter,
-Space, hover, Escape, light dismiss, focus leaving and link activation; `programmatic` covers `open`
-writes, the menu's `close()`, a layout change and losing the panel content; `peer` means a sibling
-opened. Panel content such as `lr-details` also bubbles `lr-toggle`, so a delegated listener filters
-on `event.target.localName`.
-
-**Slots:** default — the label; `start`/`end` — adornments inside the link or button; `panel` —
-flyout content; `expand-icon` — replaces the caret (inert, `aria-hidden`).
-
-**CSS parts:** `base` (the `<a>` or `<button>`, also carrying `base-current` while `current` and
-`base-open` while its panel is open — state lives in the part name because only pseudo-classes may
-follow `::part()`), `base-current`, `base-open`, `start`, `label`, `end`, `expand-icon` and `panel`.
-
-**Custom properties:** `--lr-navigation-menu-item-padding-inline` (default `var(--lr-space-l)`),
-`--lr-navigation-menu-item-min-block-size` (default
-`var(--lr-form-control-height-m, var(--lr-theme-form-control-height-m, var(--lr-size-2-5rem)))`,
-never below `--lr-icon-button-size`), `--lr-navigation-menu-item-font-size` (default
-`var(--lr-font-size-m)`), `--lr-navigation-menu-item-font-weight` (default
-`var(--lr-font-weight-medium)`), `--lr-navigation-menu-item-hover-bg` (default
-`var(--lr-color-brand-quiet)`), `--lr-navigation-menu-item-hover-color` (default
-`var(--lr-color-brand)`), `--lr-navigation-menu-item-active-bg` (default a `color-mix()` of
-`--lr-color-brand-quiet` toward `--lr-color-mix-partner`), `--lr-navigation-menu-item-open-bg`
-(default `var(--lr-color-brand-quiet)`), `--lr-navigation-menu-item-active-color` (default
-`var(--lr-color-text)`), `--lr-navigation-menu-item-current-color` (default
-`var(--lr-color-brand)`), `--lr-navigation-menu-item-current-font-weight` (default
-`var(--lr-font-weight-semibold)`), `--lr-navigation-menu-panel-padding` (default `var(--lr-space-s)`),
-`--lr-navigation-menu-panel-max-inline-size` (default `var(--lr-size-48rem)`, also capped by the
-space the viewport leaves), `--lr-navigation-menu-panel-indent` (default `var(--lr-space-l)`,
-collapsed layout), `--lr-navigation-menu-show-duration` and `--lr-navigation-menu-hide-duration`
-(default `var(--lr-duration-fast)`), `--lr-navigation-menu-switch-duration` (default
-`var(--lr-duration-base)`), the shared floating-surface family `--lr-overlay-surface`,
-`--lr-overlay-border` (panels take the subtle edge tier), `--lr-overlay-radius` and
-`--lr-overlay-shadow-anchored`, and `--lr-positioning-strategy` (the floating panel is `fixed` by
-default). All are inline fallbacks, so they can be set on the item, on the menu or on any ancestor.
-The item does not take the `size` ladder.
-
-```html
-<script type="module">
-  import '@aceshooting/lyra-ui/components/layout/navigation-menu-item/navigation-menu-item.js';
-</script>
-
-<lr-navigation-menu-item>
-  Products
-  <ul slot="panel">
-    <li><a href="/analytics">Analytics</a></li>
-  </ul>
-</lr-navigation-menu-item>
-<lr-navigation-menu-item href="https://example.com/" target="_blank" rel="external">Example</lr-navigation-menu-item>
-```
-
-
-- **`components-layout-menubar-contracts`** — Typed pass-through menu selection.
-  Import: `@aceshooting/lyra-ui/components/layout/menubar/menubar.class.js`.
-  `LyraMenubarEventMap { 'lr-select': CustomEvent<MenuItemSelectDetail>; }`

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

@@ -34,6 +34,10 @@ disabled state.
 
 The inherited `--lr-input-*` theme inputs keep `lr-input`'s ancestor-theme precedence; the number
 subclass does not redeclare them on its host.
+Beside the stepper pair it keeps `lr-input`'s constrained-row allocation: the number field gives up
+its spare width first, down to a four-character floor while a unit is shown, so a short `end` unit
+stays whole (the `Narrow Measurement Unit` story). A stepper row with a unit therefore needs room
+for the steppers plus that floor; without a unit the field still yields entirely to the steppers.
 It also installs the shared six-tier size sheet: stepper-bearing rows follow the same rendered
 action-height ladder as `lr-input` instead of remaining at the default tier for every `size`.