@toclocoinc/lattice-grid 1.71.1 → 1.71.3

package/CHANGELOG.md

@@ -9,6 +9,14 @@ and what it means for a grid already in production.
 
 ## [Unreleased]
 
+## [1.71.3] - 2026-09-25
+
+### Added
+
+- A `scheme` array coloured slices and series by position, so a category or series a filter removed shifted every colour after it — a sites-by-status donut and a severity-stacked bar could not hold "Operational" green and "Offline" red once one status disappeared for a quarter (BACKLOG-0001453). `scheme` now also accepts a `{ name: colour }` map: it keys on the category for `pie`/`donut`/`sunburst`, on the series value for any cartesian type with `series`, and on the `x` category for a single-series `bar`/`horizontalBar`. A name absent from the map falls back to the ordered scheme by its position among the other unmapped names only, so an explicit assignment is never disturbed by a name the map does not mention. A map and an array `palette` do not combine — the map wins, once, with a warning (`chart:scheme:array-and-map`).
+  - `legend: { values: true }` appends each entry's own total after its name and a thin space — a category's for `pie`/`donut`, a series' for a series legend — formatted by the measure column.
+  - A `donut` now takes `centre: { value: 'total' | number | string, label? }`, drawn in the hole: `'total'` sums the slices actually drawn, a number is formatted the same way, a string is written through unchanged; both the value and an optional label are sized to fit the hole and never drawn past its edge.
+
 ## [1.71.1] - 2026-09-24
 
 ### Added

package/README.md

@@ -5,7 +5,7 @@ dependencies, no build step required. Optional adapters for React, Vue, Svelte
 and Web Components ship alongside it, and Angular has compiled components of its
 own at `@toclocoinc/lattice-grid/angular` — inside this package, not beside it.
 
-Version 1.71.1 · [latticegrid.dev](https://www.latticegrid.dev) · TOCLOCO Inc
+Version 1.71.3 · [latticegrid.dev](https://www.latticegrid.dev) · TOCLOCO Inc
 
 ---
 

package/angular/package.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.71.1",
+  "version": "1.71.3",
   "type": "module",
   "sideEffects": false,
   "module": "./fesm2022/toclocoinc-lattice-grid-angular.mjs",

package/docs/API.html

@@ -382,7 +382,7 @@
 <div class="shell">
   <aside class="rail">
     <p class="rail__brand">Lattice Grid</p>
-    <p class="rail__sub">API reference · v1.71.1</p>
+    <p class="rail__sub">API reference · v1.71.3</p>
     <nav>
       <div class="rail__group">
         <span class="rail__label">Start</span>
@@ -553,7 +553,7 @@
     </header>
 
     <p class="chips">
-      <span class="chip">Version 1.71.1</span>
+      <span class="chip">Version 1.71.3</span>
       <span class="chip">Zero dependencies</span>
       <span class="chip"><a href="api-detail.html">Developer guide &rarr;</a></span>
     </p>
@@ -2180,7 +2180,7 @@ grid.destroy();
       <table>
         <thead><tr><th>Member</th><th>Returns</th><th>Description</th></tr></thead>
         <tbody>
-          <tr><td class="sig">getVersion()</td><td class="type">string</td><td class="desc">The version this grid came from, e.g. <code>'1.71.1'</code>. Also on the module as <code>getVersion()</code>, for when you have no grid to hand.</td></tr>
+          <tr><td class="sig">getVersion()</td><td class="type">string</td><td class="desc">The version this grid came from, e.g. <code>'1.71.3'</code>. Also on the module as <code>getVersion()</code>, for when you have no grid to hand.</td></tr>
           <tr><td class="sig">get(key)</td><td class="type">unknown</td><td class="desc">Read any configuration key.</td></tr>
           <tr><td class="sig">set(key, value)</td><td class="type">void</td><td class="desc">Write one key. Every key is live; nothing needs a rebuild.</td></tr>
           <tr><td class="sig">setAll(values)</td><td class="type">void</td><td class="desc">Write several in one pass. Emits one <code>config:changed</code> for the batch, not one per key.</td></tr>
@@ -5816,8 +5816,9 @@ const chart = createChart({
           <tr><td class="name">series</td><td class="type">string</td><td class="desc">Splits the measure into one series per distinct value.</td></tr>
           <tr><td class="name">measures</td><td class="type">object[]</td><td class="desc"><code>{col, fn, type, axis}</code>: several measures at once, each reduced by an aggregation. <code>fn</code> is one of <code>sum</code>, <code>avg</code> (alias <code>mean</code>), <code>min</code>, <code>max</code>, <code>count</code>, <code>countValues</code>, <code>first</code>, <code>last</code>; it defaults to <code>sum</code>. An <code>fn</code> that is none of these is a mistake, not a silent <code>sum</code>: it warns once, naming the value and the supported set, and falls back to <code>sum</code> so the chart still draws.</td></tr>
           <tr><td class="name">title</td><td class="type">string</td><td class="desc">Drawn above the plot.</td></tr>
-          <tr><td class="name">scheme</td><td class="type">string | string[]</td><td class="desc">A named scheme or your own colours. <code>schemeNames()</code> lists the built-in ones, including a colour-blind-safe palette.</td></tr>
-          <tr><td class="name">legend</td><td class="type">boolean | object</td><td class="desc"><code>position</code>, and <code>isolate</code> so a click shows only that series, which is what a reader with eight series wants, and what plain toggling makes them do in seven clicks.</td></tr>
+          <tr><td class="name">scheme</td><td class="type">string | string[] | object</td><td class="desc">A named scheme, your own ordered colours, or a <code>{ name: colour }</code> map (BACKLOG-0001453). <code>schemeNames()</code> lists the built-in ones, including a colour-blind-safe palette. The map is what survives a filter: a pie or donut keys it on the category, a chart with <code>series</code> keys it on the series value, and a single-series bar or column keys it on the <code>x</code> category instead. A name the map does not mention falls back to the ordered scheme by its position among the other unmapped names, so <code>{ Operational: 'green', Offline: 'red' }</code> keeps "Operational" exactly as green whichever categories a filter leaves. A map and a <code>palette</code> array do not combine — the map wins, and the array is ignored once, with a warning.</td></tr>
+          <tr><td class="name">legend</td><td class="type">boolean | object</td><td class="desc"><code>position</code>, <code>isolate</code> so a click shows only that series (what plain toggling makes a reader with eight series do in seven clicks), and <code>values: true</code>, which appends each entry's own total after its name and a thin space — a category's for pie and donut, a series' for a series legend — formatted by the measure column (BACKLOG-0001453).</td></tr>
+          <tr><td class="name">centre</td><td class="type">object</td><td class="desc">A donut's own figure, drawn in its hole (BACKLOG-0001453); every other type ignores it, having no hole. <code>{ value: 'total' | number | string, label? }</code> — <code>'total'</code> sums the slices actually drawn, so hiding a category from the legend moves the figure with them; a number is formatted the same way; a string is written through unchanged. <code>label</code> is a second line beneath it. Both are sized to fit the hole and never drawn past its edge.</td></tr>
           <tr><td class="name">labels</td><td class="type">boolean | object</td><td class="desc">Values beside each mark. <code>position</code>, <code>format</code>, <code>minGap</code>. A label that would overlap one already placed is dropped rather than drawn over it. <code>horizontalBar</code> draws them exactly as <code>bar</code> does: the figure sits past the end of the bar and, where that would spill past the plot's right edge, inside the bar instead (BACKLOG-0001451).</td></tr>
           <tr><td class="name">axis</td><td class="type">object</td><td class="desc">Titles, tick density and formatting per axis.</td></tr>
           <tr><td class="name">reference</td><td class="type">object[]</td><td class="desc">Horizontal lines: <code>{value, label}</code>.</td></tr>
@@ -5938,6 +5939,38 @@ grid.destroy();
       exactly as before &mdash; a rule and a series both mean &ldquo;colour by something&rdquo;,
       and only one is read at a time.
     </p>
+    <p class="section-note">
+      <strong>A <code>scheme</code> can colour by name instead of by position</strong>
+      (BACKLOG-0001453). <code>scheme: { Operational: 'green', Degraded: 'amber', Offline: 'red' }</code>
+      keys on the category for a <code>pie</code>, <code>donut</code> or <code>sunburst</code>; on
+      the series value for any cartesian type with a <code>series</code> column; and on the
+      <code>x</code> category for a single-series <code>bar</code> or <code>horizontalBar</code>
+      &mdash; the same "no <code>series</code>" case the rule colour above reads, and a rule still
+      outranks the map where both apply. The point of the map is what an ordered array cannot do: a
+      category a filter removes never shifts the colour of the ones that stay, because each name's
+      colour comes from the map rather than from where it happens to sort. A name the map does not
+      mention falls back to the ordered scheme by its position among the <em>other unmapped</em>
+      names only. A map and an array <code>palette</code> are two ways of choosing the same thing
+      and do not combine &mdash; given both, the map wins and the array is ignored, once, with a
+      warning (<code>chart:scheme:array-and-map</code>).
+    </p>
+    <p class="section-note">
+      <strong><code>legend: { values: true }</code> writes the number beside the name</strong>
+      (BACKLOG-0001453). Each entry gets its own total appended after a thin space &mdash; the
+      category's for a <code>pie</code> or <code>donut</code>, the series' for a series legend
+      &mdash; formatted by the measure column exactly as a cell in that column would be, so a
+      legend reading "Operational&nbsp;42" and a filtered grid never disagree about what 42 means.
+    </p>
+    <p class="section-note">
+      <strong>A donut can carry a figure in its own hole</strong> (BACKLOG-0001453):
+      <code>centre: { value: 'total', label: 'sites' }</code>. <code>'total'</code> sums the slices
+      actually drawn, so hiding a category from the legend moves the figure with the slices rather
+      than leaving it stale; a number is a caller's own figure, formatted the same way; a string is
+      written through unchanged, for a centre naming something a sum cannot. <code>label</code> is a
+      second line beneath the value. Both are sized to the hole a donut cuts &mdash; never a pie's,
+      which has none &mdash; and are shrunk together, proportionally, and truncated rather than
+      drawn past its edge.
+    </p>
 
     <h3>The chart</h3>
     <div class="table-wrap">
@@ -14740,8 +14773,9 @@ return `next ${p.mean.toFixed(1)}; r2 ${f.r2.toFixed(1)}; band ${p.upper - p.low
           <tr><td class="name">start</td><td class="type">string</td><td class="desc">The start-date column, for a gantt chart. <small>(optional)</small></td></tr>
           <tr><td class="name">end</td><td class="type">string</td><td class="desc">The end-date column, for a gantt chart. <small>(optional)</small></td></tr>
           <tr><td class="name">title</td><td class="type">string</td><td class="desc">A heading above the plot, drawn in the figure's caption alongside any `subtitle`. <small>(optional)</small></td></tr>
-          <tr><td class="name">scheme</td><td class="type"><a href="#type-ChartSchemeName">ChartSchemeName</a> | string | string[]</td><td class="desc">A named scheme, or an array of colours. The built-in names are {@link ChartSchemeName} (`'default'`, `'bright'`, `'earth'`, `'mono'`); a name registered with `registerScheme` is a plain string alongside them. <small>(optional)</small></td></tr>
-          <tr><td class="name">legend</td><td class="type">boolean | { position?: 'top' | 'bottom' | 'left' | 'right'; isolate?: boolean }</td><td class="desc">Show the series legend. The object form places it, and `isolate` lets a click on a legend entry show that series alone. <small>(optional)</small></td></tr>
+          <tr><td class="name">scheme</td><td class="type"><a href="#type-ChartSchemeName">ChartSchemeName</a> | string | string[] | Record&lt;string, string&gt;</td><td class="desc">A named scheme, an array of colours, or a `{ [name]: colour }` map (BACKLOG-0001453). The built-in names are {@link ChartSchemeName} (`'default'`, `'bright'`, `'earth'`, `'mono'`); a name registered with `registerScheme` is a plain string alongside them. The map is the form that survives a filter: a pie or donut keys it on the category (`x`) value, a chart with a `series` column keys it on the series value, and a single-series bar or column — no `series` — keys it on the `x` category instead. A name absent from the map falls back to the ordered scheme by its position among the *other unmapped* names, so `{ Operational: 'green' }` keeps every other category exactly as it was whichever ones a filter removes — an ordered array reassigns every colour after the gap. A map and an array `palette` do not combine; given both, the map wins and the array is ignored, once, with a warning. <small>(optional)</small></td></tr>
+          <tr><td class="name">legend</td><td class="type">boolean | { position?: 'top' | 'bottom' | 'left' | 'right'; isolate?: boolean; values?: boolean; }</td><td class="desc">Show the series legend. The object form places it, and `isolate` lets a click on a legend entry show that series alone. `values: true` appends each entry's own total — a category's for pie and donut, a series' for a series legend — formatted by the measure column, after the name and a thin space (BACKLOG-0001453). <small>(optional)</small></td></tr>
+          <tr><td class="name">centre</td><td class="type">{ value: 'total' | number | string; label?: string }</td><td class="desc">The figure a donut draws in its own hole (BACKLOG-0001453); ignored by every other type, which has no hole to draw into. `value: 'total'` sums the slices actually drawn — a legend click that hides a category moves the figure with them — formatted by the measure column; a number is a caller's own figure, formatted the same way; a string is written through unchanged. `label` is a second line beneath it. Both are sized to fit the hole and are never drawn past its edge. <small>(optional)</small></td></tr>
           <tr><td class="name">labels</td><td class="type">boolean | <a href="#type-ChartLabels">ChartLabels</a></td><td class="desc">Print the value beside each mark. `true` takes the defaults; the object form sets the position, the format and the minimum gap. Only the chart types that support labels honour it. <small>(optional)</small></td></tr>
           <tr><td class="name">axis</td><td class="type">{ x?: string | <a href="#type-ChartAxis">ChartAxis</a>; y?: string | <a href="#type-ChartAxis">ChartAxis</a>; y2?: string | <a href="#type-ChartAxis">ChartAxis</a>; right?: string | <a href="#type-ChartAxis">ChartAxis</a>; }</td><td class="desc">Per-axis configuration. Each side is a title string or an object of `{ title, min, max, ticks, format, grid, labels }`. `y2` (or `right`) configures the second measure axis of a dual-axis or combo chart (BACKLOG-0000743); a dual-axis chart labels both axes by default so it cannot silently mislead. <small>(optional)</small></td></tr>
           <tr><td class="name">brush</td><td class="type">boolean | 'filter' | 'zoom' | 'select' | { mode: 'filter' | 'zoom' | 'select'; axis?: 'x' | 'y' | 'y2' }</td><td class="desc">Dragging across the plot. `true` or `'filter'` writes a range condition into the grid; `'zoom'` changes only this chart's own domain; `'select'` selects the rows under the drag. The object form names which axis the drag acts on — `axis: 'y'` or `'y2'` brushes a value axis, which on a dual-axis chart must say which one it means (BACKLOG-0000743). <small>(optional)</small></td></tr>
@@ -20337,7 +20371,7 @@ return `next ${p.mean.toFixed(1)}; r2 ${f.r2.toFixed(1)}; band ${p.upper - p.low
 <!-- END GENERATED TYPE REFERENCE -->
 
     <footer>
-      Lattice Grid 1.71.1 · Copyright © 2026 TOCLOCO Inc. All rights reserved.
+      Lattice Grid 1.71.3 · Copyright © 2026 TOCLOCO Inc. All rights reserved.
       This document describes the behaviour of the shipped library. Where this guide and the code
       disagree, the code wins: please <a href="https://www.latticegrid.dev">tell us</a>.
     </footer>

package/docs/api/adapters.html

@@ -13,7 +13,7 @@
   Self-contained: no stylesheet, script or font is fetched, so this opens from disk, from
   a file share or from behind a firewall with nothing else present.
 -->
-<title>Adapters API Reference — Lattice Grid 1.71.1</title>
+<title>Adapters API Reference — Lattice Grid 1.71.3</title>
 <style>
   /* ---------------------------------------------------------------
      Palette lifted from the grid's own theme, so the reference reads as an

package/docs/api/ai.html

@@ -13,7 +13,7 @@
   Self-contained: no stylesheet, script or font is fetched, so this opens from disk, from
   a file share or from behind a firewall with nothing else present.
 -->
-<title>AI API Reference — Lattice Grid 1.71.1</title>
+<title>AI API Reference — Lattice Grid 1.71.3</title>
 <style>
   /* ---------------------------------------------------------------
      Palette lifted from the grid's own theme, so the reference reads as an

package/docs/api/alarms.html

@@ -13,7 +13,7 @@
   Self-contained: no stylesheet, script or font is fetched, so this opens from disk, from
   a file share or from behind a firewall with nothing else present.
 -->
-<title>Alarms API Reference — Lattice Grid 1.71.1</title>
+<title>Alarms API Reference — Lattice Grid 1.71.3</title>
 <style>
   /* ---------------------------------------------------------------
      Palette lifted from the grid's own theme, so the reference reads as an

package/docs/api/charts.html

@@ -13,7 +13,7 @@
   Self-contained: no stylesheet, script or font is fetched, so this opens from disk, from
   a file share or from behind a firewall with nothing else present.
 -->
-<title>Charts API Reference — Lattice Grid 1.71.1</title>
+<title>Charts API Reference — Lattice Grid 1.71.3</title>
 <style>
   /* ---------------------------------------------------------------
      Palette lifted from the grid's own theme, so the reference reads as an
@@ -478,8 +478,9 @@ const chart = createChart({
           <tr><td class="name">series</td><td class="type">string</td><td class="desc">Splits the measure into one series per distinct value.</td></tr>
           <tr><td class="name">measures</td><td class="type">object[]</td><td class="desc"><code>{col, fn, type, axis}</code>: several measures at once, each reduced by an aggregation. <code>fn</code> is one of <code>sum</code>, <code>avg</code> (alias <code>mean</code>), <code>min</code>, <code>max</code>, <code>count</code>, <code>countValues</code>, <code>first</code>, <code>last</code>; it defaults to <code>sum</code>. An <code>fn</code> that is none of these is a mistake, not a silent <code>sum</code>: it warns once, naming the value and the supported set, and falls back to <code>sum</code> so the chart still draws.</td></tr>
           <tr><td class="name">title</td><td class="type">string</td><td class="desc">Drawn above the plot.</td></tr>
-          <tr><td class="name">scheme</td><td class="type">string | string[]</td><td class="desc">A named scheme or your own colours. <code>schemeNames()</code> lists the built-in ones, including a colour-blind-safe palette.</td></tr>
-          <tr><td class="name">legend</td><td class="type">boolean | object</td><td class="desc"><code>position</code>, and <code>isolate</code> so a click shows only that series, which is what a reader with eight series wants, and what plain toggling makes them do in seven clicks.</td></tr>
+          <tr><td class="name">scheme</td><td class="type">string | string[] | object</td><td class="desc">A named scheme, your own ordered colours, or a <code>{ name: colour }</code> map (BACKLOG-0001453). <code>schemeNames()</code> lists the built-in ones, including a colour-blind-safe palette. The map is what survives a filter: a pie or donut keys it on the category, a chart with <code>series</code> keys it on the series value, and a single-series bar or column keys it on the <code>x</code> category instead. A name the map does not mention falls back to the ordered scheme by its position among the other unmapped names, so <code>{ Operational: 'green', Offline: 'red' }</code> keeps "Operational" exactly as green whichever categories a filter leaves. A map and a <code>palette</code> array do not combine — the map wins, and the array is ignored once, with a warning.</td></tr>
+          <tr><td class="name">legend</td><td class="type">boolean | object</td><td class="desc"><code>position</code>, <code>isolate</code> so a click shows only that series (what plain toggling makes a reader with eight series do in seven clicks), and <code>values: true</code>, which appends each entry's own total after its name and a thin space — a category's for pie and donut, a series' for a series legend — formatted by the measure column (BACKLOG-0001453).</td></tr>
+          <tr><td class="name">centre</td><td class="type">object</td><td class="desc">A donut's own figure, drawn in its hole (BACKLOG-0001453); every other type ignores it, having no hole. <code>{ value: 'total' | number | string, label? }</code> — <code>'total'</code> sums the slices actually drawn, so hiding a category from the legend moves the figure with them; a number is formatted the same way; a string is written through unchanged. <code>label</code> is a second line beneath it. Both are sized to fit the hole and never drawn past its edge.</td></tr>
           <tr><td class="name">labels</td><td class="type">boolean | object</td><td class="desc">Values beside each mark. <code>position</code>, <code>format</code>, <code>minGap</code>. A label that would overlap one already placed is dropped rather than drawn over it. <code>horizontalBar</code> draws them exactly as <code>bar</code> does: the figure sits past the end of the bar and, where that would spill past the plot's right edge, inside the bar instead (BACKLOG-0001451).</td></tr>
           <tr><td class="name">axis</td><td class="type">object</td><td class="desc">Titles, tick density and formatting per axis.</td></tr>
           <tr><td class="name">reference</td><td class="type">object[]</td><td class="desc">Horizontal lines: <code>{value, label}</code>.</td></tr>
@@ -600,6 +601,38 @@ grid.destroy();
       exactly as before &mdash; a rule and a series both mean &ldquo;colour by something&rdquo;,
       and only one is read at a time.
     </p>
+    <p class="section-note">
+      <strong>A <code>scheme</code> can colour by name instead of by position</strong>
+      (BACKLOG-0001453). <code>scheme: { Operational: 'green', Degraded: 'amber', Offline: 'red' }</code>
+      keys on the category for a <code>pie</code>, <code>donut</code> or <code>sunburst</code>; on
+      the series value for any cartesian type with a <code>series</code> column; and on the
+      <code>x</code> category for a single-series <code>bar</code> or <code>horizontalBar</code>
+      &mdash; the same "no <code>series</code>" case the rule colour above reads, and a rule still
+      outranks the map where both apply. The point of the map is what an ordered array cannot do: a
+      category a filter removes never shifts the colour of the ones that stay, because each name's
+      colour comes from the map rather than from where it happens to sort. A name the map does not
+      mention falls back to the ordered scheme by its position among the <em>other unmapped</em>
+      names only. A map and an array <code>palette</code> are two ways of choosing the same thing
+      and do not combine &mdash; given both, the map wins and the array is ignored, once, with a
+      warning (<code>chart:scheme:array-and-map</code>).
+    </p>
+    <p class="section-note">
+      <strong><code>legend: { values: true }</code> writes the number beside the name</strong>
+      (BACKLOG-0001453). Each entry gets its own total appended after a thin space &mdash; the
+      category's for a <code>pie</code> or <code>donut</code>, the series' for a series legend
+      &mdash; formatted by the measure column exactly as a cell in that column would be, so a
+      legend reading "Operational&nbsp;42" and a filtered grid never disagree about what 42 means.
+    </p>
+    <p class="section-note">
+      <strong>A donut can carry a figure in its own hole</strong> (BACKLOG-0001453):
+      <code>centre: { value: 'total', label: 'sites' }</code>. <code>'total'</code> sums the slices
+      actually drawn, so hiding a category from the legend moves the figure with the slices rather
+      than leaving it stale; a number is a caller's own figure, formatted the same way; a string is
+      written through unchanged, for a centre naming something a sum cannot. <code>label</code> is a
+      second line beneath the value. Both are sized to the hole a donut cuts &mdash; never a pie's,
+      which has none &mdash; and are shrunk together, proportionally, and truncated rather than
+      drawn past its edge.
+    </p>
 
     <h3>The chart</h3>
     <div class="table-wrap">
@@ -1155,8 +1188,9 @@ chart.destroy();
           <tr><td class="name">start</td><td class="type">string</td><td class="desc">The start-date column, for a gantt chart. <small>(optional)</small></td></tr>
           <tr><td class="name">end</td><td class="type">string</td><td class="desc">The end-date column, for a gantt chart. <small>(optional)</small></td></tr>
           <tr><td class="name">title</td><td class="type">string</td><td class="desc">A heading above the plot, drawn in the figure's caption alongside any `subtitle`. <small>(optional)</small></td></tr>
-          <tr><td class="name">scheme</td><td class="type"><a href="types.html#type-ChartSchemeName">ChartSchemeName</a> | string | string[]</td><td class="desc">A named scheme, or an array of colours. The built-in names are {@link ChartSchemeName} (`'default'`, `'bright'`, `'earth'`, `'mono'`); a name registered with `registerScheme` is a plain string alongside them. <small>(optional)</small></td></tr>
-          <tr><td class="name">legend</td><td class="type">boolean | { position?: 'top' | 'bottom' | 'left' | 'right'; isolate?: boolean }</td><td class="desc">Show the series legend. The object form places it, and `isolate` lets a click on a legend entry show that series alone. <small>(optional)</small></td></tr>
+          <tr><td class="name">scheme</td><td class="type"><a href="types.html#type-ChartSchemeName">ChartSchemeName</a> | string | string[] | Record&lt;string, string&gt;</td><td class="desc">A named scheme, an array of colours, or a `{ [name]: colour }` map (BACKLOG-0001453). The built-in names are {@link ChartSchemeName} (`'default'`, `'bright'`, `'earth'`, `'mono'`); a name registered with `registerScheme` is a plain string alongside them. The map is the form that survives a filter: a pie or donut keys it on the category (`x`) value, a chart with a `series` column keys it on the series value, and a single-series bar or column — no `series` — keys it on the `x` category instead. A name absent from the map falls back to the ordered scheme by its position among the *other unmapped* names, so `{ Operational: 'green' }` keeps every other category exactly as it was whichever ones a filter removes — an ordered array reassigns every colour after the gap. A map and an array `palette` do not combine; given both, the map wins and the array is ignored, once, with a warning. <small>(optional)</small></td></tr>
+          <tr><td class="name">legend</td><td class="type">boolean | { position?: 'top' | 'bottom' | 'left' | 'right'; isolate?: boolean; values?: boolean; }</td><td class="desc">Show the series legend. The object form places it, and `isolate` lets a click on a legend entry show that series alone. `values: true` appends each entry's own total — a category's for pie and donut, a series' for a series legend — formatted by the measure column, after the name and a thin space (BACKLOG-0001453). <small>(optional)</small></td></tr>
+          <tr><td class="name">centre</td><td class="type">{ value: 'total' | number | string; label?: string }</td><td class="desc">The figure a donut draws in its own hole (BACKLOG-0001453); ignored by every other type, which has no hole to draw into. `value: 'total'` sums the slices actually drawn — a legend click that hides a category moves the figure with them — formatted by the measure column; a number is a caller's own figure, formatted the same way; a string is written through unchanged. `label` is a second line beneath it. Both are sized to fit the hole and are never drawn past its edge. <small>(optional)</small></td></tr>
           <tr><td class="name">labels</td><td class="type">boolean | <a href="types.html#type-ChartLabels">ChartLabels</a></td><td class="desc">Print the value beside each mark. `true` takes the defaults; the object form sets the position, the format and the minimum gap. Only the chart types that support labels honour it. <small>(optional)</small></td></tr>
           <tr><td class="name">axis</td><td class="type">{ x?: string | <a href="types.html#type-ChartAxis">ChartAxis</a>; y?: string | <a href="types.html#type-ChartAxis">ChartAxis</a>; y2?: string | <a href="types.html#type-ChartAxis">ChartAxis</a>; right?: string | <a href="types.html#type-ChartAxis">ChartAxis</a>; }</td><td class="desc">Per-axis configuration. Each side is a title string or an object of `{ title, min, max, ticks, format, grid, labels }`. `y2` (or `right`) configures the second measure axis of a dual-axis or combo chart (BACKLOG-0000743); a dual-axis chart labels both axes by default so it cannot silently mislead. <small>(optional)</small></td></tr>
           <tr><td class="name">brush</td><td class="type">boolean | 'filter' | 'zoom' | 'select' | { mode: 'filter' | 'zoom' | 'select'; axis?: 'x' | 'y' | 'y2' }</td><td class="desc">Dragging across the plot. `true` or `'filter'` writes a range condition into the grid; `'zoom'` changes only this chart's own domain; `'select'` selects the rows under the drag. The object form names which axis the drag acts on — `axis: 'y'` or `'y2'` brushes a value axis, which on a dual-axis chart must say which one it means (BACKLOG-0000743). <small>(optional)</small></td></tr>

package/docs/api/data-router.html

@@ -13,7 +13,7 @@
   Self-contained: no stylesheet, script or font is fetched, so this opens from disk, from
   a file share or from behind a firewall with nothing else present.
 -->
-<title>Data router API Reference — Lattice Grid 1.71.1</title>
+<title>Data router API Reference — Lattice Grid 1.71.3</title>
 <style>
   /* ---------------------------------------------------------------
      Palette lifted from the grid's own theme, so the reference reads as an

package/docs/api/gantt.html

@@ -13,7 +13,7 @@
   Self-contained: no stylesheet, script or font is fetched, so this opens from disk, from
   a file share or from behind a firewall with nothing else present.
 -->
-<title>Gantt API Reference — Lattice Grid 1.71.1</title>
+<title>Gantt API Reference — Lattice Grid 1.71.3</title>
 <style>
   /* ---------------------------------------------------------------
      Palette lifted from the grid's own theme, so the reference reads as an

package/docs/api/grid.html

@@ -13,7 +13,7 @@
   Self-contained: no stylesheet, script or font is fetched, so this opens from disk, from
   a file share or from behind a firewall with nothing else present.
 -->
-<title>Grid API Reference — Lattice Grid 1.71.1</title>
+<title>Grid API Reference — Lattice Grid 1.71.3</title>
 <style>
   /* ---------------------------------------------------------------
      Palette lifted from the grid's own theme, so the reference reads as an
@@ -1115,7 +1115,7 @@ grid.destroy();
       <table>
         <thead><tr><th>Member</th><th>Returns</th><th>Description</th></tr></thead>
         <tbody>
-          <tr><td class="sig">getVersion()</td><td class="type">string</td><td class="desc">The version this grid came from, e.g. <code>'1.71.1'</code>. Also on the module as <code>getVersion()</code>, for when you have no grid to hand.</td></tr>
+          <tr><td class="sig">getVersion()</td><td class="type">string</td><td class="desc">The version this grid came from, e.g. <code>'1.71.3'</code>. Also on the module as <code>getVersion()</code>, for when you have no grid to hand.</td></tr>
           <tr><td class="sig">get(key)</td><td class="type">unknown</td><td class="desc">Read any configuration key.</td></tr>
           <tr><td class="sig">set(key, value)</td><td class="type">void</td><td class="desc">Write one key. Every key is live; nothing needs a rebuild.</td></tr>
           <tr><td class="sig">setAll(values)</td><td class="type">void</td><td class="desc">Write several in one pass. Emits one <code>config:changed</code> for the batch, not one per key.</td></tr>

package/docs/api/index.html

@@ -13,7 +13,7 @@
   Self-contained: no stylesheet, script or font is fetched, so this opens from disk, from
   a file share or from behind a firewall with nothing else present.
 -->
-<title>API Reference — Lattice Grid 1.71.1</title>
+<title>API Reference — Lattice Grid 1.71.3</title>
 <style>
   /* ---------------------------------------------------------------
      Palette lifted from the grid's own theme, so the reference reads as an
@@ -427,7 +427,7 @@
         <thead><tr><th>Page</th><th>What is on it</th><th>Sections</th><th>Interfaces</th><th>Members</th></tr></thead>
         <tbody>
           <tr><td class="name"><a href="grid.html">The grid</a></td><td class="desc">Constructing a grid, every configuration property, the column definition, each <code>grid.*</code> sub-API, the sources rows come from, and every event the grid raises.</td><td class="type">56</td><td class="type">269</td><td class="type">1891</td></tr>
-          <tr><td class="name"><a href="charts.html">The charts module</a></td><td class="desc"><code>createChart</code>, the chart types and their options, the axes, annotations and tooltips, and the geographic packs.</td><td class="type">1</td><td class="type">5</td><td class="type">108</td></tr>
+          <tr><td class="name"><a href="charts.html">The charts module</a></td><td class="desc"><code>createChart</code>, the chart types and their options, the axes, annotations and tooltips, and the geographic packs.</td><td class="type">1</td><td class="type">5</td><td class="type">109</td></tr>
           <tr><td class="name"><a href="data-router.html">The data router</a></td><td class="desc"><code>createDataRouter</code>: one stream or one dataset split across many viewers, keyed-diff snapshots, join and rollup routes, and backpressure.</td><td class="type">1</td><td class="type">12</td><td class="type">110</td></tr>
           <tr><td class="name"><a href="kpi.html">The KPI (stat-tile) view</a></td><td class="desc"><code>createKPI</code>: stat tiles over a dataset, the aggregations, baselines and delta, threshold bands, sparklines and the tile tree.</td><td class="type">1</td><td class="type">17</td><td class="type">130</td></tr>
           <tr><td class="name"><a href="alarms.html">The alarms module</a></td><td class="desc"><code>createAlarms</code>: levelled alarm events from KPI tiles, grid cells and router routes — raise and clear, with a hold timer that swallows a flapping feed.</td><td class="type">1</td><td class="type">8</td><td class="type">44</td></tr>

package/docs/api/kanban.html

@@ -13,7 +13,7 @@
   Self-contained: no stylesheet, script or font is fetched, so this opens from disk, from
   a file share or from behind a firewall with nothing else present.
 -->
-<title>Kanban API Reference — Lattice Grid 1.71.1</title>
+<title>Kanban API Reference — Lattice Grid 1.71.3</title>
 <style>
   /* ---------------------------------------------------------------
      Palette lifted from the grid's own theme, so the reference reads as an

package/docs/api/kpi.html

@@ -13,7 +13,7 @@
   Self-contained: no stylesheet, script or font is fetched, so this opens from disk, from
   a file share or from behind a firewall with nothing else present.
 -->
-<title>KPI API Reference — Lattice Grid 1.71.1</title>
+<title>KPI API Reference — Lattice Grid 1.71.3</title>
 <style>
   /* ---------------------------------------------------------------
      Palette lifted from the grid's own theme, so the reference reads as an

package/docs/api/layout.html

@@ -13,7 +13,7 @@
   Self-contained: no stylesheet, script or font is fetched, so this opens from disk, from
   a file share or from behind a firewall with nothing else present.
 -->
-<title>Layout API Reference — Lattice Grid 1.71.1</title>
+<title>Layout API Reference — Lattice Grid 1.71.3</title>
 <style>
   /* ---------------------------------------------------------------
      Palette lifted from the grid's own theme, so the reference reads as an

package/docs/api/mock-socket.html

@@ -13,7 +13,7 @@
   Self-contained: no stylesheet, script or font is fetched, so this opens from disk, from
   a file share or from behind a firewall with nothing else present.
 -->
-<title>Mock socket API Reference — Lattice Grid 1.71.1</title>
+<title>Mock socket API Reference — Lattice Grid 1.71.3</title>
 <style>
   /* ---------------------------------------------------------------
      Palette lifted from the grid's own theme, so the reference reads as an

package/docs/api/tabs.html

@@ -13,7 +13,7 @@
   Self-contained: no stylesheet, script or font is fetched, so this opens from disk, from
   a file share or from behind a firewall with nothing else present.
 -->
-<title>Tabs API Reference — Lattice Grid 1.71.1</title>
+<title>Tabs API Reference — Lattice Grid 1.71.3</title>
 <style>
   /* ---------------------------------------------------------------
      Palette lifted from the grid's own theme, so the reference reads as an

package/docs/api/types.html

@@ -13,7 +13,7 @@
   Self-contained: no stylesheet, script or font is fetched, so this opens from disk, from
   a file share or from behind a firewall with nothing else present.
 -->
-<title>Types API Reference — Lattice Grid 1.71.1</title>
+<title>Types API Reference — Lattice Grid 1.71.3</title>
 <style>
   /* ---------------------------------------------------------------
      Palette lifted from the grid's own theme, so the reference reads as an

package/docs/api-detail.html

@@ -437,7 +437,7 @@
 <div class="shell">
   <aside class="rail">
     <p class="rail__brand">Lattice Grid</p>
-    <p class="rail__sub">Developer guide · v1.71.1</p>
+    <p class="rail__sub">Developer guide · v1.71.3</p>
     <nav>
       <div class="rail__group">
         <span class="rail__label">Start here</span>
@@ -554,7 +554,7 @@
         <a href="API.html">reference tables</a> are the shorter version for when you already know.
       </p>
       <p class="chips">
-        <span class="chip">Version 1.71.1</span>
+        <span class="chip">Version 1.71.3</span>
           <span class="chip">Zero dependencies</span>
         <span class="chip">No build step</span>
       </p>
@@ -1493,7 +1493,7 @@ off();                                       <span class="cmt">// every subscrip
     </p>
     <div class="example">
       <p class="example__label">Which version am I running?</p>
-      <pre><code>grid.getVersion();          <span class="cmt">// '1.71.1'</span>
+      <pre><code>grid.getVersion();          <span class="cmt">// '1.71.3'</span>
 LatticeGrid.getVersion();   <span class="cmt">// the same, when you have no grid to hand</span></code></pre>
     </div>
     <p class="lead-in">
@@ -10175,7 +10175,7 @@ grid.licence.state();   <span class="cmt">// 'licensed' | 'localhost' | 'trial'<
 
     <footer>
       <p>
-        Lattice Grid 1.71.1 · Copyright © 2026 TOCLOCO Inc. All rights reserved.
+        Lattice Grid 1.71.3 · Copyright © 2026 TOCLOCO Inc. All rights reserved.
         Written against the shipped source. Where this guide and the code disagree, the code wins,
         please <a href="https://www.latticegrid.dev">tell us</a>.
       </p>

package/docs/warnings.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.71.1",
+  "version": "1.71.3",
   "generated": "tools/build.js from docs/warnings/catalogue.json",
   "about": "Every developer-facing diagnostic Lattice Grid prints to the console, by the key it de-duplicates on. The key is the stable identifier: it is the `id` of every reported entry `grid.diagnostics.warnings()` hands back, what the devtools panel lists, and what to quote in a support conversation. A `*` in an id stands for a value filled in at runtime (a column id, a chart id, an event name), so `icon:*` is one entry covering every column the icon renderer refuses.",
   "fields": {
@@ -14,7 +14,7 @@
     "snippet": "the smallest configuration that fixes it, where configuration is the answer",
     "docs": "the section of the API reference that covers the feature"
   },
-  "count": 474,
+  "count": 475,
   "warnings": [
     {
       "id": "ai:actorbar:no-el",
@@ -4975,6 +4975,17 @@
       "fix": "Pass the router instance (`createRouter()`'s return, or the one an adapter exposes) and, optionally, the partition kind to publish under.",
       "snippet": "alarms.publish(router, 'alarms');\nrouter.attach(alarmGrid, 'alarms');",
       "docs": "api/alarms.html#ref-alarms-reference"
+    },
+    {
+      "id": "chart:scheme:array-and-map",
+      "module": "charts",
+      "severity": "warn",
+      "since": "1.71.2",
+      "message": "chart \"scheme\" was given as a name map together with a \"palette\" array; the two do not combine. Colours came from the map and the array was ignored. Pass one or the other.",
+      "meaning": "A `scheme` name map and an array `palette` are two different ways of choosing a chart's colours, and only one can be read. Given both, the map is treated as the caller's intent and the array is dropped, because a map names an explicit colour per category or series while an array only orders them — the more specific instruction wins.",
+      "fix": "Pass either a `scheme` name map (`{ [name]: colour }`) or a `palette` array, not both.",
+      "snippet": "createChart({ grid, container, type: 'donut', x: 'status', y: 'count', scheme: { Operational: 'green', Offline: 'red' } });",
+      "docs": "api/charts.html#chartsmodule"
     }
   ]
 }

package/lattice-grid.d.ts

@@ -1,5 +1,5 @@
 /*!
- * Lattice Grid 1.71.1, type declarations
+ * Lattice Grid 1.71.3, type declarations
  * Copyright (c) 2026 TOCLOCO Inc. All rights reserved.
  * https://latticegrid.dev
  */
@@ -12100,16 +12100,40 @@ export interface ChartSpec {
   /** A heading above the plot, drawn in the figure's caption alongside any `subtitle`. */
   title?: string;
   /**
-   * A named scheme, or an array of colours. The built-in names are
-   * {@link ChartSchemeName} (`'default'`, `'bright'`, `'earth'`, `'mono'`);
-   * a name registered with `registerScheme` is a plain string alongside them.
+   * A named scheme, an array of colours, or a `{ [name]: colour }` map. The built-in names are {@link ChartSchemeName}
+   * (`'default'`, `'bright'`, `'earth'`, `'mono'`); a name registered with
+   * `registerScheme` is a plain string alongside them.
+   *
+   * The map is the form that survives a filter: a pie or donut keys it on the
+   * category (`x`) value, a chart with a `series` column keys it on the
+   * series value, and a single-series bar or column — no `series` — keys it
+   * on the `x` category instead. A name absent from the map falls back to the
+   * ordered scheme by its position among the *other unmapped* names, so
+   * `{ Operational: 'green' }` keeps every other category exactly as it was
+   * whichever ones a filter removes — an ordered array reassigns every colour
+   * after the gap. A map and an array `palette` do not combine; given both,
+   * the map wins and the array is ignored, once, with a warning.
    */
-  scheme?: ChartSchemeName | string | string[];
+  scheme?: ChartSchemeName | string | string[] | Record<string, string>;
   /**
    * Show the series legend. The object form places it, and `isolate` lets a click on a
-   * legend entry show that series alone.
+   * legend entry show that series alone. `values: true` appends each entry's own total —
+   * a category's for pie and donut, a series' for a series legend — formatted by the
+   * measure column, after the name and a thin space.
+   */
+  legend?: boolean | {
+    position?: 'top' | 'bottom' | 'left' | 'right'; isolate?: boolean; values?: boolean;
+  };
+  /**
+   * The figure a donut draws in its own hole; ignored by
+   * every other type, which has no hole to draw into. `value: 'total'` sums
+   * the slices actually drawn — a legend click that hides a category moves
+   * the figure with them — formatted by the measure column; a number is a
+   * caller's own figure, formatted the same way; a string is written through
+   * unchanged. `label` is a second line beneath it. Both are sized to fit the
+   * hole and are never drawn past its edge.
    */
-  legend?: boolean | { position?: 'top' | 'bottom' | 'left' | 'right'; isolate?: boolean };
+  centre?: { value: 'total' | number | string; label?: string };
   /**
    * Print the value beside each mark. `true` takes the defaults; the object form sets the
    * position, the format and the minimum gap. Only the chart types that support labels