@aceshooting/lyra-ui 14.1.1 → 14.3.0

package/llms/components/lr-locale-picker.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** 12 parts, 16 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 13 parts, 16 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`
 
 ---
@@ -49,6 +49,14 @@ readonly LyraLocaleEntry[]`, `LyraLocaleEntry { tag: string; label?: string; cou
 - `showFlags: boolean = true` — each row's leading `<lr-flag language={tag} variant="compact">`
   (or `<lr-flag country={country} variant="compact">` when the entry sets `country`); `false`
   omits the flag element entirely (not just visually).
+- `triggerDisplay: LyraLocaleTriggerDisplay = 'flag-label'` (attribute `trigger-display`) —
+  `'flag' | 'label' | 'flag-label'`. The default keeps the flag, label and chevron. `label`
+  omits only the trigger flag; the menu keeps its flags and endonyms. `flag` centers the flag in
+  a square and hides the visible label and chevron. The `trigger-label` remains available to
+  assistive technology and describes the trigger's current language; its accessible name still
+  follows `label`/the host `aria-label`. The square uses the shared/scoped trigger height with a
+  24px floor. `showFlags=false` retains visible text in every mode. Selection, keyboard navigation,
+  form values and the uncommitted effective-locale preview keep their usual behavior.
 - `value: string = ''` — the **committed** selection (form value, drives `lr-change`). While `''`
   and untouched, the trigger _displays_ `effectiveLocale` as a preview label, but
   `checkValidity()`/`required` are governed by the real `value`, which stays `''` until a real
@@ -112,7 +120,8 @@ priority until cleared.
 
 **CSS parts:** `form-control`, `form-control-label`, `trigger`,
 `trigger-flag` (the trigger's leading `<lr-flag>` for the current value, present only while
-`showFlags` is on), `listbox`, `option`, `option-flag` (present only while `showFlags` is on),
+`showFlags` is on and `triggerDisplay` is not `label`), `trigger-label` (the current language,
+visually hidden in flag-only mode), `listbox`, `option`, `option-flag` (present only while `showFlags` is on),
 `option-label`, `option-tag` (the row's secondary line — the raw BCP-47 tag), `expand-icon`,
 `hint`, `error`.
 
@@ -137,6 +146,11 @@ quiet-brand, and semibold semantic tokens.
 peer warning duplication; `lr-flag` itself already logs one) when the optional
 `@aceshooting/lyra-flags` package isn't installed and `showFlags` is left on.
 
+A compact header can set `trigger-display="flag"` and
+`--lr-locale-picker-trigger-height: 2.25rem` for a 36px square at the usual 16px root size.
+Import `@aceshooting/lyra-ui/components/media/flag/flag-peer.js` to register the optional flag
+resolver. Menu labels stay visible; a per-entry `country` override also reaches the compact trigger.
+
 ```html
 <lr-locale-picker label="Language"></lr-locale-picker>
 <script type="module">

package/llms/components/lr-map.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** `maplibre-gl` — see `llms/peers.md`
-- **Themeable via** 15 parts, 6 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 20 parts, 6 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`
 
 ---
@@ -127,7 +127,8 @@ string; geojson: GeoJSON.FeatureCollection; field: string; stops: [number, strin
 - `dataLayers: LyraMapGeoJsonDataLayer[] = []` (attribute: false) —
   `LyraMapGeoJsonDataLayer { sourceId: string; geojson: GeoJSON.Feature |
 GeoJSON.FeatureCollection; tone?: 'accent' | 'success' | 'warning' |
-'danger' | 'neutral'; color?: string; strokeColor?: string; kind?: LyraMapDataLayerKind;
+'danger' | 'neutral'; color?: string; strokeColor?: string; line?: LyraMapLineOptions;
+point?: LyraMapPointOptions; kind?: LyraMapDataLayerKind;
 heatmap?: LyraMapHeatmapOptions; cluster?: LyraMapClusterOptions }`. `sourceId` is trimmed and must be nonempty; the first layer for a
   `sourceId` that is successfully admitted wins; blank, malformed, and later duplicate records are
   ignored without reserving an identity for a valid later sibling. Each retained entry adds one
@@ -212,6 +213,104 @@ intensity?: LyraMapHeatmapZoomValue; opacity?: number }`, where `LyraMapHeatmapZ
   peer's default untouched on construction, and dropping a previously-authored value restores 1.
   `cluster` is ignored on a heatmap entry: a heatmap already aggregates density, and clustering its
   input would feed it one point per cluster instead of the real distribution.
+  `line?: LyraMapLineOptions { field?: string; stops?: readonly (readonly [number, string])[];
+  width?: number; opacity?: number }` configures line/outline paint for an ordinary `dataLayers`
+  entry. `field` names a numeric feature property; two usable `[value, color]` stops produce a
+  continuous linear ramp. Missing, null, and non-numeric feature values use `strokeColor`, then
+  `color`, then `tone`. Stops inspect the first 64 entries, discard non-finite values and invalid
+  CSS colors, sort ascending, and retain the first duplicate threshold. Fewer than two stops or
+  an absent field preserves flat color. Values beyond the endpoints clamp to their endpoint color.
+  CSS variables resolve on the host during reconciliation and retheming. `width` defaults to 2 CSS
+  pixels and clamps to `[0, 200]`; `opacity` defaults to 1 and clamps to `[0, 1]`. Non-finite values
+  restore those defaults, as does dropping a previously-authored option. Point colors and polygon
+  fills are unaffected; cluster and heatmap entries ignore `line`.
+
+  `point?: LyraMapPointOptions` styles individual points on ordinary and clustered auto entries.
+  It is ignored for heatmaps. `field` names a **string** feature property; `colors` maps exact
+  `[category, CSS color]` pairs. Missing, unknown and non-string categories use the existing
+  `strokeColor`/`color`/`tone` fallback. The first 32 pairs are inspected and valid duplicates are
+  first-wins. CSS variables resolve on the host and follow ancestor theme changes. `radius`
+  defaults to 5 CSS pixels and `strokeWidth` to 0; both clamp to `[0, 200]`. `strokeColor` overrides
+  the outline only, with the layer's flat color as fallback. Dropping options restores defaults.
+
+  `radius` also accepts `LyraMapPointRadiusOptions { field, stops, interpolation?, fallback? }`
+  for **numeric** feature-driven sizes. `field` is independent of the category field. The first 32
+  pairs are inspected and finite `[value, radius]` pairs are sorted ascending; duplicate thresholds are first-wins and
+  radii clamp to `[0, 200]`. `interpolation` defaults to `'step'`: below the first threshold use
+  its radius, and each threshold is inclusive. `'linear'` interpolates between adjacent stops and
+  clamps outside the domain. One usable stop is a constant for numeric features. Missing, null,
+  non-numeric and non-finite feature values use `fallback` (default 5, clamped to `[0, 200]`), as
+  do an empty field, unusable stops or a linear domain that cannot retain distinct finite intervals.
+  Invalid interpolation values use step. These options style individual/unclustered points;
+  cluster-count radii remain independent. Switching back to a number or removing the radius
+  scale restores the fixed radius without recreating the source.
+
+  `point.icons` maps exact category values to `LyraMapPointIcon { value: string; path: string;
+  viewBox?: readonly [number, number, number, number]; mode?: LyraMapPointIconMode;
+  strokeWidth?: number; lineCap?: LyraMapPointIconLineCap; lineJoin?: LyraMapPointIconLineJoin }`.
+  `iconField` defaults to `field`. Each icon is **SVG path data**, not SVG markup or a URL. Copy an icon's path data,
+  combine filled subpaths in that string, and supply its `[minX, minY, width, height]` viewBox
+  (default `[0, 0, 24, 24]`). `mode` defaults to `'fill'`; `'stroke'` draws open outline paths,
+  and `'fill-stroke'` paints both. `strokeWidth` uses **viewBox units** (default 2, clamped to
+  `[0, 200]`; zero omits the stroke), so it scales with the icon. `lineCap` accepts `'butt'`,
+  `'round'`, or `'square'`; `lineJoin` accepts `'miter'`, `'round'`, or `'bevel'`. Both default
+  to round; miter joins retain a limit of 10. Invalid modes/caps/joins restore their defaults,
+  and a non-finite stroke width restores 2. Keep padding inside the viewBox for strokes at its
+  edges, which are clipped to the fixed atlas square. These are icon-path options;
+  `point.strokeWidth` and `point.strokeColor` continue to style the surrounding circle only.
+  The first 32 entries are inspected, valid duplicates are first-wins, path data is capped at
+  8192 characters, and viewBox coordinates must be finite within ±10000 with dimensions at least
+  0.001. Invalid paths are ignored; markup, external references and event handlers cannot execute.
+  Rasterization is synchronous and local, with no fetch or HTML/SVG document insertion.
+  `iconColor` supplies both fill and stroke ink, accepts CSS variables and defaults to the tone's contrasting foreground; `iconSize`
+  is the displayed bounding square in CSS pixels (default 16, clamped to `[1, 200]`). The fixed
+  64px raster preserves the viewBox aspect ratio. Unknown categories, invalid icons and partial
+  peers lacking image-atlas methods retain their colored circles. No sprite or glyph URL is needed.
+
+  All categories use the **same GeoJSON source** and cluster across categories. Cluster circles
+  keep the existing count-based styling; only unclustered points get category colors/icons.
+  An optional symbol layer and at most 32 images are allocated per configured source, with no
+  per-feature DOM markers. Data changes reuse the source, retheming updates paint/icon pixels,
+  and style reloads restore the owned resources. Removing the entry or icons releases its images.
+  `lr-map-click` on either a point's circle or icon returns `origin: 'data-layer'`, the public
+  `sourceId`, and the rendered feature. For clustered GeoJSON, use numeric feature IDs and keep
+  string business IDs in feature properties, as MapLibre's cluster tiling uses numeric IDs. Canvas export includes both; supply an accessible textual
+  legend/list for category interpretation and individual keyboard actions.
+
+  ```js
+  import '@aceshooting/lyra-ui/components/lr-map.js';
+  map.dataLayers = [{
+    sourceId: 'places', geojson: locations, cluster: {},
+    point: {
+      field: 'category',
+      radius: { field: 'visits', stops: [[0, 10], [10, 12], [50, 14], [100, 16]], fallback: 10 },
+      strokeWidth: 1,
+      colors: [['home', 'var(--lr-color-brand)'], ['work', 'var(--lr-color-success)']],
+      icons: [
+        { value: 'home', path: 'M2 12L12 2L22 12V22H2Z' },
+        { value: 'work', path: 'M8 6V3H16V6M3 6H21V21H3ZM3 11H21',
+          mode: 'stroke', strokeWidth: 1.75, lineCap: 'round', lineJoin: 'round' },
+      ],
+      iconSize: 14,
+    },
+  }];
+  ```
+
+  Share the same stops with `legendGradient` and set its endpoint labels for units. A gradient
+  matching a line ramp remains linear even alongside a logarithmic choropleth. Changing metric,
+  filtered GeoJSON, width or opacity reconciles existing resources; style reloads restore the layer.
+  Lines remain in MapLibre's canvas and can be captured with the map's normal render-event PNG
+  export flow.
+
+  ```js
+  mapElement.dataLayers = [{
+    sourceId: 'routes', geojson: routes,
+    line: { field: 'kmh', stops: speedStops, width: 4, opacity: 0.9 }
+  }];
+  mapElement.legendGradient = speedStops;
+  mapElement.legendGradientLoLabel = '0 km/h';
+  mapElement.legendGradientHiLabel = '100 km/h';
+  ```
 - `maxBounds: LyraMapBounds | null = null` (attribute: false) — box the map may not pan outside,
   `[[west, south], [east, north]]`. Prefer it over calling `map.setMaxBounds()` through the `.map`
   escape hatch: constraining the camera can wedge maplibre-gl at a sub-1 fractional zoom in a wide
@@ -254,7 +353,9 @@ payload beside the map.
 
 **Authoring types:** `LyraMapLegendEntry`, `LyraMapLegendPattern`, `LyraMapLegendProjection`, `LyraMapChoroplethLayer`,
 `LyraMapGeoJsonDataLayer`, `LyraMapDataLayerKind`, `LyraMapClusterOptions`, `LyraMapHeatmapOptions`,
-`LyraMapHeatmapZoomValue`, `LyraMapMarker`, `LyraMapMarkerActivationDetail`,
+`LyraMapHeatmapZoomValue`, `LyraMapLineOptions`, `LyraMapPointOptions`, `LyraMapPointRadiusOptions`,
+`LyraMapPointRadiusInterpolation`, `LyraMapPointIcon`, `LyraMapPointIconMode`,
+`LyraMapPointIconLineCap`, `LyraMapPointIconLineJoin`, `LyraMapMarker`, `LyraMapMarkerActivationDetail`,
 `LyraMapMarkerActivationSource`, `LyraMapStyleSpecification`, and `LyraMapInstance`.
 The former `LegendEntry`, `ChoroplethLayer`, `GeoJsonDataLayer`, and `MapMarker` names are removed
 in v9 rather than retained as aliases.
@@ -297,7 +398,18 @@ when `legend` and `legendGradient` are both empty.
 
 **CSS parts:** `base`, `container`, `legend`, `legend-swatch`, `legend-gradient`, `legend-lo`,
 `legend-hi`, `legend-limit`, `marker`, `popup`,
-`popup-content`, `popup-close-button`, `attribution`, `attribution-toggle`, `error`.
+`popup-content`, `popup-close-button`, `attribution`, `attribution-toggle`, `navigation`,
+`zoom-in`, `zoom-out`, `compass`, `scale`, `error`.
+The compact attribution summary has a decorative, current-color information glyph and retains
+MapLibre's accessible name, keyboard/touch disclosure behavior and attribution links. To make
+only this control compact, scope the shared target-size token to its public wrapper:
+
+```css
+lr-map::part(attribution) { --lr-icon-button-size: var(--lr-size-24px); }
+```
+
+Keep that target at least 24px in both axes. This leaves navigation controls at their existing size.
+
 `legend` is a localized `role="group"` containing a real list associated to the map canvas with
 `aria-describedby`; each entry is a `listitem`, decorative swatches are inert/accessibility-hidden,
 and the overlay is bounded to the map allocation with scrolling and long-label wrapping.
@@ -310,6 +422,21 @@ peer unavailable, owner-realm WebGL2 unavailable, or initialization failed. A po
 appended to the document's pre-mounted `[data-lr-live-region="assertive"]` sink rather than making
 shadow chrome live; raw caught errors are never exposed.
 
+**Standard peer controls:** after `lr-map-load`, narrow `.map` to the installed MapLibre peer
+and use `addControl(new NavigationControl(), 'bottom-right')` and
+`addControl(new ScaleControl({ unit: 'metric' }), 'bottom-left')`. No document-level peer CSS or
+shadow-root modification is needed: navigation buttons, compass glyph, scale bar and control
+corners are styled with Lyra tokens. The corners follow inline start/end under RTL. The legend
+reserves vertical room for these controls and attribution, including after resize or removal.
+Attribution also reserves legend space when it is the only control. Opposing occupied corners
+share the available width, so expanded attribution wraps without covering a scale or navigation
+control on the other side; controls stay aligned to their logical edge in both text directions.
+Navigation exposes `navigation`, `zoom-in`, `zoom-out`, and `compass` parts; the scale exposes `scale`.
+Button names update through `zoomIn`, `zoomOut`, and `mapResetNorth` locale strings. MapLibre retains
+keyboard activation, compass rotation, zoom limits, scale units and viewport updates. No controls
+are created until the application explicitly adds them. This is a supported imperative peer-control
+integration; there is no declarative controls property.
+
 **Themeable custom properties:**
 
 - `--lr-map-height` (default `var(--lr-size-24rem)`) — host block size, shared with the optional

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

@@ -25,8 +25,9 @@ Everything else is inherited verbatim from `lr-chart`; each name below has the s
 and behavior there. **See `llms/components/lr-chart.md` for the details, code example, and gotchas
 of every entry in these lists.**
 
-**Properties:** `description`, `grid`, `indexAxis` (`index-axis`), `label`, `hiddenDatasets`, `legendPosition`
-(`legend-position`), `max`, `min`, `plugins`, `scaleType` (`scale-type`), `annotations`,
+**Properties:** `description`, `grid`, `axes`, `compact`, `indexAxis` (`index-axis`), `label`, `hiddenDatasets`, `legendPosition`
+(`legend-position`), `hiddenDatums`, `legendMode` (`legend-mode`), `legendDisplay` (`legend-display`),
+`max`, `min`, `plugins`, `scaleType` (`scale-type`), `annotations`,
 `stacked`, `withoutAnimation` (`without-animation`),
 `withoutLegend` (`without-legend`), `withoutTooltip` (`without-tooltip`), `xLabel` (`x-label`),
 `yLabel` (`y-label`), plus additive `labels`, `datasets`, `valueFormatter`, `formatter`, `area`, `zoom`,
@@ -42,6 +43,8 @@ of every entry in these lists.**
 index, label, value }`), `lr-before-legend-visibility-change` (cancelable), and
 `lr-legend-visibility-change` (commit; both legend events carry `datasetIndex`, `visible`, and the
 complete `hiddenDatasets` snapshot).
+Radial category legends additionally emit `lr-before-datum-visibility-change` (cancelable) and
+`lr-datum-visibility-change`, carrying `index`, `visible` and the frozen `hiddenDatums` snapshot.
 
 **Slots:** default JSON configuration script, `data-table`, `center`.
 

package/llms/components/lr-polar-area-chart.md

@@ -25,8 +25,9 @@ Everything else is inherited verbatim from `lr-chart`; each name below has the s
 and behavior there. **See `llms/components/lr-chart.md` for the details, code example, and gotchas
 of every entry in these lists.**
 
-**Properties:** `description`, `grid`, `indexAxis` (`index-axis`), `label`, `hiddenDatasets`, `legendPosition`
-(`legend-position`), `max`, `min`, `plugins`, `scaleType` (`scale-type`), `annotations`,
+**Properties:** `description`, `grid`, `axes`, `compact`, `indexAxis` (`index-axis`), `label`, `hiddenDatasets`, `legendPosition`
+(`legend-position`), `hiddenDatums`, `legendMode` (`legend-mode`), `legendDisplay` (`legend-display`),
+`max`, `min`, `plugins`, `scaleType` (`scale-type`), `annotations`,
 `stacked`, `withoutAnimation` (`without-animation`),
 `withoutLegend` (`without-legend`), `withoutTooltip` (`without-tooltip`), `xLabel` (`x-label`),
 `yLabel` (`y-label`), plus additive `labels`, `datasets`, `valueFormatter`, `formatter`, `area`, `zoom`,
@@ -42,6 +43,8 @@ of every entry in these lists.**
 index, label, value }`), `lr-before-legend-visibility-change` (cancelable), and
 `lr-legend-visibility-change` (commit; both legend events carry `datasetIndex`, `visible`, and the
 complete `hiddenDatasets` snapshot).
+Radial category legends additionally emit `lr-before-datum-visibility-change` (cancelable) and
+`lr-datum-visibility-change`, carrying `index`, `visible` and the frozen `hiddenDatums` snapshot.
 
 **Slots:** default JSON configuration script, `data-table`, `center`.
 

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

@@ -25,8 +25,9 @@ Everything else is inherited verbatim from `lr-chart`; each name below has the s
 and behavior there. **See `llms/components/lr-chart.md` for the details, code example, and gotchas
 of every entry in these lists.**
 
-**Properties:** `description`, `grid`, `indexAxis` (`index-axis`), `label`, `hiddenDatasets`, `legendPosition`
-(`legend-position`), `max`, `min`, `plugins`, `scaleType` (`scale-type`), `annotations`,
+**Properties:** `description`, `grid`, `axes`, `compact`, `indexAxis` (`index-axis`), `label`, `hiddenDatasets`, `legendPosition`
+(`legend-position`), `hiddenDatums`, `legendMode` (`legend-mode`), `legendDisplay` (`legend-display`),
+`max`, `min`, `plugins`, `scaleType` (`scale-type`), `annotations`,
 `stacked`, `withoutAnimation` (`without-animation`),
 `withoutLegend` (`without-legend`), `withoutTooltip` (`without-tooltip`), `xLabel` (`x-label`),
 `yLabel` (`y-label`), plus additive `labels`, `datasets`, `valueFormatter`, `formatter`, `area`, `zoom`,
@@ -42,6 +43,8 @@ of every entry in these lists.**
 index, label, value }`), `lr-before-legend-visibility-change` (cancelable), and
 `lr-legend-visibility-change` (commit; both legend events carry `datasetIndex`, `visible`, and the
 complete `hiddenDatasets` snapshot).
+Radial category legends additionally emit `lr-before-datum-visibility-change` (cancelable) and
+`lr-datum-visibility-change`, carrying `index`, `visible` and the frozen `hiddenDatums` snapshot.
 
 **Slots:** default JSON configuration script, `data-table`, `center`.
 

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

@@ -25,8 +25,9 @@ Everything else is inherited verbatim from `lr-chart`; each name below has the s
 and behavior there. **See `llms/components/lr-chart.md` for the details, code example, and gotchas
 of every entry in these lists.**
 
-**Properties:** `description`, `grid`, `indexAxis` (`index-axis`), `label`, `hiddenDatasets`, `legendPosition`
-(`legend-position`), `max`, `min`, `plugins`, `scaleType` (`scale-type`), `annotations`,
+**Properties:** `description`, `grid`, `axes`, `compact`, `indexAxis` (`index-axis`), `label`, `hiddenDatasets`, `legendPosition`
+(`legend-position`), `hiddenDatums`, `legendMode` (`legend-mode`), `legendDisplay` (`legend-display`),
+`max`, `min`, `plugins`, `scaleType` (`scale-type`), `annotations`,
 `stacked`, `withoutAnimation` (`without-animation`),
 `withoutLegend` (`without-legend`), `withoutTooltip` (`without-tooltip`), `xLabel` (`x-label`),
 `yLabel` (`y-label`), plus additive `labels`, `datasets`, `valueFormatter`, `formatter`, `area`, `zoom`,
@@ -42,6 +43,8 @@ of every entry in these lists.**
 index, label, value }`), `lr-before-legend-visibility-change` (cancelable), and
 `lr-legend-visibility-change` (commit; both legend events carry `datasetIndex`, `visible`, and the
 complete `hiddenDatasets` snapshot).
+Radial category legends additionally emit `lr-before-datum-visibility-change` (cancelable) and
+`lr-datum-visibility-change`, carrying `index`, `visible` and the frozen `hiddenDatums` snapshot.
 
 **Slots:** default JSON configuration script, `data-table`, `center`.
 

package/llms/components/lr-slider.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** 25 parts, 24 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 26 parts, 24 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`
 
 ---
@@ -113,6 +113,15 @@ single numeric string entry.
 - `showValue: boolean = false` (attribute `show-value`) — opt-in numeric readout next to the track;
   a range readout joins both values with an en dash. The explicit HTML spelling
   `show-value="false"` stays false.
+- `valueDisplay: SliderValueDisplay = 'numeric'` (attribute `value-display`) — `'numeric' |
+  'formatted'`. Opt into `formatted` to reuse `valueFormatter` (or `tooltipFormatter` when no
+  value formatter is supplied) for the visible readout too. Each range handle is formatted
+  separately; nullish results fall back to localized numbers. Existing ARIA and tooltip behavior
+  is unchanged. The callback owns its unit labels and locale formatting.
+- `valuePlacement: SliderValuePlacement = 'inline'` (attribute `value-placement`) — `'inline' |
+  'label'`. With `showValue`, `label` places the readout opposite the label in a wrapping row that
+  follows RTL. The readout stays outside the accessible label. These presentation options update
+  on live `lr-input` changes without changing the commit-only `lr-change` contract.
 - `value: number = 0`, `defaultValue: number = 0` (attribute `value`), `valueAsNumber: number`, and
   `valueAsString: string` are synchronized and finite. Values normalize the low/high domain, snap
   to the grid anchored at the low endpoint, then clamp so a non-grid endpoint remains reachable;
@@ -165,7 +174,8 @@ live value bubble per handle, present only with `with-tooltip`), `tooltip-visibl
 `tooltip` element's part list_ while that handle is focused or dragged — visibility is encoded in
 the part name because `::part(tooltip)[data-visible]` is invalid CSS and never matches; write
 `::part(tooltip-visible)`). The tooltip also exposes `tooltip__tooltip`, `tooltip__content`, and
-`tooltip__arrow`. `value` is the opt-in numeric readout.
+`tooltip__arrow`. `value` is the opt-in readout; `label-row` contains the separate label and value
+nodes when `showValue` and `valuePlacement="label"` are enabled.
 
 **CSS custom states:** `disabled`, `dragging`, `focused`, `required`, `optional`, `valid`,
 `invalid`, `user-valid`, and `user-invalid`. A slider always has a finite numeric value, so
@@ -270,8 +280,14 @@ is present for upstream form-surface parity but adds no missing-value constraint
   value); ArrowUp/ArrowDown are never swapped, since direction only affects the horizontal inline axis.
 - Changing `min`/`max`/`step` after mount automatically re-clamps/re-snaps the current `value` in the
   next update — narrowing the domain can silently move the slider's value.
-- `valueFormatter` is presentation-only: `aria-valuenow`, the visible numeric readout, geometry,
-  form value, and emitted values stay numeric. With no formatter, `aria-valuetext` remains the
+- `valueFormatter` is presentation-only: `aria-valuenow`, geometry, form value, and emitted values
+  stay numeric. The visible readout stays numeric unless `valueDisplay="formatted"` is set.
+- Numeric value/domain assignments in the same Lit update batch are normalized against the final
+  `min`, `max`, and `step`, regardless of binding order. Await `updateComplete` to read the settled
+  scalar or range endpoints. Immediate imperative readback remains clamped to the current domain;
+  separate update batches intentionally normalize independently. Programmatic normalization emits
+  no user input/change event.
+  With no formatter, `aria-valuetext` remains the
   numeric string rendered by earlier versions; a nullish formatter result omits it.
 - A pointer drag fires `lr-input` continuously and a single `lr-change` on release; a keyboard step
   fires exactly one of each per press, but OS key-repeat while a key is held re-fires `lr-input` on

package/llms/components/lr-table.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** 34 parts, 18 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 36 parts, 18 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`
 
 ---
@@ -146,6 +146,10 @@ cell: (row) => unknown }` —
   the two consequences of the fixed algorithm worth knowing before opting in
 - `sortKey: string = ''` (attribute `sort-key`)
 - `sortDir: 'asc'|'desc' = 'asc'` (attribute `sort-dir`)
+- `sortIndicators: TableSortIndicators = 'active'` (attribute `sort-indicators`) — `'all'` adds a
+  muted bidirectional indicator to each inactive sortable header, reserving the same space as the
+  active chevron. The default retains only the active column's indicator. This presentation does
+  not change keyboard interaction, client/server sorting, or `aria-sort="none"` on inactive columns.
 - `sortMode: 'client'|'server' = 'client'` (attribute `sort-mode`, reflected) — mirrors
   `paginationMode`'s identical split. `'client'` (the default) orders `rows` in the browser from
   `sortKey`/`sortDir` and the active column's `sortValue`; `'server'` renders `rows` exactly as
@@ -316,8 +320,9 @@ slot-replaceable: it reports a configuration problem (`noColumnsHeading`), not "
 nothing", and one slot covering all three would collapse that distinction. Everything else comes
 from `columns`/`rows`.
 
-**CSS parts:** `base`, `table`, `caption`, `head`, `header-cell`, `row`, `cell`, `more-button`, `sort-icon` (a
-chevron indicator shown on the active sortable header, rotated per `sortDir`), `reveal-columns-button`
+**CSS parts:** `base`, `table`, `caption`, `head`, `header-cell`, `row`, `cell`, `more-button`, `sort-icon`
+(each sort indicator), `sort-icon-active` (the active chevron, rotated per `sortDir`),
+`sort-icon-inactive` (the muted bidirectional indicator under `sort-indicators="all"`), `reveal-columns-button`
 (shown when priority columns are hidden or when a narrow allocation is currently force-visible),
 `foot` (the `<tfoot>`, only rendered when at least one
 column defines `footer`), `footer-row`, `footer-cell`, `row-total-cell` (each body row's trailing
@@ -387,7 +392,8 @@ or structural-pseudo-class selector and does not affect group, expanded, hover,
 showing through the sticky header while it scrolls.
 Same shape and rationale as `--lr-table-row-selected-bg`: inline `var()` fallbacks, not on `:host`,
 because `::part(header-cell)[aria-sort]` is invalid CSS. The `sort-icon` part styles only the
-chevron; these tokens style the header cell itself.
+indicator; these tokens style the header cell itself. Use `::part(sort-icon-inactive)` and
+`::part(sort-icon-active)` to style the two indicator states without private selectors.
 `--lr-table-sticky-offset` (default `0`) is measured and written inline per column by the component
 so multiple `sticky` columns stack instead of overlapping; it is a read-out, not a knob you set.
 `--lr-table-heat-t` is likewise component-written (each `[data-heat]` cell's position on the ramp).