@seed-ship/mcp-ui-solid 6.22.0 → 6.24.0

package/CHANGELOG.md

@@ -5,6 +5,220 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [6.24.0] - 2026-10-03
+
+Explicit missing values in charts and tables, and a unit per chart — lot 1 of
+the GeoAI display brief (`deposium_geoai/docs/handoffs/2026-10-03-mcp-ui-geoai-display-brief.md`).
+Released with `@seed-ship/mcp-ui-spec` 5.7.0, whose chart schema accepts both;
+the dependency floor moves to `^5.7.0`.
+
+### The rule
+
+Absence is never zero. A `null` keeps its slot — its label stays on the axis,
+its row stays in the table — and every view marks it, visibly and for screen
+readers. Until now `validateComponent` refused any chart carrying a `null`, so
+a host that drops invalid components (Deposium's chat does) showed nothing.
+
+Only an explicit entry is a missing value: `null` (or a non-finite number, or a
+point whose `y` is one). A dataset with no entry at all (`data: []`) is not —
+it renders exactly as it did in 6.23.0.
+
+### Added
+
+- **Charts accept `null`** in line, bar, radar, scatter and bubble datasets,
+  as a number slot or as a point's `y`:
+  - a line or a radar breaks at the missing value: `spanGaps: false` is set on
+    every dataset of a chart that has one, so nothing joins the neighbours,
+    and the date stays on the axis;
+  - a missing bar is drawn as a dashed outline at the baseline, so it cannot
+    be read as a zero bar (Chart.js draws nothing for both). Stacked or
+    overlaid bars get no outline — their baseline belongs to the series below,
+    so an outline there would point at the wrong series — and their note says
+    the values are not plotted;
+  - scatter and bubble charts leave the point out;
+  - a series whose every entry is missing keeps its legend entry, marked
+    `chartLegendNoData` ("(no data)"), and a chart with nothing to plot says
+    so in its plot area (`chartNoData`);
+  - a note under the chart explains how this chart shows a missing value
+    (`chartMissingGaps`, `chartMissingBars`, `chartMissingPoints`), shown when
+    a reader can actually see the mark, and names the series with no data
+    (`chartSeriesNoData`, joined with `Intl.ListFormat` in the strings
+    `locale`). The canvas's `aria-describedby` includes it. DOM hooks:
+    `[data-mcp-chart-notes]` and
+    `[data-mcp-chart-note="gaps|bars|omitted|no-data"]`;
+  - a tooltip names a missing bar (`missingValue`) instead of printing `0`.
+
+  Pie, doughnut and polar-area charts refuse `null`, as a bare value or as a
+  point's `y`, because Chart.js parses a missing share as `0` and would draw
+  every other share wrong. `validateChartComponent` reports
+  `MISSING_VALUE_UNSUPPORTED`. If a host bypasses validation, the renderer
+  shows its data table with `chartMissingUnsupported` instead of a misleading
+  chart.
+- **`unit`** on chart params: the value-axis title (bar, line, scatter and
+  bubble, unless `options.scales` already sets one), the tooltip value
+  (`chartValueWithUnit`, except on scatter and bubble, whose value is a pair)
+  and the column headers of the data view and of the degraded table
+  (`chartLabelWithUnit`). `validateChartComponent` reports `INVALID_UNIT` for
+  a non-string unit or one longer than 32 characters; an empty string is
+  tolerated and means "no unit".
+- **Tables.** A cell that already displayed as `-` — `null`, `undefined`, an
+  empty or whitespace-only string, `"undefined"` (after the backend's
+  `"X – undefined"` debris is stripped) or a literal `-` — is now muted,
+  hidden from assistive technology and followed by a visually-hidden
+  `missingValue`. A legend (`missingValueLegend`, `[data-mcp-missing-legend]`)
+  follows any table with such a cell. It is computed on every row, so it does
+  not flicker while paging. Missing cells sort last in both directions (an
+  empty string no longer sorts as `0`), a numeric column is detected from its
+  first present value, and search never matches a missing cell.
+- **The chart data view and the degraded tables** mark missing cells the same
+  way, under the same legend. `chartToDataTable` and `chartToDegradedTable`
+  return an extra `missing` matrix shaped like `rows`, which still hold `''`.
+  One exception: the degraded table prints point data (scatter, bubble,
+  `{x, y}` series) as JSON, where `"y":null` reads as such, and does not mark
+  it. `DegradedFallback` takes an optional `missing` prop; the graph and map
+  degraded tables do not change.
+- Ten `MCPUIStrings` keys (275 → 285), English defaults, French in the README
+  dictionary: `missingValue`, `missingValueLegend`, `chartMissingGaps`,
+  `chartMissingBars`, `chartMissingPoints`, `chartSeriesNoData`,
+  `chartLegendNoData`, `chartValueWithUnit`, `chartLabelWithUnit`,
+  `chartMissingUnsupported`.
+- `examples/geoai-daily-forecast/`: a synthetic, clearly labelled GeoAI pilot
+  (daily table, one chart per variable, comparison, map, thresholds, sources
+  and limits) built with `createComparisonLayout`, `createGeographyLayout` and
+  `createEvidenceLayout`, with tests for the brief's validation criteria that a
+  library can check. Not published, since it is outside `files`;
+  type-checked by `pnpm typecheck` (`tsconfig.examples.json`).
+
+### Unchanged on purpose
+
+- A chart with no missing entry and no unit builds exactly the 6.23.0
+  Chart.js config, and a table with no missing cell renders the 6.23.0 DOM
+  (both tested; the table against a capture taken before the change).
+- `renderCellValue` still returns `-` for a missing value; it now shares its
+  `"X – undefined"` cleanup with the table marks, so both always agree. CSV
+  and TSV exports still write an empty field, JSON still writes `null`.
+- Chart.js's default interaction (`nearest`, `intersect: true`) is kept. A
+  missing bar has no height, so its tooltip only appears in `index` mode.
+- No time axis is introduced: daily dates are categorical ISO labels. The
+  opt-in QuickChart renderer receives the payload as before; the unit and the
+  missing-value outlines, notes and legend belong to the native renderer.
+
+### Changed — for code that reads these types
+
+- `ChartComponentParams` datasets' `data` is now `Array<number | null>`, or
+  points whose `y` is `number | null`. Code that reads chart payloads under
+  `strictNullChecks` has to handle the missing value.
+- `chartToDataTable` and `chartToDegradedTable` always return the extra
+  `missing` matrix; code asserting their exact shape sees one more key.
+- `ChartDataTableLabels.withUnit` and `DegradedProjectionLabels.withUnit` are
+  new **optional** fields, so a complete labels table written for
+  6.20.0–6.23.0 as an object literal still type-checks (a
+  `Record<keyof …, string>` does not, as with any new key).
+  `CHART_DATA_TABLE_LABELS` and `DEGRADED_PROJECTION_LABELS` are now typed
+  `Required<…>`.
+- The `INVALID_DATA_TYPE` and `INVALID_POINT_DATA` messages now mention
+  `null`; the codes do not change.
+
+### For hosts
+
+- **Deposium (consumer):** bump to 6.24.0 and add the ten keys to the French
+  dictionary; `satisfies Required<MCPUIStrings>` fails until they are there.
+  The visually-hidden text uses an inline style, not Tailwind's `sr-only`, so
+  the Tailwind configuration needs no change.
+- **Producers:** emit `null` only in line, bar, radar, scatter and bubble
+  charts, never `0` for a missing value and never a shortened array. A
+  hand-copied schema mirror needs both `null` and `unit` (see the spec 5.7.0
+  changelog).
+
+## [6.23.0] - 2026-09-18
+
+### Added
+
+- Opt-in `MCPUIMathProvider` and `MathRenderer` for markdown text and table
+  cells, including virtualized tables; separate optional `/plugins/katex`
+  adapter. No new required config fields and no KaTeX import from the root.
+- Bounded dollar-delimited math parsing, currency guards, isolated Marked
+  instances, sanitized MathML-only rendering and literal fallback. Styles,
+  annotation subtrees, executable markup and trusted TeX commands stay blocked.
+- SSR keeps escaped source until the existing client hydration upgrade;
+  original text/data is retained for copy and export. No CSS or font install.
+- Optional KaTeX peer pinned to 0.18.4 to preserve Node 20 installation
+  compatibility; later 0.18.x releases currently require Node >=22.12 via
+  Commander. Cell links retain the existing new-tab, rel and styling policy.
+
+## [6.22.1] - 2026-09-18
+
+Fixes a typing regression 6.22.0 introduced. Runtime behaviour is identical.
+
+### The mistake
+
+6.22.0 made every `MCPUIConfig` field optional so that adding a policy key
+would stop breaking consumers who *author* a complete config. That fixed one
+direction and broke the other: `MCPUIConfig` is a published type, so anyone who
+*reads* one — `const policy: IframePolicy = config.iframePolicy` — suddenly
+faced `… | undefined` and stopped compiling under `strictNullChecks`. Trading
+one compile break for the opposite one is not a fix.
+
+The two demands genuinely conflict, and one name cannot serve both: an author
+must be allowed to omit a key, a reader must never meet `undefined`.
+
+### The fix — two names
+
+- **`MCPUIConfigInput`** (new, exported): what a host writes. Every field
+  optional, so a new policy key is always additive. This is what
+  `MCPUIConfigProvider`'s `config` prop takes. Note it is NOT what
+  `MCPUIConfigContext.Provider` takes — see below.
+- **`MCPUIConfig`**: what the library hands back — an interface extending
+  `Required<MCPUIConfigInput>`, every key present, which is the 6.21.0 meaning
+  restored. Keeping it an interface also preserves consumer extension and
+  declaration merging. `useMCPUIConfig()`, `DEFAULT_MCPUI_CONFIG` and
+  `MCPUIConfigContext` carry it.
+
+`MCPUIConfigContext` keeps the resolved type on purpose: it is exported, so
+`useContext(MCPUIConfigContext)` is a public read surface and typing it with the
+input view would leave a direct reader on `IframePolicy | undefined` — the very
+regression being undone. A host that bypasses `MCPUIConfigProvider` therefore
+passes a complete value, `{ ...DEFAULT_MCPUI_CONFIG, ...mine }`; passing only
+some keys is what the provider's `config` prop is for. `useMCPUIConfig()` still
+merges at runtime, so an untyped host cannot break a renderer.
+
+Derived rather than declared twice, so a key is written once and the two views
+cannot drift. The guard test now pins **both** halves: every `MCPUIConfigInput`
+field stays optional, and `MCPUIConfig` stays an interface extending
+`Required<…>`. The contract typecheck also pins interface extension and
+declaration merging. Both sides were verified to fail when their corresponding
+regression is reintroduced.
+
+### How this got through
+
+Through 6.22.0, `pnpm typecheck` ran the main `tsconfig.json` alone, and that
+config excludes `**/*.test.ts(x)`: a type-level claim written in a test file
+failed nothing. 6.22.0 shipped both a broken `MCPUIConfig` and a fixture
+annotated with the wrong type, and neither `typecheck` nor `test` said a word.
+`typecheck` now runs a second pass, `tsconfig.contracts.json`, which
+type-checks the handful of test files whose `satisfies` and annotations *are*
+the test. Including every test file instead would surface 53 unrelated errors,
+so that stays a separate piece of work.
+
+### Upgrading
+
+Reading is exactly as it was in 6.21.0, whether through `useMCPUIConfig()`,
+`useContext(MCPUIConfigContext)` or a value typed `MCPUIConfig`.
+`MCPUIConfigProvider`'s `config` prop still accepts everything it accepted
+before, `Partial<MCPUIConfig>` included.
+
+Two authoring patterns stop compiling, coming from 6.21.0 or from 6.22.0:
+
+- **A config annotated `MCPUIConfig`.** From 6.22.0 a partial one fails; from
+  6.21.0 a complete one fails too, since it lacks `chartZoom`. Annotate it
+  `MCPUIConfigInput` instead.
+- **A value handed straight to `<MCPUIConfigContext.Provider>`**, annotated or
+  not: an inline literal fails the same way. Spread the defaults,
+  `{ ...DEFAULT_MCPUI_CONFIG, ...mine }`, or pass the keys to
+  `<MCPUIConfigProvider config={…}>`, which does that merge for you.
+
+Both replacements keep compiling when the library adds its next policy key.
+
 ## [6.22.0] - 2026-09-18
 
 Wheel zoom and drag pan on the surfaces that could not be read when the content
@@ -50,6 +264,11 @@ expanded view only, and why inline zoom is opt-in.
 
 ### Changed
 
+> **Superseded by 6.22.1.** Making the fields of the published `MCPUIConfig`
+> optional broke every consumer that *reads* one. 6.22.1 moves the optional
+> fields to a new `MCPUIConfigInput` and restores `MCPUIConfig` as the
+> resolved type. The entry below describes 6.22.0 as published.
+
 - **Every `MCPUIConfig` field is now optional**, as `MCPUIStrings` has always
   been. `MCPUIConfig` grows a key in a minor release each time the library
   gains a policy switch — `iframeFallbackLink` in 6.21.0, `chartZoom` here —

package/README.md

@@ -5,6 +5,75 @@ SolidJS components + chat toolkit for MCP-generated UI. Part of the [MCP UI ecos
 [![npm version](https://img.shields.io/npm/v/@seed-ship/mcp-ui-solid.svg)](https://www.npmjs.com/package/@seed-ship/mcp-ui-solid)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 
+## What's New in v6.24.0
+
+Explicit missing values in charts and tables, and a `unit` per chart. A `null`
+in a line, bar, radar, scatter or bubble dataset is now accepted and shown as
+missing, never as zero. Lines break, a missing bar gets a dashed outline, and a
+note under the chart says how. Table cells with no value are announced to
+screen readers and explained by a legend. Ten new `MCPUIStrings` keys; requires
+`@seed-ship/mcp-ui-spec` 5.7.0. See
+[Missing values and units in charts](#missing-values-and-units-in-charts-v6240).
+
+## What's New in v6.23.0
+
+Opt-in LaTeX in markdown text components and table cells, with the same
+currency guards and sanitized MathML output. No change without a provider;
+`MCPUIConfig` is unchanged. See [Math rendering](#math-rendering).
+
+## Math rendering
+
+Install the optional peer only if the host wants the supplied KaTeX adapter:
+
+```bash
+pnpm add --save-exact katex@0.18.4
+```
+
+```tsx
+import { MCPUIMathProvider, UIResourceRenderer } from '@seed-ship/mcp-ui-solid'
+import { renderKatexMath } from '@seed-ship/mcp-ui-solid/plugins/katex'
+
+<MCPUIMathProvider renderMath={renderKatexMath}>
+  <UIResourceRenderer content={resource} />
+</MCPUIMathProvider>
+```
+
+The adapter's optional peer is pinned to 0.18.4 to retain Node 20 installation
+compatibility. KaTeX 0.18.5–0.18.7 pull in Commander 15 (Node >=22.12);
+do not replace the pin with a caret range on Node 20.
+
+The provider applies to `text` with `markdown: true` and string-valued table
+cells, including virtualized rows. It recognizes `$...$` inline and `$$...$$`
+display formulas in their own paragraph (not embedded mid-sentence).
+Code spans/fences and link destinations are not formulas;
+currency such as `$5` and `$5-$10` remains text. Malformed/incomplete formulas
+degrade to their source. Copy/export continues to use the original data.
+Dollar syntax can be ambiguous: `$5$` is a formula. Escape a literal dollar
+as `\$` when composing currency and formulas; numeric math such as `$2 + 3$`
+remains supported. Math-enabled cell links keep their existing new-tab behavior.
+
+The adapter emits **MathML only**: no KaTeX stylesheet, fonts, CDN requests,
+HTML layout or inline styles. Native MathML rendering varies by browser and
+may differ from the chat's HTML+MathML layout. There is no automatic loading:
+the explicit plugin import is the opt-in dependency boundary; hosts can load
+that module before mounting the provider if they want a separate chunk.
+
+Alternatively pass a synchronous `MathRenderer` function returning MathML
+(`(tex, { displayMode }) => string | null`). The library still sanitizes it;
+return `null` or throw to retain literal source. Passing `null` (or omitting
+`renderMath`) on a nested provider disables inherited math. Arbitrary Marked
+extensions and sanitizer overrides are deliberately not public API.
+
+On the server, escaped source is emitted without calling the renderer. The
+existing `SafeHtml` client upgrade renders sanitized formulas after hydration.
+Processing is bounded to 100,000 source characters, 4,096 per expression and
+128 expressions per parse; oversized input stays escaped text. The adapter
+also limits macro expansion and dimensions, disables trusted commands, and
+does not share macro definitions across formulas. TeX annotation subtrees are
+removed rather than exposing duplicate source after sanitization.
+
+See the [design and integration handoff](./docs/briefs/LATEX-MATHML-2026-09-18.md).
+
 ## What's New in v6.21.0
 
 - **Iframes work under `Cross-Origin-Embedder-Policy: credentialless`.** Both
@@ -656,6 +725,73 @@ Requires `protomaps-leaflet` peer dependency.
 }} />
 ```
 
+## Missing values and units in charts (v6.24.0)
+
+`null` in a chart dataset is an **explicit missing value**: the value belongs
+to the series' grid (its label stays on the axis) but was not observed. Send
+`null` rather than `0`, and rather than a shorter array, whenever a value is
+absent; a series with no value at all is all `null`.
+
+```tsx
+<UIResourceRenderer content={{
+  id: 'wind',
+  type: 'chart',
+  position: { colStart: 1, colSpan: 12 },
+  params: {
+    type: 'line',
+    title: 'Wind speed',
+    unit: 'km/h',
+    data: {
+      labels: ['2026-10-04', '2026-10-05', '2026-10-06'],
+      datasets: [
+        { label: 'Lyon', data: [18, null, 31] },   // a hole on day 2
+        { label: 'Brest', data: [null, null, null] }, // no value at all
+      ],
+    },
+  },
+}} />
+```
+
+| Chart type | A missing value is drawn as | Note under the chart |
+|---|---|---|
+| `line`, `radar` | a break in the line — never joined to its neighbours (`spanGaps: false` is forced) | `chartMissingGaps` |
+| `bar` | a dashed outline at the baseline, so it cannot read as a zero bar | `chartMissingBars` |
+| `scatter`, `bubble` | nothing: the point is not plotted | `chartMissingPoints` |
+| `bar` with `stacked` scales | nothing: the baseline belongs to the series below, so no outline is drawn | `chartMissingPoints` |
+| `pie`, `doughnut`, `polarArea` | refused: Chart.js would draw a missing share as `0` — validation reports `MISSING_VALUE_UNSUPPORTED` | — |
+
+A series whose every entry is `null` keeps its legend entry, marked
+`chartLegendNoData`, and is named in a `chartSeriesNoData` note. A chart with
+nothing to plot says `chartNoData` in its plot area. Only an explicit entry is
+a missing value: a dataset with no entry (`data: []`) renders as it always
+did. The notes are linked to
+the canvas through `aria-describedby`, and the **Data** view marks every
+missing cell with the same `-` and screen-reader text as the table component,
+under a `missingValueLegend` line.
+
+`unit` (one per chart — split values with different units into separate
+charts) titles the value axis unless `options.scales` already does, follows
+each tooltip value (`chartValueWithUnit`), and joins the data-view column
+headers (`chartLabelWithUnit`).
+
+Daily series read best with ISO dates as plain category labels, as above:
+`timeAxis` needs a Chart.js date adapter the host must register itself.
+
+Tables follow the same rule: a cell that displays as `-` — `null`,
+`undefined`, an empty or whitespace-only string, `"undefined"`, or a literal
+`-` — shows a muted `-` with a visually-hidden `missingValue`, a
+`missingValueLegend` line follows the table, missing cells sort last, and
+search never matches them.
+
+The outlines, notes, legend marks and `unit` belong to the native Chart.js
+renderer. The opt-in QuickChart renderer receives the payload as is.
+
+A synthetic, end-to-end example — daily table, one chart per variable,
+comparison, map, thresholds, sources and limits, built with the three
+presentation recipes — lives in
+[`examples/geoai-daily-forecast/`](./examples/geoai-daily-forecast/) (not
+published; its tests run with the package's).
+
 ## Chat Bus — Agent Interactions (`@experimental`)
 
 Bidirectional event/command system for agent-driven chat interactions. Your app keeps full control of its chat UI — the bus adds structured interactivity on top.
@@ -1029,6 +1165,48 @@ import { MCPUIConfigProvider } from '@seed-ship/mcp-ui-solid'
 </MCPUIConfigProvider>
 ```
 
+When you keep a partial configuration in a variable, name the authored,
+all-optional view explicitly:
+
+```tsx
+import {
+  MCPUIConfigProvider,
+  type MCPUIConfigInput,
+} from '@seed-ship/mcp-ui-solid'
+
+const config: MCPUIConfigInput = {
+  iframeCredentialless: 'always',
+  chartZoom: 'never',
+}
+
+<MCPUIConfigProvider config={config}>
+  <App />
+</MCPUIConfigProvider>
+```
+
+Prefer `MCPUIConfigProvider` for partial overrides. The exported raw context is
+also a public read surface, so its `Provider` requires the complete, resolved
+`MCPUIConfig` value. If an integration must provide that context directly,
+spread the defaults first:
+
+```tsx
+import {
+  DEFAULT_MCPUI_CONFIG,
+  MCPUIConfigContext,
+} from '@seed-ship/mcp-ui-solid'
+
+<MCPUIConfigContext.Provider
+  value={{ ...DEFAULT_MCPUI_CONFIG, iframeCredentialless: 'always' }}
+>
+  <App />
+</MCPUIConfigContext.Provider>
+```
+
+`MCPUIConfigInput` contains the library's built-in authoring fields.
+`MCPUIConfig` remains an interface for consumers that extend or augment the
+resolved contract; `MCPUIConfigProvider` also accepts those augmented fields
+as partial inline overrides.
+
 | Option | Values | Default | What it does |
 |--------|--------|---------|--------------|
 | `iframeCredentialless` | `'auto'` \| `'always'` \| `'never'` | `'auto'` | `'auto'`: the attribute on the `iframe` component when its host is **not** in `TRUSTED_IFRAME_DOMAINS` (+ `customTrustedIframeDomains`) — those frames already run without cookies. The video embed is excluded, since it has none of that sandboxing. `'always'`: every iframe, video and trusted hosts included — what a COEP host wants. `'never'`: none. |
@@ -1429,6 +1607,20 @@ formatMCPUIString('Export CSV ({count} rows)', { count: 42 }) // 'Export CSV (42
 | `sizeBytes` | `{size} B` | `ArtifactRenderer` — file size below 1 KB (template) |
 | `sizeKilobytes` | `{size} KB` | `ArtifactRenderer` — file size in kilobytes (template) |
 | `sizeMegabytes` | `{size} MB` | `ArtifactRenderer` — file size in megabytes (template) |
+| `zoomIn` | `Zoom in` | `LightboxOverlay`, `ChartJSRenderer` — zoom-in button `title`/`aria-label` (v6.22.0) |
+| `zoomOut` | `Zoom out` | `LightboxOverlay`, `ChartJSRenderer` — zoom-out button `title`/`aria-label` (v6.22.0) |
+| `zoomReset` | `Reset zoom` | `LightboxOverlay`, `ChartJSRenderer` — reset button, shown while zoomed (v6.22.0) |
+| `zoomLevel` | `Zoom {percent}%` | `LightboxOverlay` — zoom-level readout (template, v6.22.0) |
+| `missingValue` | `Missing value` | Tables, chart data view, degraded tables — screen-reader text of a missing cell; tooltip value of a missing bar (v6.24.0) |
+| `missingValueLegend` | `“{marker}” marks a missing value.` | Legend under a table or data view with a missing cell (template, `{marker}` = `-`, v6.24.0) |
+| `chartMissingGaps` | `Breaks in a line mark missing values.` | `ChartJSRenderer` — note under a line or radar chart with a missing value (v6.24.0) |
+| `chartMissingBars` | `Dashed outlines mark missing values.` | `ChartJSRenderer` — note under a bar chart with a missing value (v6.24.0) |
+| `chartMissingPoints` | `Missing values are not plotted.` | `ChartJSRenderer` — note under a scatter, bubble or stacked bar chart with a missing value (v6.24.0) |
+| `chartSeriesNoData` | `No data for {series}.` | `ChartJSRenderer` — note naming the series with no value at all (template, `{series}` joined as a list in `locale`, v6.24.0) |
+| `chartLegendNoData` | `{series} (no data)` | `ChartJSRenderer` — legend entry of a series with no value at all (template, v6.24.0) |
+| `chartValueWithUnit` | `{value} {unit}` | `ChartJSRenderer` — tooltip value followed by the chart `unit` (template, v6.24.0) |
+| `chartLabelWithUnit` | `{label} ({unit})` | Chart data view and degraded chart tables — column header followed by the chart `unit` (template, v6.24.0) |
+| `chartMissingUnsupported` | `This chart type cannot show missing values.` | `ChartJSRenderer` — shown instead of a pie, doughnut or polar-area chart that received a missing value (v6.24.0) |
 
 ### `locale` — number, date and sort formatting (default change in v6.20.0)
 
@@ -1766,6 +1958,20 @@ const fr: MCPUIStrings = {
   sizeBytes: '{size} o',
   sizeKilobytes: '{size} Ko',
   sizeMegabytes: '{size} Mo',
+  zoomIn: 'Zoom avant',
+  zoomOut: 'Zoom arrière',
+  zoomReset: 'Réinitialiser le zoom',
+  zoomLevel: 'Zoom {percent} %',
+  missingValue: 'Valeur manquante',
+  missingValueLegend: '« {marker} » signale une valeur manquante.',
+  chartMissingGaps: 'Une interruption de la courbe signale une valeur manquante.',
+  chartMissingBars: 'Un contour en pointillés signale une valeur manquante.',
+  chartMissingPoints: 'Les valeurs manquantes ne sont pas tracées.',
+  chartSeriesNoData: 'Aucune donnée pour {series}.',
+  chartLegendNoData: '{series} (aucune donnée)',
+  chartValueWithUnit: '{value} {unit}',
+  chartLabelWithUnit: '{label} ({unit})',
+  chartMissingUnsupported: 'Ce type de graphique ne peut pas afficher de valeurs manquantes.',
 }
 
 <MCPUIStringsProvider strings={fr}><App /></MCPUIStringsProvider>
@@ -1800,8 +2006,8 @@ exported default table:
 | `adapters/connector.ts` (`/adapters`) | `connectorResultToUILayout` | `options.messages?: Partial<ConnectorAdapterMessages>` | `DEFAULT_CONNECTOR_MESSAGES` | `degradedNotice`, `degradedVersionSuffix`, `versionWarning` |
 | `adapters/macro-run.ts` (`/adapters`) | `macroRunToScratchpadState`, `macroInterrogationToChatPromptConfig` | `options.messages?: Partial<MacroRunAdapterMessages>` | `DEFAULT_MACRO_RUN_MESSAGES` | `agentSectionTitle`, `progressSectionTitle`, `resultSectionTitle`, `runAborted`, `runFailed`, `confirmDefault` |
 | `services/validation.ts` (root, `/validation`) | `validateFieldValue`, `validateFormData` | `messages?: Partial<FormValidationMessages>` | `DEFAULT_VALIDATION_MESSAGES` | `required`, `mustBeChecked`, `minLength`, `maxLength`, `invalidPattern`, `invalidEmail`, `invalidNumber`, `minValue`, `maxValue`, `minDate`, `maxDate`, `invalidOption`, `invalidFormat` |
-| `utils/degraded-projections.ts` (root) | `graphToDegradedTable`, `mapToDegradedTable`, `chartToDegradedTable` | `labels?: Partial<DegradedProjectionLabels>` | `DEGRADED_PROJECTION_LABELS` | `source`, `target`, `label`, `node`, `type`, `lat`, `lng`, `info`, `marker`, `feature`, `series` |
-| `components/chart-data-table.ts` (root) | `chartToDataTable` | `labels?: Partial<ChartDataTableLabels>` | `CHART_DATA_TABLE_LABELS` | `series`, `point`, `label`, `seriesName`, `x`, `y`, `r` |
+| `utils/degraded-projections.ts` (root) | `graphToDegradedTable`, `mapToDegradedTable`, `chartToDegradedTable` | `labels?: Partial<DegradedProjectionLabels>` | `DEGRADED_PROJECTION_LABELS` | `source`, `target`, `label`, `node`, `type`, `lat`, `lng`, `info`, `marker`, `feature`, `series`, `withUnit` (optional, v6.24.0: `{label} ({unit})`, chart headers when the chart has a unit) |
+| `components/chart-data-table.ts` (root) | `chartToDataTable` | `labels?: Partial<ChartDataTableLabels>` | `CHART_DATA_TABLE_LABELS` | `series`, `point`, `label`, `seriesName`, `x`, `y`, `r`, `withUnit` (optional, v6.24.0: `{label} ({unit})`, value headers when the chart has a unit) |
 | `hooks/useStreamingUI.ts` (root, `/hooks`) | `useStreamingUI` | `options.messages?: Partial<StreamingUIMessages>` | `DEFAULT_STREAMING_UI_MESSAGES` | `initializing`, `connecting`, `loadingComponent`, `dashboardLoaded`, `errorProgress`, `connectionFailed`, `requestFailed`, `emptyResponse`, `serverSide`, `unknownError` |
 
 Every option is a trailing OPTIONAL parameter, so existing calls keep
@@ -1966,6 +2172,7 @@ import type {
   IframePolicy, ValidationOptions,
   CitationCtx, CitationEntry, DuplicateMountInfo, DuplicateMountReporter,
   MCPUIStrings, MCPUIConfig, // v6.21.0
+  MCPUIConfigInput, // v6.22.1 — the authored, all-optional view
   TelemetryEvent, TelemetrySink, TelemetryOptions, TelemetryDispatcher,
   DataValidation, HallucinatedNumber, DataValidationOptions,
   VerifiedTextContent, DataPreviewContent, MapSectionContent,