@aceshooting/lyra-ui 13.0.1 → 14.1.0

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

@@ -130,7 +130,7 @@ Plus shared tokens otherwise.
 **Known gotchas:**
 
 - `title` and `open-button` are split into two separate parts (rather than one dual-part-name
-  element) because an exact-match `[part="..."]` CSS attribute selector — as this component's own
-  tests use — cannot match a multi-token `part` attribute value.
+  element) because an exact-match `[part="..."]` CSS attribute selector cannot match a multi-token
+  `part` attribute value.
 
 ---

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

@@ -26,6 +26,13 @@ plus an explicit oniguruma engine, seeded with _only_ the grammars in `languages
 importing this entry point instead of `code-block.js` gets a build genuinely free of shiki's full
 language table.
 
+Removing `code`, `language`, or `highlight-lines` treats that input as absent: source becomes empty,
+an absent language selects plain text, and attribute-based emphasis clears. Removal preserves Lit's
+`null` property readback; an explicitly empty attribute stays an empty string, and a later value
+resumes normal rendering. Highlighted gutter labels and locale-formatted line numbers follow live
+`.strings` and inherited or explicit locale changes. Unrelated updates retain the existing
+highlighted markup.
+
 A `language` value absent from `languages` always renders the plain `<pre><code>` fallback — there is
 no default/full-table highlighter here to fall back to, unlike `<lr-code-block>`'s dynamic-import
 path for an unmapped language. That fallback is the _default_ rendering path, not a degraded one,
@@ -56,7 +63,8 @@ toggle, the loading-skeleton behavior while the fine-grained highlighter resolve
   numbers for highlighted and plain output.
 - `highlightLines: string = ''` (attribute `highlight-lines`) — comma-separated 1-based inclusive
   line ranges (e.g. `"3-5,7"`) to visually emphasize. Declarative sugar over `highlights` — merges
-  with, and renders identically to, any `line-range` entries there.
+  with, and renders identically to, any `line-range` entries there. Malformed segments are ignored
+  while valid segments still apply.
 - `activatableLines: boolean = false` (attribute `activatable-lines`) — turns the
   (`lineNumbers`-gated) gutter into a roving-tabindex group of buttons emitting `lr-line-activate`.
   Has no effect while `lineNumbers` is unset. If controlled `code` shrinks while a line owns
@@ -70,8 +78,8 @@ toggle, the loading-skeleton behavior while the fine-grained highlighter resolve
 - `languages: Record<string, ShikiLanguageInput> = {}` (attribute: false) — grammar definitions this
   instance can highlight, e.g. `{ json: jsonGrammar }` (import from `shiki/langs/<name>.mjs`). Empty
   (the default) never highlights at all — every `language` renders the plain-text fallback.
-  Replacing the map while connected starts a new loading generation; an older map that settles
-  later cannot clear the current map's loading state or replace its highlighted output. For a
+  If `languages` changes while highlighting is loading, only results for the current map can update
+  the displayed code. For a
   TypeScript annotation, use `import type { ShikiLanguageInput } from
 '@aceshooting/lyra-ui/components/conversation/code-block/code-block-core.js'`; the type-only
   granular import emits no registration side effect.
@@ -80,7 +88,6 @@ toggle, the loading-skeleton behavior while the fine-grained highlighter resolve
 resolving to one) by scrolling its start line into view within `[part="body"]`; resolves `false`
 when the anchor isn't a `line-range`, the id isn't found, or the start line is out of bounds.
 `refreshTheme(): void` re-reads the resolved theme for syntax highlighting.
-`refreshTheme(): void` re-reads the resolved theme for syntax highlighting.
 Identical behavior to `<lr-code-block>`'s own method.
 
 **Events:** the same fulfilled-only `lr-copy`, generic `lr-error`, full `lr-copy-error`, cancelable
@@ -106,8 +113,12 @@ fallback separately.
 **Optional peer deps:** `shiki` (specifically its `shiki/core`, `shiki/engine/oniguruma`,
 `shiki/wasm`, and `shiki/themes/github-{light,dark}.mjs` subpaths — never `shiki`'s main entry point,
 which is what carries the ~200-language table this component exists to avoid). Building the
-fine-grained highlighter is cached per `languages` object identity (a `WeakMap`), so passing the same
-module-level `languages` constant on every render builds it only once.
+fine-grained highlighter is cached per `languages` object identity. A bounded weak cache also shares
+recently used equivalent, deeply frozen plain grammar maps, including the detached snapshots owned
+by separate component instances. Grammar contents and property/array order must agree completely;
+mutable or unusual inputs keep identity-only caching. Highlighters returned by the public loader
+can therefore be shared across equivalent frozen maps. Passing a stable module-level `languages`
+constant also avoids repeated component snapshots.
 
 ```ts
 import { html } from "lit";
@@ -128,7 +139,8 @@ const view = html`<lr-code-block-core
   added to `languages` will never highlight, no matter how common that language is elsewhere. Reach
   for `<lr-code-block>` instead if you need to support an open-ended set of languages without
   pre-declaring each one.
-- `languages` is keyed by object identity for caching purposes — pass a stable, module-level constant
-  (not a fresh object literal per render), or every render rebuilds its own fine-grained highlighter.
+- Pass a stable, module-level `languages` constant to avoid repeated snapshots on parent renders.
+  Equivalent frozen maps can share a recently used highlighter, but that bounded weak reuse is an
+  optimization: callers must not depend on distinct frozen map objects producing distinct cores.
 
 ---

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

@@ -17,13 +17,20 @@
 ## `lr-code-block`
 
 Fenced code display with optional lazy syntax highlighting and a copy button. First-party invention
-(no Web Awesome equivalent). It lazy-loads the optional peer dependency `shiki` (see
-`code-loader.ts`) for the actual tokenizing, and includes a compact GreyCat/GCL grammar because
+(no Web Awesome equivalent). It lazily loads the optional `shiki` peer for syntax highlighting and
+includes a compact GreyCat/GCL grammar because
 Shiki does not bundle one. It falls back to a plain `<pre><code>` when that peer isn't installed or
 `language` is unset/unrecognized. That
 fallback is the _default_ rendering path, not a degraded one: unhighlighted code is perfectly usable,
 and it's what every instance renders at zero extra bytes until shiki resolves.
 
+Removing `code`, `language`, or `highlight-lines` treats that input as absent: source becomes empty,
+an absent language selects plain text, and attribute-based emphasis clears. Removal preserves Lit's
+`null` property readback; an explicitly empty attribute stays an empty string, and a later value
+resumes normal rendering. Highlighted gutter labels and locale-formatted line numbers follow live
+`.strings` and inherited or explicit locale changes. Unrelated updates retain the existing
+highlighted markup.
+
 **Properties:**
 
 - `code: string = ''` — the raw source text
@@ -49,7 +56,8 @@ and it's what every instance renders at zero extra bytes until shiki resolves.
   numbers for both highlighted output and the plain-text fallback
 - `highlightLines: string = ''` (attribute `highlight-lines`) — comma-separated 1-based inclusive
   line ranges (e.g. `"3-5,7"`) to visually emphasize. Declarative sugar over `highlights` — merges
-  with, and renders identically to, any `line-range` entries there.
+  with, and renders identically to, any `line-range` entries there. Malformed segments are ignored
+  while valid segments still apply.
 - `activatableLines: boolean = false` (attribute `activatable-lines`) — turns the
   (`lineNumbers`-gated) gutter into a roving-tabindex group of buttons emitting `lr-line-activate`.
   Has no effect while `lineNumbers` is unset. If controlled `code` shrinks while a line owns
@@ -128,14 +136,10 @@ so it inherits: set it on the element, on an ancestor, or at the theme level.
 `:host` declaration) so it inherits, retinting just the highlighted-line background and leaving every
 other `--lr-color-warning-quiet` surface alone.
 
-**Optional peer deps:** `shiki` (lazy-loaded and cached once per page by `code-loader.ts`'s
-`loadShikiHighlighter()`, which builds a single `Highlighter` seeded with the bundled `github-light`/
-`github-dark` "dual themes" and _zero_ language grammars up front; each `language` a
-`<lr-code-block>` actually requests is loaded incrementally on first use via
-`loadShikiLanguage()`, and a language id that fails to load once is remembered and never retried. If
-`shiki` isn't installed, `loadShikiHighlighter()` resolves to `null` with a one-time `console.warn`
-and every instance falls back to plain text — install it with `pnpm add shiki` to enable
-highlighting).
+**Optional peer deps:** `shiki` — requested only when syntax highlighting is used and shared by
+code blocks on a page. Languages load on demand. If the peer or requested language is unavailable,
+every instance retains a readable plain-text fallback; install it with `pnpm add shiki` to enable
+highlighting.
 
 ```ts
 import { html } from "lit";
@@ -174,9 +178,8 @@ one deliberate exception to every other color being a `--lr-*` token.
 
 - `copyable` defaults to `true` and reflects — literal `copyable="false"` and a `.copyable=${false}`
   property binding both disable it; a `?copyable=${false}` boolean-attribute binding does not.
-- an in-flight per-language grammar load is guarded by an internal token so a `code`/`language` change
-  that arrives before a previous load resolves never applies a stale result — only the load matching
-  the _current_ `language` is ever rendered.
+- if `code` or `language` changes while highlighting is loading, only the result matching the
+  current values is rendered.
 - a malformed `code`/`language` combination that makes shiki's `codeToHtml()` throw falls back to
   plain text silently, not a blank code block.
 - the "Copied!" label appears only after clipboard fulfillment and reverts to "Copy" after 1500ms.

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

@@ -20,6 +20,15 @@ Long translated form chrome wraps within the host, while long source stays reach
 editor's internal scroll extent instead of widening the page. The `Narrow RTL long content
 (320px)` story covers both boundaries together.
 
+`form.reset()` restores the default value and pristine interaction feedback. Required and custom
+validity constraints remain; a required-empty editor is still invalid. Removing `label`, `hint`, or
+`error-text` treats the removed value as absent for rendering while retaining native
+attribute-removal property readback.
+
+Host `aria-describedby` references resolve in the host root onto the native textarea before its
+local error/hint guidance. Target replacement, removal, reinsertion, unresolved IDs, reconnect, and
+adoption keep that relationship current.
+
 Dependency-free, form-associated multiline code editor built around a native textarea, with an
 optional line-number gutter. No syntax highlighting: `language` is metadata only.
 
@@ -29,9 +38,11 @@ optional line-number gutter. No syntax highlighting: `language` is metadata only
   `data-language`; purely a consumer-reachable styling/metadata hook, nothing tokenizes the text
 - `lineNumbers: boolean = true` (attribute `line-numbers`, reflected) — renders the `gutter` part,
   one row per `\n`-separated line
-- `tabSize: number = 2` (attribute `tab-size`) — spaces inserted per Tab press, and the textarea's
-  inline `tab-size`. Sanitized on assignment to a finite integer clamped to `1..16`, so a
-  `NaN`/`Infinity` value can neither empty the insert nor throw out of `String.repeat()`
+- `tabSize: number = 2` (attribute `tab-size`) — spaces inserted per Tab press and the tab width
+  shared by the native textarea and text measurement. Explicit property/attribute assignment wins
+  over `--lr-code-editor-tab-size`; otherwise the token controls the rendered tab width. Sanitized
+  on assignment to a finite integer clamped to `1..16`, so a `NaN`/`Infinity` value can neither
+  empty the insert nor throw out of `String.repeat()`.
 - `label: string = ''`, `hint: string = ''`, `errorText: string = ''` (attribute `error-text`),
   `placeholder: string = ''`
 - `readonly: boolean = false` (reflected) — also disables Tab indentation
@@ -47,8 +58,10 @@ optional line-number gutter. No syntax highlighting: `language` is metadata only
   `lr-textarea`/`lr-input`/`lr-select`, accepting both spellings of every tier (`2xs`/`xs`/`s`/`m`/
   `l`/`xl` and `small`/`medium`/`large`). Governs the gutter's and textarea's padding and font size,
   plus the editor frame's minimum block size.
-- `wrap: 'off' | 'soft' | 'hard' = 'off'` — native textarea wrapping; `'off'` (the default) makes
-  the `editor` part the single horizontal scroll viewport. `hard` uses the owner realm's native
+- `wrap: 'off' | 'soft' | 'hard' = 'off'` — native textarea wrapping. `'off'` (the default) makes
+  the `editor` part the single horizontal scroll viewport. Soft/hard text wraps within the editor
+  allocation, with the caret and logical line-number gutter following the wrapped lines as the
+  allocation changes; the editor frame owns scrolling. `hard` uses the owner realm's native
   textarea serializer, so FormData receives platform-equivalent `cols` wrapping while the live
   `value` remains unwrapped.
 - `spellcheck: boolean = false` — off by default for code, and parsed with a string-aware converter
@@ -70,6 +83,8 @@ optional line-number gutter. No syntax highlighting: `language` is metadata only
 emitting an event), and `scrollPosition()` / `scrollPosition({top?,left?})`. The `input` getter
 returns the owned native textarea after render. `selectionStart`, `selectionEnd`, and
 `selectionDirection` use native nullable sentinels before that surface exists.
+`scrollPosition()` reads or writes `[part="editor"]`'s top/left offsets: the gutter and caret share
+that single scroll owner rather than a private textarea scroll position.
 The native textarea receives the actual `required` state. Its `aria-invalid` is true whenever
 visible property/slotted error chrome exists, or after interaction while native validity fails;
 showing error chrome alone does not mutate `ElementInternals` validity.

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

@@ -21,6 +21,15 @@ opens a popover holding a saturation/brightness grid, a hue slider, an optional
 field accepting any parseable CSS colour, an optional predefined palette, and — where the browser
 supports it — a screen eyedropper.
 
+Host `aria-describedby` references resolve in the host's root and precede the trigger's local error,
+hint and current-value guidance. Same-ID target replacement, removal, reinsertion, reconnection and
+document adoption keep those relationships current. Inline mode has no trigger.
+
+Own or fieldset disablement discards an unfinished native text draft without committing it and
+blocks palette/format actions immediately, including before disabled rendering settles. A valid
+enabled draft still commits on normal blur or Enter. Format changes retain their existing
+programmatic event silence. Pointer and eyedropper cancellation behavior remains unchanged.
+
 **Rewritten in 8.0.0.** It used to wrap a bare native `<input type="color">`; it is now a real
 picker built from the pieces above. Two consequences for existing code:
 

package/llms/components/lr-combobox.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-command-palette.md

@@ -20,6 +20,10 @@ Searchable application command menu. Renders nothing at all while closed. Uses t
 overlay infrastructure as `lr-dialog` (focus-trapping Tab, Escape dismissal, backdrop-click
 dismissal, ref-counted document scroll lock).
 
+Valid string keywords still participate in search alongside the command's label, description, and
+group. Unsafe keyword entries are skipped without invoking accessors, and selection returns the
+original command object.
+
 **Properties:**
 
 - `open: boolean = false` (reflected) — after the initial silent render, property and attribute

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

@@ -19,6 +19,9 @@
 A compact commit summary (subject, author/time, diffstat, per-file changes) that links file rows out
 to a diff view.
 
+Removing the `message` attribute clears the displayed subject and body; the property retains the
+normal `null` readback of a removed string attribute.
+
 **Properties:** `hash: string = ''`, `message: string = ''`, `author: string = ''`, `timestamp?:
 number` (attribute: false, epoch milliseconds), `files: CommitFileChange[] = []` (attribute: false) —
 `CommitFileChange { path: string; additions: number; deletions: number; status?: GitStatus }`

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

@@ -19,6 +19,13 @@
 Side-by-side A/B output comparison with a winner vote (LMSYS-arena / LangSmith-pairwise style): two
 slotted panes, a vote bar, synchronized reading.
 
+Disabled vote buttons retain their resting colors during hover and press, including an existing
+selected vote.
+
+At narrow widths, stacked response panes size to their content up to
+`--lr-compare-panel-max-height`. Short responses remain fully readable; longer responses retain the
+configured height limit and scrolling.
+
 **Properties:** `labelA: string = ''` (attribute `label-a`) and `labelB: string = ''` (attribute
 `label-b`) — pane headings. `vote: 'a' | 'b' | 'tie' | 'both-bad' | null = null` (reflected) — the
 recorded winner, host-writable to reflect a previously-recorded vote back. `itemId: string = ''`

package/llms/components/lr-condition-builder.md

@@ -19,6 +19,11 @@
 Composable flat condition builder for tabular or dashboard data: condition rows combined with an
 AND/OR combinator, distinct by name and model from `lr-graph-query-builder`.
 
+A field or operator select choice updates the builder once and emits one `lr-input` carrying the
+complete `{ value: ConditionBuilderValue }` snapshot. Child native `input`/`change`, prefixed value
+aliases and listbox show/hide lifecycle events remain inside those pickers. Programmatic `value`
+assignments remain silent.
+
 **9.0 migration:** `lr-query-builder` / `LyraQueryBuilder` / `QueryBuilder*` were renamed without
 aliases to `lr-condition-builder` / `LyraConditionBuilder` / `ConditionBuilder*`. Update the tag,
 granular import path, class/type imports, selectors, and framework bindings together.

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

@@ -20,6 +20,9 @@ A selectable row representing one chat session in a history sidebar list. Usable
 `renderItem()` payload of `<lr-virtual-list>`; has no dependency on that (or any) other component.
 First-party invention (no Web Awesome equivalent).
 
+Inline rename keeps IME composition keys in the editor; ordinary Enter commits and Escape cancels
+after composition.
+
 **Properties:**
 
 - `conversationId: string = ''` (attribute `conversation-id`) — stable domain identity carried by

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

@@ -21,6 +21,12 @@ A standalone copy-to-clipboard affordance for a plain text `value` or a source e
 settles; a consumer-provided default-slot trigger can replace that button. The component takes no
 positioning opinion of its own.
 
+The CopyFailure example temporarily supplies a denied clipboard operation during click capture,
+including after a held pointer press, then restores the original own property descriptor or removes
+its temporary override when the clipboard was inherited. Pointer gestures that end without a click
+do not install an override. This example does not change the clipboard contract of ordinary copy
+buttons.
+
 **Properties:**
 
 - `value: string = ''` — the plain text to copy.
@@ -54,7 +60,10 @@ positioning opinion of its own.
 **Methods:** `focus(options?)`, `blur()` and `click()` forward to the active built-in or custom
 trigger. `getToolbarActions(): readonly LyraToolbarAction[]` implements the public logical-toolbar
 provider protocol with one stable action whose id is `copy`; its focus, roving tab index, disabled
-state, and composed-event matching follow the active trigger without exposing that node.
+state, and composed-event matching follow the active trigger without exposing that node. Its
+`releaseTabIndex()` action method lets a parent stop managing its tab index on disconnect, adoption,
+trigger replacement, and parent departure: an untouched author-supplied `tabindex` is restored,
+while a newer author change is never overwritten.
 
 **Events:**
 

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

@@ -19,6 +19,11 @@
 Responsive, keyboard-accessible controlled widget grid. It positions layout entries and emits
 move, resize, collision, and layout-change requests; the host owns persistence and applies updates.
 
+Pointer move and resize gestures measure the rendered column/row pitch, including the gutter, so
+movement by four painted tracks proposes four logical columns in either LTR or RTL. Row-height and
+gap overrides also govern vertical pointer snapping. The component continues to emit controlled
+layout proposals; the caller accepts them by assigning `layout`.
+
 **Properties:** `layout: readonly LyraDashboardCell[] = []` (attribute: false, never mutated by the component),
 `columns: number = 12`, `rowHeight: number = 80` (px, also the row snap pitch), `gap: number = 8`
 (px, both axes), `collision: 'reject' | 'push' | 'overlap' = 'reject'`, `cellsDraggable: boolean = false`

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

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 47 parts, 21 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 47 parts, 27 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`
 
 ---
@@ -20,6 +20,12 @@ Virtualized client/server data grid with multi-sort, column filters, global sear
 trees, row details, paging, pinning, resizing, reordering, selection, copy, and CSV export. Import
 the granular registration module when the root bundle is not already loaded:
 
+Repeated references to an admitted root row appear once in processed rows, pagination, facets, and
+CSV, matching rendered canonical identity. The retained occurrence remains the original caller-owned
+record. Clicking a supported interactive descendant, including a native control inside its open
+shadow root, runs that control without also emitting `lr-cell-click`. Passive cell content continues
+to activate the cell.
+
 ```js
 import "@aceshooting/lyra-ui/components/data/data-grid/data-grid.js";
 ```
@@ -114,7 +120,11 @@ are `text`, `equals`, `number-range`, `date-range`, `set`, `includes-any`, and `
 
 **Methods:**
 
-- `autoSizeColumn(columnId)`, `autoSizeColumns()`, and `sizeColumnsToFit()` manage measured widths.
+- `autoSizeColumn(columnId)` and `autoSizeColumns()` manage measured widths. `sizeColumnsToFit()`
+  reserves visible effective zero-flex column widths and selection-control allocation before
+  dividing the remaining width proportionally among flexible columns. Fixed widths are preserved;
+  min/max clamps still apply, and an all-fixed grid is unchanged. Maximum clamps can leave unused
+  space, while incompatible minimum widths can still overflow.
 - `collapseAllRows()`, `collapseRow(key)`, `expandAllRows()`, and `expandRow(key)` update expansion
   without emitting the user-only row events.
 - `copySelectedRows(options?: DataGridCopyOptions)` copies selected rows (or all processed rows
@@ -236,7 +246,16 @@ body-cell text, `--lr-data-grid-cell-link-color` (default `var(--lr-color-brand)
 anchors, and `--lr-data-grid-cell-link-hover-color` (default
 `var(--lr-data-grid-cell-link-color, var(--lr-color-brand))`) controls those anchors on hover,
 focus-visible, and active interaction. Set the link color to `revert` to restore the user-agent
-default.
+default. Six independent interaction-background hooks preserve those state boundaries:
+`--lr-data-grid-control-hover-background` and `--lr-data-grid-control-active-background` theme
+search, toolbar, pager, and resize controls; `--lr-data-grid-page-size-active-background` themes
+the page-size selector when pressed; `--lr-data-grid-row-active-background` themes pressed data
+rows; and `--lr-data-grid-sortable-header-hover-background` and
+`--lr-data-grid-sortable-header-active-background` theme sortable header states. They default to
+live `color-mix()` values of the effective grid accent and transparent, using the corresponding
+`--lr-color-mix-hover` or `--lr-color-mix-active` token (the page-size pressed state intentionally
+uses the hover mix), so an accent override remains coherent while each surface can still be
+overridden independently.
 
 ```html
 <lr-data-grid

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

@@ -34,8 +34,9 @@ rather than a phantom success, and a header-row target scrolls with the same
 `max-height`), and `scrollMode: DatasetViewerScrollMode = 'self'` (attribute `scroll-mode`,
 reflected). Invalid CSS `max-height` values, declaration breaks, and `url()` are ignored.
 `scrollMode='self'` preserves contained horizontal scrolling and applies `maxHeight`.
-`scrollMode='page'` drops both the overflow container and height cap so an uncapped sticky header
-uses the page scrollport; the explicit tradeoff is that a wide dataset can overflow its host.
+`scrollMode='page'` removes intervening scroll containers and the height cap, so a populated table's
+sticky header follows the page scrollport while rows continue below it. The border and rounded
+header corners remain; a wide dataset can overflow its host in page mode.
 Unsupported attribute and untyped property values normalize to `'self'`.
 Host `aria-label` names the table by attribute presence, including an explicitly empty value;
 `name` and the localized row-count caption are fallbacks. The same computed name (host `aria-label`,

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

@@ -21,8 +21,37 @@ Mirrors the `<wa-date-picker>`/`<wa-date-input>` 3.11 public API under `lr-`. Bo
 components are **experimental since 3.8**. Values use ISO 8601: `YYYY-MM-DD` (single) or
 `YYYY-MM-DD/YYYY-MM-DD` (range).
 
-The ISO model is proleptic Gregorian in every locale, including years `0000`–`0099` (no JavaScript
-`Date` 1900 remap). Month/day names and visible day/week digits follow the effective locale while
+For `lr-date-input`, host `aria-describedby` targets resolve in the host's root and describe the
+native combobox input through element references, before its existing error and hint descriptions.
+Replacement, removal, reinsertion, newly resolved IDs, reconnect, and adoption update those
+relationships. Removing `label`, `hint`, or `error-text` safely omits that copy while preserving
+`null` property readback; later supplied values render normally.
+
+`lr-date-input`'s `clearLabel`, `openLabel`, and `dialogLabel` retain their initial defaults (`''`,
+`''`, and `'Choose date'`). Omitted labels localize; explicitly supplied text, built-in English
+labels, and empty strings win over `.strings`. Attribute removal restores localization while
+preserving `null` readback. The composed calendar applies the same range endpoint and
+inclusive-length admission rules as the standalone picker.
+
+An authored host `aria-label` names an enclosing calendar group. Individual month and selection
+grids retain their distinct generated period names; changing or removing the purpose label updates
+the group without changing a caller-authored host role. Removing the `value` attribute renders an
+empty selection safely while preserving `null` readback; a subsequent valid value works normally.
+
+Live constraints repair roving state without moving focus from an unrelated control. If a focused
+cell becomes unavailable, focus recovers onto an enabled cell. Explicit distant bounds seed the
+bounded automatic search within the permitted domain; a genuinely empty domain has no enabled roving
+stop. Selected day and range-endpoint buttons retain their foreground/background pairing during
+hover and press; author state-token overrides remain available. Month/year/decade state buttons
+retain the common typography, padding, border reset, and minimum action size.
+
+The `calendar-core.ts` helper `formatISO()` returns an empty string for invalid dates or years
+outside `0000`–`9999`, so generated ISO anchors never advertise an unsupported signed or five-digit
+year.
+
+The ISO model is proleptic Gregorian in every locale and supports years `0000`–`9999`, including
+`0000`–`0099` without JavaScript's `Date` 1900 remap. Navigation anchors remain within that domain;
+moving past either boundary leaves a valid roving stop and does not change the selected value. Month/day names and visible day/week digits follow the effective locale while
 formatters explicitly select the Gregorian calendar. `lr-date-input` uses locale `formatRange()`
 for range presentation and normalizes locale digits plus bidi marks before parsing, so its own
 Arabic/Persian display round-trips to the same ISO value.
@@ -50,12 +79,20 @@ Inline month-grid calendar, not form-associated (used standalone or embedded ins
   tell them apart. A reversed preset normalizes; a malformed one is ignored rather than clearing the
   current value, so a bad entry in a config-driven list never reads as "the user picked nothing".
   Non-array runtime assignments normalize to the empty collection, and null/non-object entries in
-  an otherwise valid array are omitted from the rendered row rather than aborting the calendar.
+  an otherwise valid array are omitted from the rendered row rather than aborting the calendar. Empty and
+  whitespace-only labels are also omitted, preserving named siblings. Explicit endpoints clamp to
+  `min`/`max` before admission. Both endpoints must be selectable, and the inclusive length must
+  satisfy `minRange`/`maxRange`; invalid outcomes render disabled and do not emit value events.
+  Interior dates need not all be enabled. A same-day manual completion obeys those same inclusive
+  length limits. Long preset labels wrap in narrow allocations, including unbroken text and RTL.
   The active button carries `aria-pressed="true"` and `data-active`. Deliberately the same
   `label`/`start`/`end` shape as `<lr-time-range>`'s `TimeRangePreset`, so the library has one
   preset vocabulary rather than two — the only difference is the unit (ISO dates, not numbers)
 - `appliedPreset: LyraDateRangePreset | undefined` (read-only, new in 11.1.0) — the preset whose
-  button produced the current `value`, or `undefined` when the range was picked by hand. Read it
+  button produced the current `value`, or `undefined` when the range was picked by hand, cleared, or changed externally.
+  `clear()` removes identity before synchronous `input`/`change` listeners run; an external value
+  change removes identity silently. An accepted preset retains its exact caller-owned source
+  identity through its own update. Read it
   inside your own `change`/`input` handler. It exists because a dashboard filter has to persist
   *which* preset is active rather than the pair it froze to: "Last 7 days" must still mean the last
   7 days after tomorrow's reload. That fact is not recoverable from `value` — re-deriving it by
@@ -91,8 +128,11 @@ Inline month-grid calendar, not form-associated (used standalone or embedded ins
 - `weekdayFormat: 'narrow'|'short'|'long' = 'short'` (attribute `weekday-format`, reflected)
 - `withOutsideDays: boolean = false` and `withWeekNumbers: boolean = false` (reflected)
 
-Lyra retains the additive `previousLabel`/`nextLabel` localized accessible-label overrides and
-the `selection` range getter.
+Lyra retains the additive `previousLabel`/`nextLabel` accessible-label overrides and the `selection`
+range getter. Their initial readback remains `'Previous month'` and `'Next month'`; omitted labels
+localize, while explicit text, the built-in English labels, and empty strings win over locale and
+`.strings` copy. Removing either label attribute restores localized omission while preserving
+`null` property readback.
 
 **Methods:** `clear()`, `focus(options?)`, `goToToday()`, and
 `goToDate(date: string | Date)`. Valid navigation dates are clamped to `min`/`max`; invalid values
@@ -388,6 +428,10 @@ and `dateTimeFormat(locale, options)`.
   currently-selected paint for a `presets` quick-range button. Defaults are
   `var(--lr-color-brand-quiet)`, that hover colour mixed by `--lr-color-mix-active`, and
   `var(--lr-color-brand)` respectively.
+- `--lr-date-picker-preset-selected-border` (default `var(--lr-color-brand)`) and
+  `--lr-date-picker-preset-selected-color` (default `var(--lr-color-on-brand)`) independently
+  theme a selected preset's border and foreground; the selected background token controls only its
+  background.
 - `--lr-date-picker-title-hover-color`, `--lr-date-picker-title-active-color`,
   `--lr-date-picker-title-active-bg`, and `--lr-date-picker-title-active-radius` — Month-title
   hover/press paint and pressed shape; defaults to brand, brand, brand-quiet, and