@aceshooting/lyra-ui 13.0.1 → 14.1.0

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

@@ -20,6 +20,11 @@
 An expand/collapse hierarchy (document/graph navigation tree). Mirrors `wa-tree`/`wa-tree-item` and
 `sl-tree`/`sl-tree-item`.
 
+An otherwise unnamed data row receives its stable `id` as a semantic name. Usable `accessibleLabel`,
+visible label, description, badge content and explicit host naming retain precedence; the fallback
+changes neither visible content nor installed data. Blank visible labels remain supported.
+Declarative items receive no automatic ID fallback.
+
 **Renamed in 8.0.0 — breaking:** the child element is `<lr-tree-item>` (class `LyraTreeItem`), not
 `<lr-tree-node>`/`LyraTreeNode`. It was the only child element in the library whose tag diverged
 from both upstreams, so `wa-tree-item`/`sl-tree-item` markup had nothing to rename to. The shared
@@ -72,9 +77,10 @@ deeply-nested node's own shadow root still reaches it).
 - `data: readonly LyraTreeNodeData[] = []` (attribute: false) — the object child model; ignored
   while any author-written `<lr-tree-item>` child is present. Assignment installs a detached,
   recursively frozen snapshot: mutate caller data only before assignment, then reassign after
-  changes. Normalization accepts at most 1,000 valid nodes and 64 descendant levels, never invokes
-  caller accessors, and exposes `dataTruncated = true` when malformed or over-budget input was
-  omitted. Collapsed branches do not instantiate descendants; disclosure projects only normalized
+  changes. Normalization accepts at most 1,000 valid nodes and 64 descendant levels, and lazily
+  inspects at most 10,000 root/child array positions globally in depth-first order. It never
+  invokes caller accessors and exposes `dataTruncated = true` when malformed or over-budget input
+  was omitted or the inspected-position ceiling was reached. Collapsed branches do not instantiate descendants; disclosure projects only normalized
   children while `aria-setsize` preserves the declared sibling count. `LyraTreeNodeData` is
   `{ readonly id: string; readonly label: string; readonly children?: readonly LyraTreeNodeData[];
 readonly selected?: boolean; readonly disabled?: boolean; readonly lazy?: boolean; readonly
@@ -88,7 +94,7 @@ LyraVariant; readonly label?: string }`. `badges` renders tone-mapped chips in o
   author-supplied host `aria-label` takes precedence by presence and is never overwritten or
   removed by later object refreshes; removing the author attribute restores the current data name.
   `id` is the event, roving-focus, reconciliation, and reorder identity and must be unique across
-  the complete reachable hierarchy; malformed/blank rows and later duplicates are omitted as described above
+  the complete reachable hierarchy; malformed rows, blank IDs and later duplicates are omitted as described above
 - `selection: 'single'|'multiple'|'leaf'|'leaf-multiple' = 'single'` — self-managed selection for
   both child models. `single` selects one item; `leaf` selects one loaded leaf; `multiple` displays
   checkboxes and cascades through enabled descendants; `leaf-multiple` applies that cascade only
@@ -213,7 +219,8 @@ when assigned):
 - `isDisabled: boolean` — `item.disabled` in the data model, the `disabled` property in the
   declarative one
 - `nodeLabel: string` — this item's spoken name, used for the tree's reorder announcements: a host
-  `aria-label` is authoritative in both models; otherwise `item.accessibleLabel || item.label` in
+  `aria-label` is authoritative in both models
+  (including the component-owned stable-ID fallback for otherwise unnamed data rows); otherwise `item.accessibleLabel || item.label` in
   the data model, or flattened accessibility-visible slotted label text (nested items excluded)
   followed by the `label` fallback in the declarative one. Direct and forwarding-slot
   text/ARIA/visibility mutations update the name

package/llms/components/lr-tree.md

@@ -20,6 +20,11 @@
 An expand/collapse hierarchy (document/graph navigation tree). Mirrors `wa-tree`/`wa-tree-item` and
 `sl-tree`/`sl-tree-item`.
 
+An otherwise unnamed data row receives its stable `id` as a semantic name. Usable `accessibleLabel`,
+visible label, description, badge content and explicit host naming retain precedence; the fallback
+changes neither visible content nor installed data. Blank visible labels remain supported.
+Declarative items receive no automatic ID fallback.
+
 **Renamed in 8.0.0 — breaking:** the child element is `<lr-tree-item>` (class `LyraTreeItem`), not
 `<lr-tree-node>`/`LyraTreeNode`. It was the only child element in the library whose tag diverged
 from both upstreams, so `wa-tree-item`/`sl-tree-item` markup had nothing to rename to. The shared
@@ -72,9 +77,10 @@ deeply-nested node's own shadow root still reaches it).
 - `data: readonly LyraTreeNodeData[] = []` (attribute: false) — the object child model; ignored
   while any author-written `<lr-tree-item>` child is present. Assignment installs a detached,
   recursively frozen snapshot: mutate caller data only before assignment, then reassign after
-  changes. Normalization accepts at most 1,000 valid nodes and 64 descendant levels, never invokes
-  caller accessors, and exposes `dataTruncated = true` when malformed or over-budget input was
-  omitted. Collapsed branches do not instantiate descendants; disclosure projects only normalized
+  changes. Normalization accepts at most 1,000 valid nodes and 64 descendant levels, and lazily
+  inspects at most 10,000 root/child array positions globally in depth-first order. It never
+  invokes caller accessors and exposes `dataTruncated = true` when malformed or over-budget input
+  was omitted or the inspected-position ceiling was reached. Collapsed branches do not instantiate descendants; disclosure projects only normalized
   children while `aria-setsize` preserves the declared sibling count. `LyraTreeNodeData` is
   `{ readonly id: string; readonly label: string; readonly children?: readonly LyraTreeNodeData[];
 readonly selected?: boolean; readonly disabled?: boolean; readonly lazy?: boolean; readonly
@@ -88,7 +94,7 @@ LyraVariant; readonly label?: string }`. `badges` renders tone-mapped chips in o
   author-supplied host `aria-label` takes precedence by presence and is never overwritten or
   removed by later object refreshes; removing the author attribute restores the current data name.
   `id` is the event, roving-focus, reconciliation, and reorder identity and must be unique across
-  the complete reachable hierarchy; malformed/blank rows and later duplicates are omitted as described above
+  the complete reachable hierarchy; malformed rows, blank IDs and later duplicates are omitted as described above
 - `selection: 'single'|'multiple'|'leaf'|'leaf-multiple' = 'single'` — self-managed selection for
   both child models. `single` selects one item; `leaf` selects one loaded leaf; `multiple` displays
   checkboxes and cascades through enabled descendants; `leaf-multiple` applies that cascade only
@@ -213,7 +219,8 @@ when assigned):
 - `isDisabled: boolean` — `item.disabled` in the data model, the `disabled` property in the
   declarative one
 - `nodeLabel: string` — this item's spoken name, used for the tree's reorder announcements: a host
-  `aria-label` is authoritative in both models; otherwise `item.accessibleLabel || item.label` in
+  `aria-label` is authoritative in both models
+  (including the component-owned stable-ID fallback for otherwise unnamed data rows); otherwise `item.accessibleLabel || item.label` in
   the data model, or flattened accessibility-visible slotted label text (nested items excluded)
   followed by the `label` fallback in the declarative one. Direct and forwarding-slot
   text/ARIA/visibility mutations update the name

package/llms/components/lr-typing-indicator.md

@@ -25,6 +25,9 @@ classic "typing…" affordance for a standalone status line), `pulse` (a single
 quieter cue for a tight space, e.g. next to an avatar), `cursor` (a blinking vertical bar, meant to
 sit inline at the tail end of streamed text still being appended to).
 
+Removing `label` restores the localized thinking name while preserving an explicit host
+`aria-label`. Later label assignments remain reactive.
+
 **Properties:**
 
 - `shape: TypingIndicatorShape = 'dots'` (`'dots' | 'pulse' | 'cursor'`, reflected)

package/llms/components/lr-usage-badge.md

@@ -23,6 +23,10 @@ The tooltip reuses `lr-tool-call-chip`'s hover/focus/Escape/`aria-describedby` c
 Not `lr-context-meter` (occupancy of a fixed capacity); not `lr-generation-metrics` (live, with a
 Stop button) — this is static after the fact.
 
+Removing `cost-text` or `summary` safely omits that content; explicit empty values remain empty and
+later values restore it. An open tooltip participates in shared Escape ordering even while only
+hovered, and dismissal preserves focus elsewhere.
+
 **Properties:** `tokensIn?: number` (attribute `tokens-in`) — input tokens, normalized to a
 non-negative integer, locale-formatted; segment omitted while unset/non-finite. `tokensOut?: number`
 (attribute `tokens-out`) — same rules. `costText: string = ''` (attribute `cost-text`) —

package/llms/components/lr-video.md

@@ -21,6 +21,10 @@ selectable captions, and bounded WebVTT thumbnail previews. It mirrors the publi
 API under the `lr-` prefix. Import the granular registration entry with
 `import '@aceshooting/lyra-ui/components/media/video/video.js'`.
 
+When progress is unavailable, the disabled native range input and its visible timeline track retain
+resting paint under hover and press. Once media duration makes progress available, the track retains
+its token-driven hover and press feedback.
+
 **Properties:** `autoplay: boolean = false`, `autoplayMuted: boolean = false` (attribute
 `autoplay-muted`), `autoplayOnVisible: boolean = false` (attribute `autoplay-on-visible`),
 `controls: 'none' | 'standard' | 'full' = 'standard'`, `currentTime: number = 0` (attribute
@@ -107,8 +111,10 @@ kept for mechanical Web Awesome migration. Lyra also supplies
 Caption and playback-rate selectors remain native `<select>` controls with decorative, pointer-inert
 chevrons; their option foreground and background inherit `--controls-color` and
 `--controls-background`. Controls, elapsed/title text, caption text, and selectors consistently use
-the semantic strong-overlay foreground. The fallback remains legible in light and dark themes;
-an explicit `--controls-color` still has final precedence, and forced-colors mode remains UA-owned.
+the semantic strong-overlay foreground. The fallback remains legible in light and dark themes.
+The poster play button and its glyph instead default to `--lr-color-text` against their
+`--lr-color-surface-overlay` surface. An explicit `--controls-color` retains final precedence on
+both poster and overlay controls, and forced-colors mode remains UA-owned.
 
 **RTL behavior:** surrounding controls follow the inherited direction, while the elapsed-media axis
 stays physical left-to-right. Native ArrowRight advances and ArrowLeft rewinds the timeline in both

package/llms/components/lr-virtual-list.md

@@ -134,7 +134,9 @@ the `lr-virtual-scroll` detail shape.
 `groupByRecency(items, options?)` is a DOM-free helper that returns non-empty
 Today/Yesterday/Previous 7 Days/Older buckets, preserves input order within each bucket, and accepts
 a timestamp extractor, reference date, and label overrides. Import it from its granular subpath —
-the package root re-exports it too, but that entry pulls in the eager registration barrel:
+the package root also re-exports it without registering custom elements, while the granular
+route limits the named-export module graph. `@aceshooting/lyra-ui/all.js` is the separate eager
+registration entry:
 
 ```ts
 import { groupByRecency } from "@aceshooting/lyra-ui/utilities/group-by-recency.js";
@@ -303,11 +305,11 @@ default estimate with sparse `ResizeObserver` measurements for rows that have ac
   Each row carries `will-change: transform` (a compositor hint for the per-frame translate), which
   makes every row its own stacking context. Rows otherwise carry no `z-index`, so they paint in DOM
   order and each one paints over the previous. Anything a row renders that overflows its own box —
-  an `<lr-menu>` popup in a row-action menu, a tooltip, an outward focus ring — is therefore painted
+  an `<lr-dropdown>` popup containing a row-action menu, a tooltip, an outward focus ring — is therefore painted
   _underneath_ every following row, no matter how high its own `z-index` is: that `z-index` only
   orders siblings inside the row's own context. The last row always looks correct, which is exactly
   why the failure tends to hide in short lists. A row lifts to `--lr-layer-content` while something
-  inside it holds focus or while it contains an open `lr-menu`. The explicit menu-open branch covers
+  inside it holds focus or while it contains an open `lr-dropdown`. The explicit dropdown-open branch covers
   imperative opening and virtual measurement/render cycles, where focus can temporarily return to
   the document while the popup remains visible. The value deliberately _matches_
   `[part='group']`'s rather than exceeding it, so the two land on the same layer and DOM order

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

@@ -32,6 +32,14 @@ control changes target; closing or filtering also retires a row-owned preview on
 control represents it. Does not synthesize speech, fetch catalogs, or persist selection; not a
 persona picker; `lr-model-select` stays for LLMs.
 
+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.
+
 **Exported types:** `LyraVoiceCatalogEntry extends LyraCatalogEntry { language?: string;
 description?: string; previewUrl?: string }` — `language`/`description` render as a quiet
 `[part="option-meta"]` second line. Voice catalogs use the shared
@@ -60,6 +68,10 @@ identically-named properties. `size: LyraSize = 'm'` (reflected) selects the sha
 `--lr-form-control-*` metrics. The separate preview button retains the library-wide 40px minimum
 hit area at compact tiers and grows with `l`/`xl`.
 
+`readonly: boolean = false` (reflected) mirrors `lr-model-select`: it blocks user typing and catalog
+commits while preserving focus, popup navigation, selection/copy, reset, submission, programmatic
+writes, and the preview actions.
+
 The `label` property and `label` slot share one native label in the standard `form-control` frame.
 Slotted label content participates in the accessible name in both closed-dropdown and free-text
 modes; an explicit host `aria-label` remains the highest-precedence name.
@@ -113,8 +125,9 @@ outer pair. One bubbling/composed `lr-invalid` alias fires when native validity
 `[part="form-control-label"]`, retunable or suppressible through
 `--lr-form-control-required-content`, `--lr-form-control-required-color` and
 `--lr-form-control-required-offset`; and while the picker is barred from
-constraint validation (own `disabled`, or an ancestor `<fieldset disabled>` — there is no `readonly`
-here) it reports no violation and publishes neither `:state(invalid)` nor `:state(user-invalid)`.
+constraint validation (own `disabled` or `readonly`, or an ancestor `<fieldset disabled>`) it
+reports no violation and publishes neither `:state(invalid)` nor
+`:state(user-invalid)`.
 
 **CSS parts:** `form-control` (the complete field frame), `form-control-label`, `trigger` (closed-dropdown mode), `combobox`/`combobox-input`
 (free-text mode), `provider-badge`, `listbox`, `option`, `option-label`, `option-meta` (the quiet

package/llms/components/lr-widget-renderer.md

@@ -30,6 +30,15 @@ navigates (no `href` props are allowlisted anywhere). Controlled state binding i
 narrow: a versioned document may bind an allowlisted primitive prop to a JSON Pointer, and the host
 must apply every requested change itself.
 
+Default authoring diagnostics are silent outside Lit's development mode. An explicit expert
+`ResolveContext.warn` callback remains active in every runtime; warning keys and the suppression cap
+remain scoped to the current context generation. Runtime `lr-render-error` reporting is independent
+of this development diagnostic policy.
+
+`createWidgetDocument` validates authored trees immediately. To handle a received, untrusted
+document, pass its envelope to the renderer's `document` boundary; malformed envelopes clear prior
+output and emit `lr-render-error`. The malformed-stream example exercises this boundary.
+
 **Exported types:**
 
 - `LyraWidgetNode { readonly type: string; readonly id?: string; readonly props?:
@@ -123,12 +132,12 @@ value to complete the update.
 **CSS parts:** `base` (the root wrapper, `display: contents`), `row`, `col`, `text` (built-in
 structural nodes only — a mapped lyra component exposes its own parts instead).
 
-Caps: depth 32, 5,000 nodes, 100 visited props per node, and 100 unique warning keys plus one
-deterministic suppression warning. The current document/registry generation deduplicates warnings;
-binding-state-only re-resolution stays quiet, while replacing the root or registry releases prior
-keys. Exported deterministic `nodeKey`/`nodePath` identity drives reconciliation. One bounded input
-snapshot is shared by traversal, identity validation, pointer resolution, and rendering, so getters
-beyond an admitted cap are never dereferenced.
+For predictable rendering, documents are limited to depth 32, 5,000 nodes, and 100 properties per
+node. Content beyond those size limits is omitted or truncated; malformed documents fail closed,
+clearing prior output and emitting `lr-render-error`. `document` is captured when assigned, so
+mutate a copy and assign it to update; `bindingState` updates bindings without changing that
+captured document or registry. Exported deterministic `nodeKey`/`nodePath` identity drives
+reconciliation.
 
 ```ts
 import { html } from "lit";
@@ -157,10 +166,10 @@ const view = html`<lr-widget-renderer
 ```
 
 For a controlled binding, use a per-instance registry and apply the event's requested value back to
-`bindingState` (this one-field example binds `/name`). This is also the lean registration route: it imports
-the side-effect-free renderer class, defines only `lr-widget-renderer`, and imports only the mapped
-input registration. Do not import `widget-renderer.js` on this route; that entry intentionally
-installs the full default registry.
+`bindingState` (this one-field example binds `/name`). The direct class route supplies the
+default type mappings but defines only `lr-widget-renderer`; register every mapped custom element
+you use yourself. The normal `widget-renderer.js` entry also registers the eight default mapped
+elements, so do not import it on this route.
 
 ```html
 <lr-widget-renderer id="bound-widget"></lr-widget-renderer>
@@ -200,6 +209,5 @@ renderer.addEventListener("lr-widget-state-change", (event) => {
 
 **Optional peer deps:** none new — the normal registration entry directly imports the eight mapped
 components (`markdown` keeps its own `marked`/`dompurify` optional-peer fallback). The manual class
-route above is the verified lean path: its real peer-inclusive esbuild metafile excludes
-`default-registry.js` and all eight default mapped class modules, while the consumer explicitly
-imports only the component registrations its per-instance registry maps.
+route supplies the same default type mappings while leaving component registration under the
+consumer's control.

package/llms/components/lr-widget.md

@@ -23,8 +23,10 @@ position) survives the transition.
 
 **Properties:**
 
-- `label: string = ''`
-- `sublabel: string = ''`
+- `label: string = ''` — header title; a removed attribute renders as absent while preserving
+  `null` readback. Supplied empty strings remain empty and later values recover normally.
+- `sublabel: string = ''` — secondary header copy with the same removal, empty-string and recovery
+  behavior.
 - `collapsible: boolean = false` (reflected — shows the collapse/expand chevron button)
 - `collapsed: boolean = false` (reflected)
 - `expandable: boolean = false` (reflected — shows the fullscreen toggle button)

package/llms/components/lr-word-cloud.md

@@ -34,6 +34,10 @@ and repeated edge movements append repeated announcements even when their text i
 no live-region role of its own. Pointer input resolves the nearest word from the adequately-sized
 SVG surface; the potentially tiny text glyphs are not independent hit targets.
 
+Pinned opposite-sign finite endpoints such as `[-1e308, 1e308]` produce bounded finite scale
+fractions and SVG geometry, including with reversed endpoints or square-root scaling. Word weights
+remain nonnegative; placement budgets, font-size limits, and the omitted-word policy are unchanged.
+
 **Properties:**
 
 - `words: readonly WordCloudWord[] = []` (attribute: false) — readonly `{ text: string, weight:

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

@@ -25,6 +25,10 @@ matching. Every document type declaration is rejected before `DOMParser`, preven
 entity access and browser-specific internal-entity expansion. Not `lr-json-viewer` (JS values); not `lr-html-viewer`
 (sanitized _rendered_ HTML). No XPath/XSLT evaluation, no editing, no schema validation.
 
+The registration entry also matches extensionless `application/*+xml` MIME essences, ignoring
+parameters, case and outer whitespace. Exact registered MIME keys retain precedence over this
+fallback matcher.
+
 **Properties:** `src: string = ''` — URL to fetch and parse; ignored once `xml` is set. `xml?:
 string` (property only) — raw XML text to parse and render; wins over `src`, and setting it parses
 synchronously. Assigning `undefined` relinquishes inline authority and immediately resumes an
@@ -43,8 +47,11 @@ attribute. Invalid CSS `max-height` values, declaration breaks, and `url()` are
 every element's tag name, attribute names/values, and own text (empty/whitespace query behaves like
 `clearSearch()`), accepting at most 4,096 query code units and scanning at most 4,000,000 code
 units while retaining 10,000 matches; `searchNext()`/`searchPrevious()` advance/step back through matches (wrapping);
-`clearSearch()` clears the query and matches. All three resolve only after the newly active match's
-row has been scrolled into view (`block: 'center'`, `behavior: 'auto'` under
+`clearSearch()` clears the query and matches. Imperative `search()`, `searchNext()` and
+`searchPrevious()` reopen the selected match and its ancestors, including manually collapsed
+nodes, before scrolling. Other explicit collapse choices remain in effect, and later manual
+collapse still takes precedence over default expansion. All three resolve only after the newly
+active match's row has been scrolled into view (`block: 'center'`, `behavior: 'auto'` under
 `prefers-reduced-motion`) — before 9.0.0 they moved `data-active-match` without ever scrolling, so
 on a document taller than the viewport the reader never saw the match they had stepped to. Replacing
 the XML source clears document-relative matches and emits the canonical empty `lr-search-change`;

package/llms/components/lr-zoomable-frame.md

@@ -20,6 +20,9 @@ Sandboxed iframe preview that mirrors Web Awesome's zoomable-frame contract. It
 `<iframe>` through discrete controls without changing the document's own viewport, and fills its
 allocated inline size with a 16:9 aspect ratio by default (override `aspect-ratio` on the host).
 
+Focus on either zoom control does not enter the iframe browsing context, and `blur()` does not blur
+a focused zoom control.
+
 **Properties:**
 
 - `src: string = ''` — iframe URL. Relative, `http:`, `https:`, `blob:`, and exact `about:blank`
@@ -45,7 +48,7 @@ allocated inline size with a 16:9 aspect ratio by default (override `aspect-rati
   and carries no unsupported `aria-disabled` claim.
 - `accessibleLabel: string | null` (attribute `aria-label`) — a declarative attribute remains on
   the host while the iframe gets its localized purpose title, avoiding a duplicate name on two
-  semantic owners. A property-only value names the iframe. Explicit empty host naming is preserved
+  semantic owners. A property-only value names the iframe and updates reactively without creating a host attribute. Explicit empty host naming is preserved
   as an empty iframe title rather than replaced through truthiness.
 - readonly `iframe?: HTMLIFrameElement`, `contentWindow: Window | null`, and
   `contentDocument: Document | null`. Both content accessors return `null` while detached;
@@ -73,7 +76,7 @@ rather than a second interactive control; the native zoom buttons remain the sol
 actions.
 
 **Events:** internal `focus`/`blur` from the iframe are relayed exactly once as owner-realm native
-`FocusEvent`s (bubbling and composed, preserving `relatedTarget`);
+`FocusEvent`s (bubbling and composed, preserving external `relatedTarget`; a transition to or from an internal zoom control uses `null` because retargeting that control to the host would suppress the relay);
 native `load` and `error` are relayed exactly once from the current iframe
 generation as non-bubbling, non-composed `Event` instances. Navigation/source-policy changes
 replace the iframe, so a late event from an earlier document is ignored; detached frames do not
@@ -82,7 +85,7 @@ notify.
 **CSS parts:** `iframe`, `controls`, `zoom-in-button`, and `zoom-out-button`. Real focus entry into
 the browsing context (Tab, pointer, or `focus()`) exposes `data-frame-focused` on the host and paints
 the shared focus ring around the iframe boundary; blur, navigation rekey, disablement, and removal
-clear it.
+clear it. Moving between the iframe and a zoom control clears or restores the marker and emits one matching native blur or focus relay; focusing a zoom control alone leaves the marker absent.
 
 **CSS custom properties:** read-only `--lr-zoomable-frame-zoom`, resolved from the `zoom`
 property and applied to the internal iframe scale; and `--lr-zoomable-frame-control-hover-background`

package/llms/peers.md

@@ -39,11 +39,11 @@ for the page.
 |---|---|---|
 | `@aceshooting/lyra-flags` | `^2.3.0` | _(loaded by a shared internal module)_ |
 | `@aiden0z/pptx-renderer` | `^1.2.4` | `lr-pptx-viewer` |
-| `@sgratzl/chartjs-chart-boxplot` | `^4.4.5` | `lr-box-plot` |
-| `chart.js` | `^4.5.1` | `lr-bar-chart`, `lr-box-plot`, `lr-bubble-chart`, `lr-chart`, `lr-doughnut-chart`, `lr-histogram`, `lr-line-chart`, `lr-pie-chart`, `lr-polar-area-chart`, `lr-radar-chart`, `lr-scatter-chart` |
-| `chartjs-plugin-annotation` | `^3.1.0` | `lr-bar-chart`, `lr-bubble-chart`, `lr-chart`, `lr-doughnut-chart`, `lr-histogram`, `lr-line-chart`, `lr-pie-chart`, `lr-polar-area-chart`, `lr-radar-chart`, `lr-scatter-chart` |
+| `@sgratzl/chartjs-chart-boxplot` | `^4.0.0` | `lr-box-plot` |
+| `chart.js` | `^4.0.1` | `lr-bar-chart`, `lr-box-plot`, `lr-bubble-chart`, `lr-chart`, `lr-doughnut-chart`, `lr-histogram`, `lr-line-chart`, `lr-pie-chart`, `lr-polar-area-chart`, `lr-radar-chart`, `lr-scatter-chart` |
+| `chartjs-plugin-annotation` | `^3.0.0` | `lr-bar-chart`, `lr-bubble-chart`, `lr-chart`, `lr-doughnut-chart`, `lr-histogram`, `lr-line-chart`, `lr-pie-chart`, `lr-polar-area-chart`, `lr-radar-chart`, `lr-scatter-chart` |
 | `chartjs-plugin-datalabels` | `^2.2.0` | `lr-bar-chart`, `lr-bubble-chart`, `lr-chart`, `lr-doughnut-chart`, `lr-histogram`, `lr-line-chart`, `lr-pie-chart`, `lr-polar-area-chart`, `lr-radar-chart`, `lr-scatter-chart` |
-| `chartjs-plugin-zoom` | `^2.2.0` | `lr-bar-chart`, `lr-bubble-chart`, `lr-chart`, `lr-doughnut-chart`, `lr-histogram`, `lr-line-chart`, `lr-pie-chart`, `lr-polar-area-chart`, `lr-radar-chart`, `lr-scatter-chart` |
+| `chartjs-plugin-zoom` | `^2.0.0` | `lr-bar-chart`, `lr-bubble-chart`, `lr-chart`, `lr-doughnut-chart`, `lr-histogram`, `lr-line-chart`, `lr-pie-chart`, `lr-polar-area-chart`, `lr-radar-chart`, `lr-scatter-chart` |
 | `d3-drag` | `^3.0.0` | `lr-graph`, `lr-knowledge-graph-explorer` |
 | `d3-force` | `^3.0.0` | `lr-graph`, `lr-knowledge-graph-explorer` |
 | `d3-selection` | `^3.0.0` | `lr-graph`, `lr-knowledge-graph-explorer` |
@@ -58,7 +58,7 @@ for the page.
 | `maplibre-gl` | `>=5 <7` | `lr-geojson-view`, `lr-geojson-viewer`, `lr-map` |
 | `marked` | `^18.0.11` | `lr-agent-workspace`, `lr-dashboard-grid`, `lr-eval-run`, `lr-markdown`, `lr-markdown-core`, `lr-message-parts`, `lr-notebook-viewer`, `lr-rag-answer`, `lr-streaming-text`, `lr-widget-renderer` |
 | `papaparse` | `^5.7.0` | `lr-csv-viewer`, `lr-dataset-viewer` |
-| `pdfjs-dist` | `^6.2.108` | `lr-pdf-viewer` |
+| `pdfjs-dist` | `^6.3.289` | `lr-pdf-viewer` |
 | `postal-mime` | `^3.0.0` | `lr-email-viewer` |
 | `qrcode` | `^1.5.4` | `lr-qr-code` |
 | `react` | `>=19 <20` | type-only `@aceshooting/lyra-ui/custom-elements-jsx` entry (no runtime import) |

package/llms/shared.md

@@ -10,11 +10,6 @@ introduced by the current release, it is the current package version.
   compatibility promises: once published, their public APIs receive the same full-semver protection
   as stable components until they are formally deprecated and removed.
 
-An experimental component graduates to stable only after its documented API, populated
-accessibility state, behavior in Chromium, Firefox, and WebKit, and compatibility contract pass
-maintainer review and release qualification. A stable component keeps that status only while those
-contracts remain release-blocking.
-
 Deprecation is explicit metadata, not an implication from status. Each deprecated component or
 member names a replacement, a deprecation version, a rationale, and the earliest permitted removal
 version. If an API is deprecated in major version M, it remains available for the complete M+1
@@ -49,8 +44,7 @@ The major-version landmarks after 9.0.0 are:
 
 - **10.0.0:** removed eligible members deprecated during 9.x and made the public-contract
   corrections listed in its changelog entry; follow that entry's per-member migration guidance.
-- **11.0.0:** carried no known consumer-breaking change. The major number recorded conservative
-  public-API-gate fingerprint and generated-type churn; consumers upgrading from 10.x were not
+- **11.0.0:** carried no known consumer-breaking change; consumers upgrading from 10.x were not
   expected to change code.
 - **12.0.0:** removed the inherited static `LyraElement.getPropertyDescriptor()` surface after Lit
   deprecated that finalization hook. Ordinary component consumers need no migration; only subclasses
@@ -64,10 +58,10 @@ Chromium 120+, Gecko 121+, WebKit 16.4+, and Node 20+ (ESM only; there is no Com
 Those floors are derived from platform features the source actually uses — `:dir()`, `:has()`,
 `@container`, `color-mix()`, `ElementInternals` form association — because the package ships
 untranspiled ES2022 modules with no polyfills and no build-time downleveling. There is deliberately
-no `browserslist` field: it would describe a build step this package does not have. CI proves the
-current stable build of each engine (the full suite on Chromium, a contract subset on Firefox and
-WebKit, on Node 20 and 22); the version floors are derived rather than tested. Raising any floor is
-a semver-major change. Full policy, including the known WebKit cross-shadow-selection gap and the
+no `browserslist` field: it would describe a build step this package does not have. The version
+floors are derived from those platform features rather than individually verified version-by-version.
+Raising any floor is a semver-major change. Full policy, including the known WebKit
+cross-shadow-selection gap and the
 rule for when a `@supports` fallback may be dropped:
 <https://github.com/aceshooting/lyra-ui/blob/main/docs/support-policy.md>.
 
@@ -185,12 +179,49 @@ The entry points, then:
   `@aceshooting/lyra-ui/ai` (provider-neutral data types), `@aceshooting/lyra-ui/testing`
   (happy-dom shims), `@aceshooting/lyra-ui/utilities/*` (the curated shared helpers, all documented below).
 
+### Registration-free component helpers
+
+The following focused helpers are public, side-effect-free modules. They do not define a custom
+element, so they are suitable for server code, workers, or applications that need the same data
+normalization as a component without registering it:
+
+```ts
+import {
+  DEFAULT_INTERNAL_PATTERNS,
+  parseStackTrace,
+  STACK_TRACE_LIMITS,
+} from '@aceshooting/lyra-ui/components/agent-tools/stack-trace/stack-trace-parse.js';
+import {
+  MAX_RENDERED_LYRA_SPANS,
+  normalizeLyraSpans,
+} from '@aceshooting/lyra-ui/components/agent-tools/trace-tree/span.js';
+import {
+  agentStatusMessage,
+  agentStatusVariant,
+} from '@aceshooting/lyra-ui/components/agent-tools/agent-status-presentation.js';
+import {
+  approvalAction,
+  approvalDecision,
+} from '@aceshooting/lyra-ui/components/agent-tools/approval-state.js';
+import { DEFAULT_WIDGET_TYPE_REGISTRY } from '@aceshooting/lyra-ui/components/conversation/widget-renderer/default-registry.js';
+```
+
+Their companion type exports remain on those same paths: stack parsing exposes `StackFrame`,
+`StackGroup`, `StackTraceParseOptions`, and `StackTraceParseResult`; span projection exposes
+`LyraSpan`, `LyraSpanKind`, `LyraSpanStatus`, and `LyraSpanProjection`; status and approval helpers
+expose their respective presentation and decision types. The status helpers are `agentStatusKind`,
+`agentStatusLabel`, `agentStatusMessage`, `agentStatusVariant`, `isAgentStatusTerminal`, and
+`isAgentStatusActive`; approval also exports `ApprovalAction` and `ApprovalDecision`; span also
+exports `normalizeLyraSpanKind` and `normalizeLyraSpanStatus`; the widget registry module exports
+only `DEFAULT_WIDGET_TYPE_REGISTRY`. Import a component registration entry separately when the page
+also renders that component.
+
 ### Optional autoloader
 
 `@aceshooting/lyra-ui/autoloader.js` exports `discover(root?, options?)`, `start(root?, options?)`,
-and `stop()`. It contains an inventory-generated literal class-module import for every known Lyra
-tag, so a bundler can split each component while ordinary granular imports remain independent.
-Importing this entry alone has no side effect and registers nothing.
+and `stop()`. It can load each known Lyra tag independently, allowing bundlers to split components
+while granular imports remain independent. Importing this entry alone has no side effect and
+registers nothing.
 
 - `discover()` scans once. `start()` performs the same initial scan, then observes dynamic and
   Turbo-style replacement subtrees; a later `start()` stops the previous watcher. `stop()` is
@@ -351,8 +382,8 @@ through `@aceshooting/lyra-ui/events` for listeners on an ancestor, `document` o
 ## Form association
 
 `FormAssociated(Base)` (`@aceshooting/lyra-ui/utilities/form-associated.js`) makes a `LitElement`
-form-associated: `static formAssociated = true` plus `attachInternals()` in the constructor, which
-eagerly calls
+form-associated: `static formAssociated = true` plus a descriptor-safe `attachInternals` lookup in
+the constructor, which eagerly calls
 `internals.setFormValue('')` so an untouched control is present in `FormData` as `""` from
 construction — matching native `<input>` — instead of being absent.
 
@@ -811,8 +842,8 @@ both modes: `on-<e>` clears WCAG 1.4.3's 4.5:1 against `fill-<e>` at the _same_
 construction, and no other pairing is promised. `border-normal` and `border-loud` clear 1.4.11's
 3:1 against the page surface, so a control's visible bounds are always discernible. `border-quiet`
 is deliberately exempt: it exists for decoration that is not load-bearing — a rule between table
-rows, a hairline inside an already-bounded card — so never use it as a control's only boundary. All
-of this is checked at build time across both modes, not asserted by hand.
+rows, a hairline inside an already-bounded card — so never use it as a control's only boundary.
+These guarantees apply in both modes.
 
 **Every slot has its own `--lr-theme-*` override**, named after the slot, so one decision can be
 rethemed without forking anything beneath it:
@@ -1040,11 +1071,9 @@ fails when inherited from a wrapper, that is a component bug; setting the same h
 every host should not be necessary.
 
 **There is no way to tell a live `--lr-*` declaration from a dead one without rendering.** A dead
-declaration is byte-identical to a working one in the stylesheet, and nothing in a build reports
-it — a test asserting on stylesheet source text (`expect(source).toContain('--lr-token: …')`)
-passes just as happily when the token is being shadowed at a nested host. Verify with
-`getComputedStyle` on the real element in the real state, and perturb the value deliberately to
-confirm the assertion actually bites.
+declaration is byte-identical to a working one in the stylesheet; a stylesheet-text check cannot
+distinguish it. Verify with `getComputedStyle` on the real element in the real state, and perturb
+the value deliberately to confirm the assertion actually bites.
 
 The same trap has a second form inside a component's own styles: a _declared_ value always wins
 over a `var()` fallback arm, and `auto` is a declared value. That is why the exact-height escape
@@ -1670,11 +1699,8 @@ import {
   `CitationSelectEventDetail`, `ToolApprovalEventDetail`, `CancelEventDetail`, `RetryEventDetail`,
   `ExportEventDetail`
 
-The package's no-emit type-test program asserts that each type still matches the property it feeds
-on `lr-chat-message`, `lr-tool-call-chip`, `lr-tool-result-view`, `lr-source-card`,
-`lr-attachment-chip`, and `lr-document-preview`. The binding is enforced by `tsc` without shipping
-an importable contract module. The types are structural and provider-agnostic: map any vendor's
-payload onto them once, at the edge.
+These structural, provider-agnostic types correspond to the component inputs above; map a vendor
+payload onto them at the edge.
 
 ### Task-first AI composition guide
 
@@ -1775,24 +1801,17 @@ whose rendering depends on something only a browser can answer — its own light
 browser global such as `EyeDropper` — reproduces the server's answer on the hydrating render and
 corrects itself on the next update, so a slotted override lands one frame after hydration; a
 browser-only mount is unaffected and renders the final result the first time. Layout/observer/canvas/media work
-begins after hydration, and remote content is client-only. CI imports every granular module, renders
-every inventory tag through its declared tier, and crawls a real Chromium DSD page (including
-`lr-page`) while failing hydration warnings/errors or DOM-identity replacement.
-
-## Testing a downstream project: `@aceshooting/lyra-ui/testing`
-
-`testing/happy-dom-shims.ts` exports `installHappyDomFormAssociatedShims(): void` for a consumer's
-own Vitest + happy-dom suite. happy-dom implements no `ElementInternals`, and every form-associated
-component calls `this.attachInternals()` unconditionally in its constructor, so instantiating one
-throws immediately without the shim. Call it once from a Vitest `setupFiles` entry, before importing
-any component. It patches `HTMLElement.prototype.attachInternals` with a stub covering what the
-components actually call — `setFormValue()`, `setValidity()`, `checkValidity()`, `reportValidity()`,
-plus readonly `form`/`labels`/`validity`/`validationMessage`/`willValidate`. `setValidity()` matters
-beyond construction: `AnchoredValidityController` calls it on every update, so without the shim a
-form control throws on any `value` change, not only when it is created. The shim is a no-op wherever
-`attachInternals` already exists (any real browser), so it is safe to call unconditionally from a
-shared setup file. This package's own tests run in real browsers via `@web/test-runner` and never
-call it.
+begins after hydration, and remote content is client-only.
+
+## Testing form-associated components: `@aceshooting/lyra-ui/testing`
+
+`@aceshooting/lyra-ui/testing` exports `installHappyDomFormAssociatedShims(): void` for test
+environments without usable `ElementInternals`. In that environment, form participation is inert
+while components retain local validity and state behavior. Install the helper once before assertions
+that need form-value or validity behavior: it supplies
+`setFormValue()`, `setValidity()`, `checkValidity()`, `reportValidity()`, and readonly
+`form`/`labels`/`validity`/`validationMessage`/`willValidate`. The shim is a no-op where the
+platform already provides internals, so it is safe in a shared setup file.
 
 ## Accessibility contract
 
@@ -1818,20 +1837,13 @@ computed name. Check the component's own reference section (or its class JSDoc)
 convention it uses before writing markup — an `accessible-label` attribute on an `aria-label`-only
 component is a silent no-op, not an error.
 
-**What that contract is verified by, precisely.** Every one of the 284 public tags carries at least
-one axe-core assertion in its own directory's tests, in a test that mounts its own tag; contrast
-(4.5:1 text, 3:1 control borders, in both the light and dark palettes), a 40px minimum target size,
-pressed-state coverage for every hoverable part, and `::part()` reachability are separate blocking
-gates. All of that is automated. **No screen reader has been run against this library, in any
-pairing, and no human accessibility audit exists** — so treat "accessible" here as "passes an
-automated rule engine and a written role/name/state contract", never as verified assistive-technology
-behavior, and expect no conformance claim or VPAT. The full statement of what is and is not covered,
-plus how to report an accessibility bug, is at
+Lyra UI does not make a formal assistive-technology conformance claim or provide a VPAT. For the
+documented accessibility scope and how to report an accessibility issue, see
 <https://github.com/aceshooting/lyra-ui/blob/main/docs/accessibility.md>.
 
 ## Editor and tooling integration
 
-The published package ships machine-readable metadata for editors, all regenerated on `prepack`:
+The published package ships machine-readable metadata for editors:
 `custom-elements.json` (Custom Elements Manifest), `web-types.json` (JetBrains, zero-config), and
 `vscode-html-data.json` / `vscode-css-data.json` (point `html.customData` / `css.customData` at them
 in `.vscode/settings.json`). For an agent, `llms/components/<tag>.md` is the cheaper source; these
@@ -2014,7 +2026,9 @@ arrowPadding?: number; hoverBridge?: HTMLElement; onPlaced?: (result: PlacementR
   application can build its **own** form-associated control alongside Lyra's and have it
   participate in a form, restore on reset, and report validity the same way every `lr-` control
   does. Reach for it instead of hand-rolling `attachInternals()` when a bespoke control has to sit
-  in the same `<form>` as these.
+  in the same `<form>` as these. `attachInternalsSafely()` inspects own and inherited data
+  descriptors without reading accessors, calls an eligible implementation once, and returns the
+  fallback internals for a missing, accessor-backed, non-callable, or throwing capability.
   The free-function signatures are `attachInternalsSafely(host)`,
   `createStringArrayFormDataState(name, values)`, `readStringArrayFormDataState(state)`, and
   `FormAssociated(Base, valueAdapter?)`. For a non-string value, pass a typed
@@ -2277,13 +2291,10 @@ number; clearTimeout(handle: number): void }`.
 - `formResetCallback()` restores the _content attribute_ default, so `el.value = 'x'` never redefines
   what `form.reset()` restores to (native `defaultValue`/`defaultSelected` semantics).
 
-## Packaging
+## Reference artifacts
 
-`custom-elements.json`, the React/Vue/Svelte declaration entry points, editor metadata, and derived
-LLM artifacts are regenerated by `prepack` and included in `package.json`'s `files` allowlist. The
-family references, this shared guide, and the introductory LLM sources are authored inputs; the
-generated index, per-component pages, tokens, peers, migration reference, and concatenated catalog
-are freshness-checked against them, the manifest, and `dist/` before publication.
+The package includes authored family and shared references plus derived index, component, token,
+peer, migration, and concatenated references.
 
 ## When no component fits, file it