@aceshooting/lyra-ui 13.0.1 → 14.1.0

package/llms/components/lr-flow-run-status.md

@@ -26,7 +26,7 @@ poll, or time anything — pure pushed state; `durationMs` is host-computed.
 - `for: string = ''` — id of the target `lr-flow-canvas`; empty resolves to the nearest ancestor
 - `decorations: FlowRunDecorations = {}` (attribute: false) — a detached, deeply frozen readonly
   record bounded to 10,000 keys plus finite nested depth/entry budgets and pushed onto the resolved
-  canvas; invalid status entries are omitted, and consumers reassign the record after changes
+  canvas; invalid statuses and records with unreadable `status`, `progress`, `durationMs` or `detail` fields are omitted independently, retaining valid neighbors, and consumers reassign the record after changes
 - `hideSummary: boolean = false` (attribute `hide-summary`) — omits the "{done} of {total} steps
   complete" strip, keeping only the decoration push
 - `label: string = ''` — accessible name for the summary strip

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

@@ -39,6 +39,8 @@ granular fields are then ignored entirely (`Intl` throws when the two are mixed)
 to use the granular set. An unparseable `date` renders the default slot. An invalid
 `timeZone` throws a `RangeError` inside `Intl`, which is caught and retried once without the zone —
 so the output falls back to the browser's local zone instead of failing to render. Valid output is
-wrapped in semantic `<time datetime="…">`.
+wrapped in semantic `<time datetime="…">`. Date input accepts primitive strings/numbers or a
+genuine `Date`; arbitrary objects are rejected without calling their `valueOf()`, `toString()`, or
+other conversion hooks.
 
 **Slots:** default — fallback content for an invalid/unparseable `date`.

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

@@ -18,6 +18,10 @@
 
 `Intl.NumberFormat` output.
 
+Removing `currency` preserves the removal readback while formatting with the declared USD fallback.
+An explicitly blank currency also keeps its existing USD formatting fallback, and a later valid
+currency takes effect normally.
+
 Shared by all four formatters (`lr-format-number`, `lr-format-date`, `lr-format-bytes`,
 `lr-relative-time`): each is text-only — a `display: inline` host with **no CSS parts, no events, and
 no themeable custom properties of its own** — rendering one formatted string into its shadow root.

package/llms/components/lr-funnel.md

@@ -21,6 +21,10 @@ bar whose length is that stage's share of the **first** stage, read top-to-botto
 drop-off. It sits beside `lr-gauge` and `lr-heatmap` as an analytics primitive rather than a general
 chart type.
 
+When a positive finite stage value divided by a positive finite baseline overflows to `Infinity`,
+the main or comparison data fill clamps to 100%. Nonfinite input normalization, nonpositive-baseline
+behavior, percentage and drop-off text, and overflow border styling keep their existing rules.
+
 It is deliberately not a sorted bar chart: it normalizes to the first stage rather than to the data
 maximum, draws no value axis, and reads as stage-to-stage retention rather than category comparison.
 Reach for `lr-bar-chart`/`lr-lite-chart` when you actually want a value axis and category comparison.

package/llms/components/lr-gauge.md

@@ -18,6 +18,10 @@
 
 Dependency-free SVG radial, full-circle ring, or linear meter (no charting library).
 
+Removing `label` omits the visible SVG label in radial, linear, and ring shapes and restores the
+localized gauge name unless `aria-label` is authored. The property retains removal `null`;
+explicitly empty labels remain empty and later labels render normally.
+
 **Properties:**
 
 - `value: number = 0`

package/llms/components/lr-generation-metrics.md

@@ -20,6 +20,11 @@ A compact, ticking status readout shown alongside an in-progress AI response: el
 count, and token-throughput, plus a built-in Stop button. First-party invention (no Web Awesome
 equivalent). Renders as e.g. `12.3s · 340 tokens · 27 tok/s [Stop]`.
 
+The host handles `lr-stop` by stopping its own producer and setting `status` to `complete`. A
+restart supplies a fresh `startedAt`, resets its token count, and retires the previous producer
+timer. The live example wires this lifecycle on mount, so its first Stop and every Restart take
+effect immediately.
+
 **9.0 identity migration:** `lr-generation-status` → `lr-generation-metrics`,
 `LyraGenerationStatus` → `LyraGenerationMetrics`, and `LyraGenerationStatusEventMap` →
 `LyraGenerationMetricsEventMap`. The old tag, class, event-map name, registration route, and

package/llms/components/lr-graph-legend.md

@@ -37,8 +37,10 @@ string; shape?: 'circle' | 'square' | 'diamond' }`, the shared `lr-graph.nodeTyp
   `aria-label` makes the host the sole overall owner (the wrapper omits its duplicate role/name);
   an explicitly empty host label stays empty on the wrapper
 
-**Events:** `lr-visibility-change` (`detail: { hiddenTypes }`, the complete updated array, fired
-after each toggle).
+**Events:** cancelable `lr-before-visibility-change` (`detail: { hiddenTypes }`, a frozen complete
+next array) fires before a toggle changes state or announces it. Preventing it suppresses all three.
+`lr-visibility-change` (`detail: { hiddenTypes }`, the complete updated array) fires after an
+accepted assignment and announcement.
 
 **Slots:** none.
 

package/llms/components/lr-graph-query-builder.md

@@ -19,6 +19,12 @@
 Form-associated editor for a typed graph relationship/path query, including entity anchors,
 relationship and node-type filters, hop limits, validation, and saved queries.
 
+When the DOM cannot provide `activeElement`, the builder skips focus restoration while chip removal
+and saved-query updates continue normally. Each minimum/maximum-hop select choice updates the query
+once and emits one `lr-input` with the complete `{ value: GraphQuery }` snapshot. Native value
+events, prefixed value aliases and listbox show/hide lifecycle events from those child selects are
+contained. Programmatic query assignments remain silent.
+
 The normalized `value` present at the first update is the form reset default. Later property writes
 and user edits change only the live query; `form.reset()` restores that initial model, clears
 interaction/touched state and the save-name draft, and retains a caller-set custom validity message

package/llms/components/lr-graph.md

@@ -18,6 +18,12 @@
 
 A force-directed node-link diagram with pan/zoom/drag, built on `d3-force`.
 
+A zero-width canvas link paints neither a stroke nor an arrowhead; its relationship remains in the
+nonvisual topology summary.
+
+In both renderers, roving navigation transfers real focus through nodes, operable links, then
+community hulls; zero-width, fully transparent, and dangling links remain outside that focus order.
+
 **Properties:**
 
 - `nodes: LyraGraphNode[] = []` (attribute: false) — readonly `LyraGraphNode { id: string; label?: string;
@@ -111,7 +117,7 @@ camera; `getNodePosition(id)` returns the current `{ x, y }` in graph-local draw
 **Events:** `lr-node-click` (`detail: { nodeId, x, y }`, where `x` and `y` are the clicked node's current
 local drawing coordinates), `lr-link-click` (`detail: { sourceNodeId, targetNodeId,
 linkId? }`; the optional `linkId` is the stable `LyraGraphLink.id` supplied by the caller), `lr-node-enter`/
-`lr-node-leave` (`detail: { nodeId }`, hover start/end, suppressed while dragging/panning),
+`lr-node-leave` (`detail: { nodeId }`, hover start/end, suppressed while dragging/panning; canvas emits once per hit-identity transition or exit),
 `lr-link-enter`/`lr-link-leave` (`detail: { sourceNodeId, targetNodeId, linkId? }`, same hover contract),
 `lr-node-expand` (`detail: { nodeId }`, a node was double-activated — native `dblclick`, or two
 Enter/Space activations within 500ms — regardless of `LyraGraphNode.expandable`), `lr-community-click`
@@ -222,7 +228,7 @@ localized `part="error"` alert. Install with
   force on the new midpoint and nudges the simulation via `alpha(0.1).restart()`, in addition to
   resizing the rendered `viewBox` — both branches apply independently, so setting `width` and
   `chargeStrength` in the same synchronous batch retunes both, not just one.
-- zoom is bounded via `minZoom`/`maxZoom` (`d3-zoom`'s `.scaleExtent(...)`, live-reactive); pan/
+- zoom is bounded via `minZoom`/`maxZoom` (`d3-zoom`'s `.scaleExtent(...)`, live-reactive in both SVG and canvas); pan/
   zoom/drag are still pointer-only with no keyboard equivalent. Links (`<line part="link">`) are now
   keyboard-operable too (`tabindex="0"`, `role="button"`, `aria-label`, Enter/Space), matching nodes.
 - while the `d3-force`/`d3-drag`/`d3-zoom`/`d3-selection` peers are resolving, the host shows an

package/llms/components/lr-grounding-summary.md

@@ -25,7 +25,7 @@ and `lr-citation-badge` for each evidence entry.
 **Properties:**
 
 - `assessment: GroundingAssessment | null = null` (attribute: false) — **`GroundingAssessment`,
-  imported from `@aceshooting/lyra-ui/ai`** (`src/ai/types.ts`): `{ supportedClaims: number;
+  imported from `@aceshooting/lyra-ui/ai`**: `{ supportedClaims: number;
 unsupportedClaims: number; coverage: number; confidence?: number; warnings?: string[];
 claims?: GroundedClaim[] }`, where `coverage` and `confidence` are 0–1 fractions. `null` renders
   the empty state
@@ -48,16 +48,16 @@ label?: string }`. Independent of `assessment`; empty omits the whole evidence s
   level used by both warnings and evidence sections; `'none'` keeps the visual text without
   exposing a heading role, and invalid untyped values fall back to level 3
 
-Direct citations and `assessment.claims` are canonicalized independently by nonblank `id` before
-counts, child composition, rendering, or events. Malformed rows and later duplicate ids are omitted;
-the first valid occurrence wins.
+Direct citations and `assessment.claims` are keyed independently by nonblank `id` before counts,
+rendering, or events. Usable display fields are captured once while emitted selected claim/citation
+objects retain their original identity. Malformed rows and later duplicate ids are omitted; the
+first valid occurrence wins.
 
 **Events:** `lr-citation-select` (`detail: CitationSelectEventDetail` from
 `@aceshooting/lyra-ui/ai` = `{ citation: Citation }`) — emitted when an evidence badge is activated.
 The inner `lr-citation-badge`'s generic activation is stopped at this composition boundary; this
-richer event exists because a bare `sourceId`/`index` pair can't tell a host which exact evidence
-_span_ to jump to. The composed `lr-claim-evidence` also surfaces
-`lr-claim-select` (`detail: { claim }`) unchanged when a claim is activated.
+richer event exists because a bare `sourceId`/`index` pair cannot identify the exact evidence span.
+The summary emits `lr-claim-select` (`detail: { claim }`) when a claim is activated.
 
 **Slots:** none.
 
@@ -69,7 +69,7 @@ row), `warnings` (omitted when there are none), `warnings-heading`, `warnings-co
 its semantics survive list-style resets),
 `evidence-item` (one `<li>` containing a badge + always-visible label/span text),
 `evidence-label` (omitted when `Citation.label` is unset), `evidence-span` (the formatted
-`Citation.span` range, omitted when unset), `claims` (the composed claim-evidence audit), `empty`
+`Citation.span` range, omitted when unset), `claims` (the claim/evidence region), `empty`
 (shown when `assessment` is `null`).
 
 **Themeable custom properties:** shared tokens only.

package/llms/components/lr-heatmap.md

@@ -33,6 +33,19 @@ Full canvas redraws pause while the host is outside the viewport. Data, locale,
 DPR invalidations remain pending and coalesce into one redraw when the heatmap intersects again;
 environments without `IntersectionObserver` retain eager drawing.
 
+Focus-only updates repaint a bounded neighborhood around the old and new cells, restoring all
+intersected neighboring fills and overlays while preserving the focus-ring geometry. Calendar axis
+pixels intersected by the repaint are restored too.
+
+Changing `domain` or `midpoint` without replacing matrix data preserves absent and nullish cells as
+no data in paint, accessible text, callbacks, and cell events. Missing values still use `-1` in
+default unsigned mode and `NaN` in signed mode; supplied negative signed values remain data.
+
+Invalid authored ramp colors retain the default endpoint fallback. The public `resolveRgb()` helper
+likewise preserves its supplied fallback bytes. These authoring diagnostics are once-per-color
+development warnings and remain silent in production; the separate missing-canvas runtime warning is
+unchanged.
+
 Set `accessibleCells: true` (`accessible-cells`) to opt into a semantic grid backed by a bounded
 window of native buttons. It retains the complete `aria-rowcount`/`aria-colcount` and arrow-key
 navigation model without mounting one node per cell. Buttons use localized `aria-label`s, explicit

package/llms/components/lr-histogram.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** `chart.js`, `chartjs-plugin-annotation`, `chartjs-plugin-datalabels`, `chartjs-plugin-zoom` — see `llms/peers.md`
-- **Themeable via** 16 parts, 35 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 16 parts, 36 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`
 
 ---
@@ -65,7 +65,7 @@ inherited from `LyraChart`, unaffected by the binning logic).
 `--lr-chart-data-table-button-active-bg`, `--lr-chart-data-table-toggle-hover-bg`,
 `--lr-chart-data-table-toggle-active-bg`, `--lr-chart-reset-zoom-button-hover-bg`,
 `--lr-chart-reset-zoom-button-active-bg`, `--lr-chart-canvas-hover-outline-width`, and
-`--lr-chart-pattern-step`, plus `--lr-chart-legend-side-max` — inherited from `LyraChart`, identical in meaning, together with the
+`--lr-chart-canvas-hover-outline-color`, `--lr-chart-pattern-step`, plus `--lr-chart-legend-side-max` — inherited from `LyraChart`, identical in meaning, together with the
 mirrored `--border-color-1`,
 `--border-color-2`,
 `--border-color-3`, `--border-color-4`, `--border-color-5`, `--border-color-6`, `--fill-color-1`,

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

@@ -22,6 +22,13 @@ slot when a form action is required. Because it is not form-associated, an ances
 `<fieldset disabled>` does not disable it and it is absent from `form.elements`; set `disabled`
 directly on each icon button.
 
+External descriptions follow the current source element identity when an element with the same ID
+replaces it, when a source is removed or reinserted, and when the control reconnects or moves to
+another document. Host-root lookup and ordering follow the current `aria-describedby` list,
+including unresolved IDs and duplicates. Switching between native button and anchor modes keeps the
+relationship on the current action. Existing accessible names and `aria-controls` relationships
+retain their separate contracts.
+
 Its public `--lr-icon-button-*` theme inputs stay undeclared on the host, so an ancestor theme
 wrapper can override the built-in fallbacks; a value set directly on the element still wins.
 

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

@@ -21,6 +21,15 @@ landing surface for `region`-anchored citations. Distinct from `<lr-svg-viewer>`
 documents) and `<lr-image-comparer>` (before/after slotted surfaces). Adopts `DocumentAnchorTarget`
 with `anchorKinds: ['region']` only — no text selection is bound.
 
+Disabled fit, rotate and annotate controls retain their resting paint on hover and press. Enabled
+controls keep their token-driven feedback.
+
+The annotation wrapper displays the shared token-driven focus ring in keyboard modality. The ring
+sits inside the wrapper so an image filling the scroll viewport cannot clip it. Annotation commands
+apply when that wrapper itself owns keyboard input. Enter on a highlight button activates that
+highlight without starting or committing an annotation, whether or not a draft exists; wrapper arrow
+commands retain physical image-coordinate semantics in both directions.
+
 **Properties:** `src: string = ''`, `name: string = ''`, `alt?: string`,
 `fit: LyraImageFit = 'contain' | 'width' | 'actual'` (reflected; invalid writes normalize to
 `contain`), `zoom: number = 1` (reflected), `minZoom: number = 0.5` (attribute

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;
@@ -73,7 +77,7 @@ announcement itself goes to the library's shared **light-DOM** assertive region,
 consumer's `<body>` and marked `data-lr-live-region="assertive"`, because a live region inside a
 shadow root is not reliably announced (JAWS with Firefox ignores one outright). What is announced
 is unchanged: only failures added or transitioned _after_ mount, so historical failed rows stay
-visible without being re-announced. Assert against that document-level region rather than
+visible without being re-announced. Read that document-level region rather than
 `::part(failure-live)`.
 
 In virtualized mode (above `virtualizeAt`) the rows live in the internal

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-intersection-observer.md

@@ -27,6 +27,15 @@ boolean = false` (reflected; unobserves a target after its first intersection).
 target stays consumed across option-driven observer rebuilds and disconnect/reconnect cycles;
 setting `once` to false is the explicit reset boundary.
 
+The browser capability is optional. A missing or throwing owner-window lookup or unavailable
+constructor leaves that rebuild inert rather than leaking an exception; an initial construction
+failure retries once with safe default options. Individual `observe`, `unobserve`, and `disconnect`
+failures are contained, so later valid targets and later rebuilds can still observe. Callbacks are
+tied to the current owner document, so a detached or adopted wrapper cannot emit a stale batch.
+Threshold collections inspect at most their first 10,000 direct data entries. Malformed or
+accessor-backed entries are skipped; a valid prefix remains active, while an entirely unusable value
+falls back to threshold `0`.
+
 **Events:** mapped `lr-intersect` once per entry with `{ entry }`, plus the existing batch alias
 `lr-intersection` with a frozen
 `Readonly<{ entries: readonly IntersectionObserverEntry[] }>` detail. The batch sequence is

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

@@ -18,12 +18,21 @@
 
 A collapsible, copyable tree view for an arbitrary JSON-serializable value (object, array, string,
 number, boolean, null, or `undefined`). Serves as a fallback renderer wherever a raw payload needs
-inspecting without a bespoke view. Expand/collapse state is keyed by structural path (not object
+inspecting without a bespoke view. Assignment creates one bounded, frozen graph from own enumerable
+data descriptors. It never invokes getters or object-conversion hooks; accessor/reflection-failed
+branches and function or symbol leaves are omitted, while bigint is retained as decimal text.
+Rendering, searching, toolbar copy, and per-node copy all use that same owned graph, so later
+mutation or revocation of the supplied object cannot change a displayed or copied value. Ordinary
+aliases, cycles, and sparse-array holes are retained. Expand/collapse state is keyed by structural path (not object
 identity), so it survives a `data` reassignment that keeps the same shape — e.g. a streaming result
 being patched in place. A container value that self-references (directly or through a longer cycle)
 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-base.md

@@ -35,7 +35,8 @@ errorMessage?: string }` (all four types exported here), where
   `syncStatus === 'error'`. `id`/`name` follow `DocumentRef`'s spirit, but a source is a _connector
   feeding_ documents, not a document, so the rest of the fields are its own
 - `label?: string` — heading text and the table's accessible name; omission uses the localized
-  knowledge-base label, while an explicit empty string stays empty
+  knowledge-base label. An explicit empty string keeps the visible heading empty while the nested
+  table still takes the localized default as its accessible name
 - `hideSummary: boolean = false` (attribute `hide-summary`, reflected) — hides the aggregate
   total/synced/syncing/needs-attention row
 - `hideCreate: boolean = false` (attribute `hide-create`, reflected) — hides the "Add source"
@@ -63,6 +64,14 @@ unset), `sync-cell`, `sync-badge`, `sync-timestamp`, `sync-error`, `health-cell`
 `document-count` (omitted when unset), `permission-badge` (omitted when `permission` is unset),
 `actions-menu`, `actions-trigger` (the kebab `<button>`).
 
+The 13 row parts — `name-cell`, `source-name`, `source-type`, `sync-cell`, `sync-badge`,
+`sync-timestamp`, `sync-error`, `health-cell`, `health-badge`, `document-count`,
+`permission-badge`, `actions-menu`, and `actions-trigger` — are forwarded from the composed table
+through `[part="table"]`/`exportparts`, so they are styleable as
+`lr-knowledge-base::part(actions-trigger)`. `actions-trigger` is the forwarded kebab button: it
+inherits the row font, has the shared `--lr-icon-button-size` minimum hit area (40px by default),
+and keeps independent hover, pressed, and focus treatment.
+
 **Themeable custom properties:** shared tokens only.
 
 **Optional peer deps:** none.

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-line-chart.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** `chart.js`, `chartjs-plugin-annotation`, `chartjs-plugin-datalabels`, `chartjs-plugin-zoom` — see `llms/peers.md`
-- **Themeable via** 16 parts, 35 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 16 parts, 36 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Documented with** `lr-bar-chart`, `lr-pie-chart`, `lr-doughnut-chart`, `lr-radar-chart`, `lr-polar-area-chart`, `lr-bubble-chart`, `lr-scatter-chart` (same section below)
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
@@ -58,7 +58,7 @@ failure transition is announced through the shared document-level light-DOM asse
 `--lr-chart-data-table-button-active-bg`, `--lr-chart-data-table-toggle-hover-bg`,
 `--lr-chart-data-table-toggle-active-bg`, `--lr-chart-reset-zoom-button-hover-bg`,
 `--lr-chart-reset-zoom-button-active-bg`, `--lr-chart-canvas-hover-outline-width`, and
-`--lr-chart-pattern-step`, plus `--lr-chart-legend-side-max` — all inherited from `LyraChart`, identical in meaning and default (see
+`--lr-chart-canvas-hover-outline-color`, `--lr-chart-pattern-step`, plus `--lr-chart-legend-side-max` — all inherited from `LyraChart`, identical in meaning and default (see
 `lr-chart` above); each of the eight variants below reads the same set, so one rule retunes them
 together. The mirrored hooks are `--border-color-1`,
 `--border-color-2`, `--border-color-3`, `--border-color-4`, `--border-color-5`,

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

@@ -76,7 +76,8 @@ passthrough). Not a subclass of `LyraChart`.
   more here than on `lr-chart`: this component exists to avoid the Chart.js peers, so without it an
   app that chose it for exactly that reason had to either hand-roll a `<details>` around a
   duplicated table or adopt `lr-chart` and pull in Chart.js for a button — the cheap component
-  stuck with the expensive workaround. Unset, nothing renders and behavior is unchanged.
+  stuck with the expensive workaround. A supplied `slot="data-table"` follows the same disclosure
+  state. Unset, nothing renders and behavior is unchanged.
   Themeable via `--lr-lite-chart-data-table-toggle-hover-bg` (default
   `var(--lr-color-brand-quiet)`) and `--lr-lite-chart-data-table-toggle-active-bg` (default: that
   hover colour mixed by `--lr-color-mix-active`).
@@ -134,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
@@ -143,19 +147,28 @@ 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) — applies to every interactive data mark for
-  both `type="bar"` and `type="line"`: matching bars and line points receive `data-selected` and
-  explicit `aria-pressed="true"`; all other marks render `aria-pressed="false"`. For a multi-series
-  chart, the category index selects the matching mark in every dataset. Empty is the default.
+- `selectedIndices: readonly number[] = []` (attribute: false) — names **source category indices**,
+  not positions in the sampled SVG output. Finite integer entries whose source rows are represented
+  in the bounded rendered sample select matching bars and line points, which receive
+  `data-selected` and explicit `aria-pressed="true"`; all other marks render `aria-pressed="false"`.
+  For a multi-series chart, a selected source category selects the matching rendered mark in every
+  dataset. Empty is the default.
   Style the built-in highlight through `--lr-lite-chart-selected-outline-color` and
   `--lr-lite-chart-selected-outline-width`. Note
   `::part(bar)[data-selected]` and `::part(point)[data-selected]` are **invalid CSS** — Shadow Parts
@@ -166,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
 
@@ -182,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.
 
@@ -96,6 +102,12 @@ raises `customError` and blocks submission, `''` restores the picker's own compu
 required picker with nothing committed goes back to `valueMissing`. It survives every
 `value`/`required` change and a form reset. `getForm()` returns the browser-resolved owning form.
 
+The open list is a nonmodal overlay: only its topmost owner handles Escape and outside pointer
+dismissal; Escape restores the trigger, while Tab keeps ordinary document navigation. Disconnect or
+cross-document adoption closes it. A required, uncommitted value recomputes its intrinsic localized
+message when `.strings` or the effective locale changes; an author custom-validity message retains
+priority until cleared.
+
 **Slots:** `label`, `hint`, `error`.
 
 **CSS parts:** `form-control`, `form-control-label`, `trigger`,