@aceshooting/lyra-ui 14.0.0 → 14.1.0

package/llms/components/lr-include.md

@@ -29,6 +29,11 @@ include instance. Other navigation and resource attributes such as `href`, `src`
 cannot remain interactive; their wrappers are unwrapped when their ordinary children are safe,
 while elements such as inputs that have no passive content are removed.
 
+The same passive restrictions apply through nested template contents before a remote document is
+retained in the cache or a selected fragment becomes live. Template text and fragment selection
+remain supported at nested depths, including ordinary elements inside templates; permitted local
+anchors still resolve against per-instance rebased IDs.
+
 A bare primitive: no label/hint/error chrome, no implicit role, no computed accessible name, and no
 `aria-live` wrapper (the fragment can carry its own landmarks; wrapping the host would re-announce
 all of it on every load). The host always carries explicit `aria-busy="true"|"false"`: true while

package/llms/components/lr-ingestion-queue.md

@@ -19,6 +19,10 @@
 Controlled list of documents moving through an ingestion pipeline: stage badge, progress, chunk/
 embedding counts, retry attempts, errors, and retry/cancel requests. Never ingests anything itself.
 
+Nonstring failure details use the localized failed-stage label for row text and fresh failure
+announcements. Omitted details stay omitted. Formatting uses the effective locale, and historical
+failures remain silent on mount.
+
 **Properties:**
 
 - `items: IngestionQueueItem[] = []` (attribute: false) — `IngestionQueueItem { id: string;

package/llms/components/lr-input.md

@@ -21,6 +21,20 @@ 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`.
+
+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.
 
@@ -61,9 +75,9 @@ shared hit target (42px including the row border at the default theme); `l` and
 - `clearable: boolean = false` (reflected) — shows a localized clear action while a `text` or
   `search` input has a value; clearing preserves input focus
 - `withClear: boolean = false` (attribute `with-clear`) — Web Awesome's spelling of `clearable`;
-  either one shows the same action. Inherited by `lr-number-input`, where it is inert because that
-  type renders no clear action, and by `lr-time-input`, where it enables the segmented field's
-  localized clear action
+  either one shows the same action. Inherited by `lr-number-input` and `lr-native-time-input`,
+  where it is inert because their native types render no clear action. The separate segmented
+  `lr-time-input` implements its own `with-clear` action
 - `readonly: boolean = false` (reflected) — forwarded to the native input and disables clearing
 - `label: string = ''`
 - `hint: string = ''`
@@ -95,7 +109,7 @@ writes remain valid and read back as booleans. Markup uses `autocorrect="on"` /
   `type="time"`. On `lr-input` itself the `min`/`max` _attributes_ are number-converted, so a
   non-numeric bound only survives a direct property assignment; the declared type also admits a
   string so a subclass can narrow the attribute parsing to its own native type's literal form —
-  `lr-time-input` does exactly that. Inert for the other types
+  `lr-native-time-input` does exactly that. Inert for the other types
 - `minlength?: number` / `maxlength?: number` (attributes `minlength`/`maxlength`) — text-length
   bounds forwarded to the native input and reported as `validity.tooShort`/`validity.tooLong`.
   Apply to the text-bearing types (`text`, `search`, `email`, `password`); the platform ignores
@@ -203,8 +217,8 @@ than the icon-beside-label gap the ladder is tuned for. `--lr-input-radius` (def
 `--lr-form-control-radius`, its corner radius) is retunable the same way but _does_ follow the tier:
 the two tightest tiers take a smaller radius, since a 6px corner on a 20px-tall control reads as a
 lozenge. `pill` changes its private default to `--lr-radius-pill`; an inherited or direct public
-value still wins. `lr-number-input`/`lr-time-input` inherit both
-unchanged.
+value still wins. `lr-number-input`/`lr-native-time-input` inherit both
+unchanged. The separate segmented `lr-time-input` also consumes the documented input theme tokens.
 
 `--lr-input-fill` (default `transparent`) is the control row's background and
 `--lr-input-border-color` (default `var(--lr-color-border)`) its border color. `appearance` changes
@@ -298,8 +312,8 @@ submission must never shadow it: `lr-textarea` and `lr-code-editor` insert a new
 whole point of a multi-line surface; `lr-select`'s `role="combobox"` trigger opens the listbox (and
 then commits the active option), per the ARIA pattern; and `lr-date-picker` selects the focused day
 in the calendar grid. The controls that _do_ wire it are `lr-input` (and its `lr-number-input`/
-`lr-time-input` subclasses), `lr-combobox`, `lr-date-input`, `lr-phone-input`, `lr-token-input` and
-`lr-otp-input`.
+`lr-native-time-input` subclasses), the separate segmented `lr-time-input`, `lr-combobox`,
+`lr-date-input`, `lr-phone-input`, `lr-token-input` and `lr-otp-input`.
 
 ### Exact-height hatches — the one rule that applies to all of them
 

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

@@ -29,6 +29,10 @@ being patched in place. A container value that self-references (directly or thro
 renders as a leaf `Circular reference` marker (`data-type="circular"`) instead of recursing — no
 stack overflow on cyclic `data`.
 
+Removing `search` clears matches while retaining null property readback. Before any match is active,
+`searchPrevious()` selects the final match; later next/previous navigation wraps. Navigation may
+reopen the selected match’s ancestors while unrelated manual collapse remains intact.
+
 **Properties:**
 
 - `data: unknown` (attribute `false` — property-only, not settable via an HTML attribute)

package/llms/components/lr-kbd.md

@@ -20,6 +20,9 @@ A small chip representing a keyboard shortcut, rendering the platform-appropriat
 cross-platform modifier keys (⌘ on macOS, "Ctrl" elsewhere) from a single platform-neutral `keys`
 string. First-party invention (no Web Awesome equivalent).
 
+Removing `keys` safely clears the shortcut. Unknown tokens, including `constructor` and `__proto__`,
+render and name themselves verbatim; recognized modifiers keep their localized labels.
+
 **Properties:**
 
 - `keys: string = ''` — a `+`-separated sequence of tokens, e.g. `"mod+k"` or `"mod+shift+p"`.

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

@@ -21,6 +21,13 @@ neighborhood expansion, pinned nodes, path finding between pins, node selection,
 overlay. Composes `lr-graph`, `lr-graph-legend`, `lr-entity-card`, `lr-neighbor-list`,
 `lr-path-strip`, and `lr-popover.showAt()`.
 
+Removing `search-query` retains `null` property readback while clearing the search input, results
+and search dimming; an explicitly empty value remains empty and later queries work normally.
+Path-node `lr-entity-activate` is consumed by the explorer and enters the same selection, graph
+focus and details flow as other entity activations, emitting one `lr-selection-change`.
+`lr-relation-activate` continues to pass through unchanged. The canonical search event fields remain
+`query`, `matchCount`, and `matchCountExact`.
+
 **Properties:** (host-supplied data, identity-normalized before rendering)
 
 - `nodes: LyraGraphNode[] = []`, `links: LyraGraphLink[] = []`, `nodeTypes: LyraNodeTypeStyle[] = []`,

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

@@ -21,6 +21,13 @@ collected as three plain day/month/year number fields in the locale's natural or
 calendar popup. Uses the shared `FormAssociated` mixin; the submitted value is always canonical ISO
 8601 (`YYYY-MM-DD`), or `''` while any field is blank or the combination isn't a real calendar date.
 
+Host `aria-describedby` resolves external guidance onto the aggregate date fieldset and follows live
+target replacement/removal/reinsertion and document adoption. Each native field retains the
+component’s local hint and error guidance. Removed `label` and `hint` render as absent. Removing
+`day-label`, `month-label`, or `year-label` restores that field’s localized omitted default; an
+explicitly empty label remains empty. Own or fieldset disablement preserves each field’s resting
+paint on hover and press.
+
 **Properties:**
 
 - `value: string` — canonical `YYYY-MM-DD` or `''`. Assignment goes through a strict-ISO gate:

package/llms/components/lr-lite-chart.md

@@ -135,7 +135,10 @@ passthrough). Not a subclass of `LyraChart`.
   percentage cap from its own ResizeObserver result would create a shrinking feedback loop. The
   gutter remains at logical start under RTL. Unset keeps exactly 36px.
 - `barGapRatio?: number` (attribute `bar-gap-ratio`) — overrides the internal 0.2 `BAR_GROUP_GAP`
-  fraction of a category slot left as a gap between categories. Unset keeps the fixed 0.2.
+  fraction of a category slot left as a gap between categories. Unset keeps the fixed 0.2. Internal
+  grouped-bar gaps are bounded within the remaining category width so supported multi-series groups
+  retain positive, nonoverlapping bars for ratios below 1. A ratio of 1 reserves the whole slot as
+  gap and leaves zero-width bars.
 - `scale: 'linear' | 'sqrt' | 'logarithmic' = 'linear'` — `'sqrt'` (**bar type only**) maps a bar's
   value to height via `Math.sqrt(value / domainMax)` instead of the standard linear `niceDomain`
   fraction (mirroring `lr-heatmap`'s matrix-mode `sqrt` scale), so a skewed dataset's smaller bars
@@ -144,13 +147,20 @@ passthrough). Not a subclass of `LyraChart`.
   `'logarithmic'` is the base-10 value axis for data spanning several orders of magnitude, where a
   linear axis collapses everything below the maximum into the baseline. Unlike `'sqrt'` it applies
   to **bars, line points and gridlines alike**, since a log axis whose gridlines stayed linear
-  would misrepresent the plot. Its lower bound is the smallest *positive* datum rather than the
+  would misrepresent the plot. Value ticks use positive, bounded steps within that same domain:
+  powers of ten across whole decades, with positive numeric steps for spans smaller than a decade.
+  Both domain bounds remain represented, with space reserved between interior ticks and the bounds.
+  Linear and square-root tick selection is unchanged. Its lower bound is the smallest *positive* datum rather than the
   linear `lo`: `beginAtZero` defaults to true, so `lo` is normally `0`, which has no logarithm —
   deriving the floor from the data is what makes a 1…1000 series span three even decades instead of
   collapsing onto one. Values at or below that floor (including zero and negatives, which have no
   real logarithm) pin to the axis floor rather than producing `-Infinity` geometry, and a degenerate
   domain falls back to the linear fraction. `lr-chart`'s own `scaleType` is the Chart.js-backed
-  equivalent for the full charts.
+  equivalent for the full charts. With `stacked` and `'logarithmic'`, the finite sum of positive
+  raw values determines the log-mapped total extent; positive raw fractions partition that extent.
+  Nonpositive segments have zero natural log height. With `minBarHeight` unset, the stack stays
+  within the plot and its top agrees with the log axis. The square-root mode retains its separate
+  signed-total compression and proportional allocation, with linear gridlines.
 - `withoutValueAxis: boolean = false` (attribute `without-value-axis`) — suppresses gridlines and
   value-axis tick labels; x-axis category labels remain.
 - `selectedIndices: readonly number[] = []` (attribute: false) — names **source category indices**,
@@ -169,7 +179,8 @@ passthrough). Not a subclass of `LyraChart`.
   collection.
 - `minBarHeight?: number` (attribute `min-bar-height`) — optional minimum visible bar height for
   small non-zero values; finite input is capped at 1,000,000px before derived SVG geometry is
-  calculated
+  calculated. Authored floors can exceed the available plot height. Linear and logarithmic stacks
+  push subsequent segments along their signed pixel cursor; zero values remain unfloored.
 - `appendData(label, values, maxPoints?)` — appends one aligned category and optionally trims the
   oldest categories
 
@@ -185,6 +196,12 @@ markup. CSV rows cover the canonical record count — the maximum of `labels.len
 is never truncated or shifted. The method does not download a file; pair it with
 `lr-export-button` for download UX.
 
+Axis titles retain their complete `xLabel`/`yLabel` values and accessible names. In the browser,
+visible titles fit their plot allocation using the rendered SVG font; long titles end with an
+ellipsis. If even the ellipsis cannot fit, the title remains accessible without painting text.
+Fitting refreshes after rendering, allocation changes, inherited or host font changes, font loading,
+and reconnection. Server rendering retains the original title until browser layout is available.
+
 The axis gutter/title and y-axis labels mirror to logical start under RTL. Built-in mark summaries
 are complete localized templates and format values with `effectiveLocale`.
 

package/llms/components/lr-live-region.md

@@ -21,6 +21,9 @@ A throttled screen-reader announcement helper, split into a DOM-free coalescing
 and a real custom element that composes both. The two helpers are public — part of the curated,
 semver-covered `utilities/` surface documented in `llms/shared.md`, not internals:
 
+The Basic example’s controls announce through its sibling live region; both first and repeated
+messages appear in the visible log and the light-DOM announcement sink.
+
 ```ts
 import {
   Announcer,

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

@@ -23,6 +23,12 @@ plus `en` — kept live via `subscribeLyraLocaleRegistry()`. Built directly on `
 trigger-button/`aria-activedescendant` listbox technique, not composed from it — a plain closed
 list, no filter/free-text mode.
 
+Host `aria-describedby` references resolve onto the role=combobox trigger before its local error and
+hint guidance. The relationship tracks missing IDs, target replacement, removal/reinsertion,
+reconnect, and document adoption. Removing `label`, `hint`, or `error-text` safely omits that
+content while leaving native `null` property readback unchanged; explicit empty strings remain empty
+and later supplied text renders normally.
+
 Public `--lr-locale-picker-*` theme inputs stay undeclared on the host, so an ancestor theme
 wrapper can override size-tier fallbacks; a value set directly on the element still wins.
 

package/llms/components/lr-map.md

@@ -22,6 +22,14 @@ plus a peer-neutral `map` getter for common imperative operations. Its runtime v
 underlying MapLibre map. The component observes its own map-container allocation and calls the
 peer's `resize()` when that allocation changes.
 
+Markers and popups use the physical top-left origin required by MapLibre's projected transforms in
+both LTR and RTL. Their text and surrounding controls retain logical direction-aware layout.
+
+Live ancestor theme or token changes resolve the choropleth's stop colors and explicit or implicit
+step base color again, as well as its opacity. These are paint-only updates on the existing fill
+layer: the map instance, source, layer and viewport are preserved. Linear, logarithmic and step
+modes use the same expression semantics at initial render and after a theme change.
+
 **Properties:**
 
 - `center: [number, number] = [0, 0]`

package/llms/components/lr-markdown-core.md

@@ -25,6 +25,10 @@ this component's own module never imports or calls that function at all; it only
 `loadShikiHighlighterCore(languages)`, so a consumer importing this entry point instead of
 `markdown.js` gets a build genuinely free of shiki's full language table.
 
+Removing `content` clears the document and its empty-document tab stop, including while streaming.
+The property keeps Lit's `null` readback after removal; an explicitly empty attribute remains an
+empty string. Later source text renders normally.
+
 A fenced code block whose language isn't a key in `languages` always renders the plain-text fallback
 — there is no default/full-table highlighter here to fall back to, the same default (not degraded)
 rendering path as `<lr-code-block-core>`'s identical contract. A block that _is_ highlighted follows the

package/llms/components/lr-markdown.md

@@ -24,6 +24,10 @@ instance on a page shares one load. `heading`/`code`/`blockquote`/`table`/`link`
 rendered through a `marked` renderer override that injects `part="..."` attributes directly into the
 produced HTML in a single pass (no second DOM walk after insertion).
 
+Removing `content` clears the document and its empty-document tab stop, including while streaming.
+The property keeps Lit's `null` readback after removal; an explicitly empty attribute remains an
+empty string. Later source text renders normally.
+
 If an instance disconnects and reconnects before that shared promise settles, only the current
 connection applies the result and reparses; the stale connection callback is generation-guarded.
 
@@ -92,10 +96,10 @@ uses for its own `[part="body"]`.
   than overflowing past the HTML heading levels. `0` (the default) preserves the original
   `<h${token.depth}>` output
 - `streaming: boolean = false` (reflected) — marks the host `aria-busy="true"` while partial Markdown
-  is still arriving and lets consumers target `lr-markdown[streaming]`; content updates while it is
-  true are coalesced to at most one parse per animation frame, while the final `streaming=false`
-  update flushes the latest content immediately; busy state also remains true while parser
-  dependencies are loading
+  is still arriving and lets consumers target `lr-markdown[streaming]`. Both `lr-markdown` and
+  `lr-markdown-core` display accumulated plain text without parsing or highlighting while it is
+  true. Setting `streaming=false` parses and renders the latest complete content; busy state also
+  remains true while parser dependencies are loading
 - `highlightCode: boolean = true` (attribute `highlight-code`) — syntax-highlights fenced code
   blocks via the optional `shiki` peer. `true` (the default) upgrades every fenced block once the
   peer is available; set `false` to keep plain output even when `shiki` is installed. No effect

package/llms/components/lr-media-card.md

@@ -22,6 +22,10 @@ server-side-conversion state machine) and `lr-attachment-chip` (a pre-send queue
 upload progress). This component has neither concern; it only ever shows a `src` that's already
 final.
 
+Removing `mime-type` consumes the hint as absent and restores generic file detection unless `kind`
+explicitly selects a format. Property readback stays `null`; an explicit empty hint remains empty
+and later MIME values restore detection.
+
 **Properties:**
 
 - `src: string = ''` — the media URL. Always re-validated against a safe-scheme allowlist before
@@ -38,8 +42,7 @@ final.
   carve-out: an empty `alt` there still falls through to `filename`/the generic description, because
   an empty accessible name would leave an interactive player unnamed rather than mark it decorative.
 - `accessibleLabel: string | null = null` (attribute `aria-label`) — a declarative attribute names
-  the host as a whole while its nested button/link keeps a purpose-specific localized action name. A
-  property-only assignment can override the nested action when no host label is present. An explicit
+  the host as a whole while its nested button/link keeps a purpose-specific localized action name. A property-only assignment names the nested action and updates reactively when no host label is present, without creating a host attribute. An explicit
   empty string behaves like the unset `null` default — both fall through to the generated
   purpose-specific name. Image alt text and the native video's own purpose label remain independent;
   an explicitly empty host still leaves every interactive descendant named.

package/llms/components/lr-mention-popover.md

@@ -27,6 +27,11 @@ cross-root string IDREF is never left behind. Later localized result-count and a
 changes are announced once through the shared polite region; opening markup and unchanged state are
 silent.
 
+Forward native input keydown events to `handleKeyDown()` as usual. Events with `isComposing` or
+legacy `keyCode === 229` return false without preventing default, moving the active suggestion,
+selecting, or closing the popover. Removing `query` uses the unfiltered empty-query behavior while
+preserving null readback; an explicitly empty query remains empty.
+
 **Properties:**
 
 - `anchor?: HTMLElement` (attribute: false) — the element to position the popup relative to. A

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

@@ -22,6 +22,10 @@ The inline semantic menu mapped from Shoelace's `sl-menu`, plus its action-row e
 wrapping keyboard navigation, type-ahead, and one canonical selection event. It deliberately has no
 trigger, positioned popup, root open state, placement API, or overlay lifecycle.
 
+Removing or disabling the remembered active item repairs the roving stop without taking focus from
+outside controls or the menu's header/footer. If the changed item held actual focus, focus moves to
+a valid survivor or through the existing owner dismissal path when none remain.
+
 For a menu button or other anchored overlay, compose the semantic controller inside
 `<lr-dropdown>`:
 

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

@@ -25,9 +25,10 @@ name (`lr-menu-item` or `lr-dropdown-item`), not `instanceof`, so an adopted sam
 foreign-realm item remains enrollable. A label matches neither tag, is never enrolled in the roving
 tabindex, and can never become a focus stop; nothing on `<lr-menu>` has to know this element exists.
 
-To announce a _named group_ rather than a caption, wrap the labelled items in an element with
-`role="group"` and give it a matching `aria-label`. `aria-labelledby` pointing at this element's
-internals would not resolve — idrefs do not cross a shadow boundary.
+Keep selectable items directly assigned to the menu's default slot, or forward them through a
+slot, with `lr-menu-label` as a sibling visual caption. Arbitrary `role="group"` wrappers do not
+provide a supported menu-group API. `aria-labelledby` cannot reference this element's shadow
+internals because idrefs do not cross a shadow boundary.
 
 **Properties:** none. **Events:** none. **Slots:** default (the heading text).
 **CSS parts:** `base` (the heading row).

package/llms/components/lr-menu.md

@@ -22,6 +22,10 @@ The inline semantic menu mapped from Shoelace's `sl-menu`, plus its action-row e
 wrapping keyboard navigation, type-ahead, and one canonical selection event. It deliberately has no
 trigger, positioned popup, root open state, placement API, or overlay lifecycle.
 
+Removing or disabling the remembered active item repairs the roving stop without taking focus from
+outside controls or the menu's header/footer. If the changed item held actual focus, focus moves to
+a valid survivor or through the existing owner dismissal path when none remain.
+
 For a menu button or other anchored overlay, compose the semantic controller inside
 `<lr-dropdown>`:
 

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

@@ -34,6 +34,9 @@ becomes unavailable, focus moves to the nearest survivor or the stable toolbar,
 newer external focus move. Keyboard movement starts from the action that actually received the event,
 even after a controlled state write changed the remembered stop.
 
+ArrowLeft/ArrowRight/Home/End from a slotted feedback comment editor remain native editing keys.
+Roving navigation still operates on the actual toolbar and thumb actions.
+
 **Properties:** `controls: MessageActionControl[] = []` (attribute: false) —
 `MessageActionControl = 'copy' | 'regenerate' | 'edit' | 'feedback'` (exported here); which built-ins
 render, in that order. Duplicate names are omitted first-wins before rendering, roving focus, or

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

@@ -24,6 +24,10 @@ read-only display). Activating the pressed thumb while its detail panel is open
 activating the still-pressed thumb reopens it with the surviving draft. A thumbs-only control always
 uses the ordinary re-activate-to-clear toggle.
 
+Asynchronous finalization or reversion preserves focus on an outside control. Settlement retains the
+existing thumb/submit fallback when focus remains within the feedback or was lost as its pending
+controls became disabled.
+
 **Properties:** `rating: MessageFeedbackValue = null` (`'up' | 'down' | null`, reflected),
 `detail?: MessageFeedbackDetailConfiguration` (attribute: false) — one configuration with optional
 `reasons?: readonly { id, label }[]` and `commentable?: boolean`; omit it for thumbs-only feedback.

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

@@ -18,8 +18,9 @@
 
 Ordered renderer for provider-neutral `MessagePart[]`: text, reasoning, tool call/result, citation,
 attachment, data/widget, audio, and error parts can interleave without flattening stream order.
-Built-in text and reasoning Markdown receives each part's `state === 'streaming'` hint, coalescing
-parse/highlight work; replacing that same-id part with `state: 'complete'` flushes the final content.
+Built-in text and reasoning Markdown receives each part's `state === 'streaming'` hint and displays
+accumulated plain text without parsing or highlighting. Replacing that same-id part with
+`state: 'complete'` parses and renders the final content.
 Citation badge ranks are precomputed in one linear pass per render, rather than rescanning and
 allocating every preceding part for each citation in a citation-heavy or growing message.
 

package/llms/components/lr-model-select.md

@@ -26,6 +26,14 @@ element. First-party invention (no Web Awesome equivalent).
 Session-history/autofill restoration synchronously restores the model id and form entry without
 emitting `lr-change`.
 
+Removing `label`, `hint`, or `error-text` clears that optional copy in both catalog and free-text
+modes. Removed string properties retain `null` readback, and later assignments restore their
+content.
+
+Composing key events (`isComposing` or legacy `keyCode === 229`) remain with the catalog query or
+custom-value editor: they do not navigate options, commit a selection or custom value, or close the
+popup. Ordinary keyboard behavior resumes after composition.
+
 When `catalog`/`allowCustom` replaces a focused trigger with the free-text input or vice versa,
 focus follows the available replacement. If the new owner is disabled or inert, focus returns to
 the available element that led into the picker, or to the stable `form-control` owner when no

package/llms/components/lr-multi-split.md

@@ -21,6 +21,13 @@ auto-inserted between each adjacent pair. Panels participating in persistence ca
 nonempty, whitespace-stable `panel-id`; this business identity stays independent from the platform
 `id` attribute and is never rewritten.
 
+Feasible `minPx` floors also constrain flex shrinking after the divider target gutters take their
+allocation: a 600px split with a 40px divider can render panels of 300px and 260px. If the floors
+cannot fit, the remaining panel space is shared proportionally instead of overflowing. The budget
+follows allocation and the actual divider geometry, including font-relative tokens resolved in the
+divider's own font context. Panel font sizes do not change that gutter budget; stored percentages,
+initialization precedence, and resize event values retain their existing meaning.
+
 Granular import: `@aceshooting/lyra-ui/components/layout/multi-split/multi-split.js`.
 The Lyra-original v9 identity migration is mechanical: `lr-split` → `lr-multi-split`,
 `LyraSplit` → `LyraMultiSplit`, generic container authoring types → the corresponding
@@ -28,10 +35,10 @@ The Lyra-original v9 identity migration is mechanical: `lr-split` → `lr-multi-
 `--lr-split-*` hooks/storage keys → `--lr-multi-split-*`/`lr-multi-split:*`. The separate mirrored
 `lr-split-panel`, its `LyraSplitPanel` class, `SnapFunction`, and `SNAP_NONE` are unchanged.
 
-With a definite block size, each direct panel owns a native `overflow: auto` scroll surface and has
-`min-block-size: 0`, so long content stays inside the split rather than escaping into following
-content. Set `overflow` directly on an individual panel when its content needs a different scrolling
-surface.
+With a definite block size, each direct panel owns a native `overflow: auto` scroll surface.
+Unconstrained panels have a zero block minimum, so long content stays inside the split rather than
+escaping into following content. Set `overflow` directly on an individual panel when its content
+needs a different scrolling surface.
 
 **Properties:**
 
@@ -97,8 +104,10 @@ number; maxPx?: number; minPercent?: number; maxPercent?: number }`, index-align
   side resolves to the stricter one (larger for min, smaller for max) via a native CSS `max()`/`min()`
   in the rendered `clamp()` flex-basis. `sizes`, the `lr-resize` payload, and localStorage persistence
   stay percent-based regardless — only the effective drag/keyboard clamp bounds (and the rendered
-  `flex-basis`, via a native CSS `clamp()` so a constrained panel stays pinned between its bounds
-  across container resizes with no extra `ResizeObserver`) change for a constrained panel.
+  `flex-basis`, via a native CSS `clamp()` across container resizes) change for a constrained panel.
+  Pixel minimums also account for live divider dimensions. Bounds on neighboring panels remain
+  active during collapse transitions, including when constraints are updated from an
+  `lr-multi-split-collapse-change` handler.
 - `collapse: 'start'|'end'|'none' = 'none'` (reflected) — opt-in responsive collapse for one panel:
   `'start'`/`'end'` is a _logical_ position (RTL-aware, matching CSS logical properties — the panel at
   the document's visual leading/trailing edge, not a raw array index). `lr-multi-split` only owns the

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

@@ -22,6 +22,16 @@ forces its internal native input to `type="time"` on construction and reconnect,
 as numbers. Use it when the browser/OS picker is preferred; new `wa-time-input` migrations should
 use the segmented `lr-time-input` above.
 
+`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.
+
+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.
+
 **Inherits:** all public surface from `lr-input`.
 
 All `lr-input` properties, form methods, events, label/hint/error/start/end slots, parts, and theme

package/llms/components/lr-node-palette.md

@@ -22,6 +22,9 @@ at `lr-node-add`/`lr-palette-place`; the host mutates `nodes`. Fully decoupled f
 `lr-flow-canvas` (no `for` resolution, unlike the other three companions) — it only needs to agree
 with a `droppable` canvas on the `FLOW_PALETTE_MIME_TYPE` drag payload shape.
 
+For `lr-palette-place`, create the node and assign the updated array to the target canvas's public
+`nodes` property. Updating a captured local array alone does not update an already rendered canvas.
+
 **Properties:**
 
 - `items: LyraPaletteItem[] = []` (attribute: false) — `LyraPaletteItem { type: string; label: string;

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

@@ -32,7 +32,10 @@ are removed, and only inline base64 raster image sources render. Sanitized `imag
 is likewise network-silent and non-interactive: animation is removed and only same-document
 fragment references or inline base64 raster image references survive.
 Cells are virtualized through `lr-virtual-list`. `node-path` anchors resolve `path[0]` as a cell
-index; `fragment` anchors resolve a cell's own `id`. No execution, no kernels, no editing, no
+index; `fragment` anchors resolve a cell's own `id`. For cells with IDs, successful public anchor
+navigation scrolls the matching virtual row into the notebook allocation and applies active-cell
+paint using that same ID. Repeating a target scrolls back to it after manual scrolling.
+`maxHeight` also bounds the child virtual viewport. No execution, no kernels, no editing, no
 ipywidgets.
 
 **Properties:** `src: string = ''` — URL to fetch and parse as a notebook; ignored while `notebook`

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

@@ -20,6 +20,16 @@ A numeric field with the complete `lr-input` form, validation and native-editing
 own increment/decrement stepper pair. Its constructor and `connectedCallback()` both force
 `type = 'number'`; all inherited `lr-input` form and editing APIs remain available.
 
+`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.
+
+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.
+
 **Inherits:** all public surface from `lr-input`.
 
 The inherited `--lr-input-*` theme inputs keep `lr-input`'s ancestor-theme precedence; the number
@@ -30,7 +40,8 @@ action-height ladder as `lr-input` instead of remaining at the default tier for
 **Properties:** `size` (`2xs`…`xl`), `appearance`, `pill`, `autofocus`, `placeholder`, `readonly`,
 `label`, `hint`, `errorText`
 (`error-text`), `accessibleLabel` (`aria-label`), `autocomplete`, `spellcheck`, `autocapitalize`,
-`autoCorrect` (`autocorrect`), `inputMode` (`inputmode`), `enterKeyHint` (`enterkeyhint`), and
+`autocorrect` (boolean readback; accepts `boolean | 'off' | 'on'` writes), `inputMode`
+(`inputmode`), `enterKeyHint` (`enterkeyhint`), and
 `min`/`max`/`step` (the native numeric constraint validation), all inherited from `lr-input` with
 identical meaning. This component changes the mapped defaults to `appearance='outlined'`,
 `inputMode='numeric'`, and `step=1`. `clearable` (and its `with-clear` spelling),

package/llms/components/lr-option.md

@@ -21,6 +21,32 @@ Filterable single/multi-select combining a text input with a listbox. Mirrors th
 `<wa-combobox>` API under the `lr-` prefix. **Form-associated** (hand-rolled internals, not the
 shared `FormAssociated` mixin — see gotchas).
 
+Consumer writes on mounted options immediately update the owning picker and its submission,
+without changing the reset default or emitting picker input/change events. Owner synchronization
+does not echo as a consumer selected write.
+
+A mounted `option.selected` assignment updates the live picker value and form submission
+immediately, including deselection and equal-value writes; it emits no user input/change event.
+
+When `multiple` becomes false, the public value, live option flags, and popup `aria-selected` expose
+one selected occurrence. The retained multiple-selection history returns if multiple is enabled
+again without another selection write.
+
+Composing keyboard events (`isComposing` or legacy key code 229) remain with filter editing; they do
+not navigate, select/create a value, or dismiss the popup.
+
+Source options with `inert`, including inherited inertness, are unavailable through the popup. Live
+inert changes refresh row availability. Text, insertion, replacement, removal, slot
+reassignment/removal, and relevant attributes of `start`/`end`/`prefix`/`suffix` adornments refresh
+the corresponding cloned presentation; unchanged presentation retains its clone identity while
+filtering.
+
+Host `aria-describedby` resolves external descriptions onto the native combobox filter before local
+error/hint guidance. References track missing targets, replacement, removal/reinsertion, reconnect,
+and adoption. Removing `label`, `hint`, or `error-text` safely omits the content while leaving
+removed string properties at their native `null` readback; explicit empty strings remain supplied
+empty strings.
+
 **First-interaction registration.** Where initial-route weight is stricter than a static combobox
 registration allows, keep a labelled native `<input list>` as the working pre-JavaScript control
 and import only the granular combobox registration on its first focus. Copy the native value after
@@ -206,9 +232,12 @@ AbortSignal; limit: number }) => Promise<readonly ComboboxSourceRow[] | { rows,
 - `value: string | string[]` — a getter/setter: plain `string` in single mode, `string[]` in
   `multiple` mode
 - `customError: string | null` (attribute `custom-error`) — reflected consumer validation message
-- `selectedRows: ComboboxSourceRow[]` (read-only getter) — structured rows for the current
-  selection, including any opaque `data` payload supplied by an async source. Selected async rows
-  remain available after the query changes or a later source result no longer contains them
+- `selectedRows` (read: `ComboboxSourceRow[]`; write: `readonly ComboboxSourceRow[]`) — structured
+  rows for the current selection, including any opaque `data` payload supplied by an async source.
+  Reads return detached row snapshots. Writes select stable row values resolved against the
+  current or deferred source, dropping duplicate and detached values without emitting selection
+  events. Selected async rows remain available after the query changes or a later source result
+  no longer contains them
 - `selectionStart`, `selectionEnd`, and `selectionDirection` — selection getters/setters forwarded
   to the internal input
 
@@ -264,7 +293,9 @@ selection. It is the supported way to read that text; reaching into the shadow r
 `[part="combobox-input"]`'s value is not. Named `lr-filter` rather than `lr-input` precisely because
 `lr-input`'s detail on `<lr-input>` is the committed value, and the two must not share a name while
 carrying different strings. It fires for user edits only. Picking a row, `form.reset()`, dismissing
-the listbox, a programmatic `value` write, and `setRangeText()` blank the filter silently.
+the listbox, and a programmatic `value` write blank the filter silently. `setRangeText()` silently
+replaces the requested or selected native text range, synchronizes the resulting query and visible
+options, and refreshes an async source when present; it preserves the committed selection.
 Activating the clear button is a user edit: when a query existed it emits `lr-filter` with
 `value: ''` before the clear transaction finishes.
 `lr-show` and `lr-hide` report the start of listbox visibility transitions. `lr-show` is a

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

@@ -19,6 +19,16 @@
 A form-associated one-time-code field: several character segments that together hold one value.
 Mirrors `wa-otp-input`.
 
+Host `aria-describedby` references resolve onto the native control input before its local error and
+hint guidance. The relationship tracks missing IDs, target replacement, removal/reinsertion,
+reconnect, and document adoption. The decorative code segments do not receive a second copy of the
+descriptions.
+
+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.
+
 The segments are **presentational**. A single real `<input>` sits transparently across them and owns
 focus, selection and the value. It remains the native integration point for SMS autofill
 (`autocomplete` defaults to `one-time-code`), IME composition and mobile keyboards, and keeps the