@object-ui/core 17.6.0 → 18.0.0

package/dist/utils/chart-presentation.d.ts

@@ -5,58 +5,6 @@
  * This source code is licensed under the MIT license found in the
  * LICENSE file in the root directory of this source tree.
  */
-/**
- * chart-presentation — the AUTHORED half of a dataset-bound chart, lowered onto
- * the bindings {@link buildChartSeries} derived from the dataset selection.
- *
- * `chart-series.ts` beside this file owns the DATA half: which columns become
- * series, which rows, which buckets. This file owns everything the author gets
- * to say about how that data LOOKS — the ruled data/presentation split of
- * objectui#4229, stated once:
- *
- *  - **Data (derived, never forwarded)** — series MEMBERSHIP and the column each
- *    binding reads. Concretely `buildChartSeries`' `dataKey`s, `xAxisKey`, and
- *    the spec's two binding keys `ChartSeries.name` and `ChartAxis.field`.
- *  - **Presentation (authored, merged forward)** — everything else on those same
- *    objects: `series[].type` (the per-series mark), `series[].yAxis` (which
- *    axis it binds to), `label`/`color`/`stack`/`variant`/`dashArray`/`opacity`,
- *    the axis definitions' `title`/`format`/`min`/`max`/`stepSize`/
- *    `showGridLines`/`position`/`logarithmic`, and the chart chrome
- *    (`showLegend`, `showDataLabels`, `colors`, `annotations`, …).
- *
- * ## Why it lives in `@object-ui/core` rather than in one plugin
- *
- * It was written for `plugin-dashboard`'s `DatasetWidget` (#3135 → objectstack#7016
- * → #4229) and lifted here by objectui#4877, when `plugin-report`'s embedded
- * report chart turned out to need the SAME merge over the same spec shapes: the
- * report was forwarding six keys and dropping every authored chrome key the
- * schema declares, and re-deriving this beside the dashboard's copy is exactly
- * the duplication objectui#4389 filed as a defect (two longhand copies of the
- * analytics label net, one per plugin, drifting apart).
- *
- * Everything here is a pure data transform over plain records, so it sits below
- * both plugins with no React and no i18n — the same layering `chart-series.ts`
- * already has (see {@link OptionLabelTranslator} there for why an i18n-resolved
- * string always arrives as an ARGUMENT rather than being read here).
- *
- * ## Two entry points, because the two surfaces declare axes differently
- *
- * A dashboard widget's `chartConfig` spells its axes as spec `ChartAxis`
- * OBJECTS. A report's `chart.xAxis` / `chart.yAxis` are bare dimension/measure
- * NAME strings — on that surface the axes are pure DATA (they ARE the selection)
- * and carry no presentation at all. So:
- *
- *  - {@link mergeAuthoredPresentation} is the object-axis entry point: series
- *    merge + axis presentation, for a caller whose axes are `ChartAxis` objects.
- *  - {@link mergeAuthoredSeries} is the series merge ALONE, for a caller whose
- *    axes are names. That split is structural, not a guard: handing a bare
- *    string to {@link mergeAuthoredPresentation} would run it through
- *    `axisPresentation`, which reads nothing off a string and would synthesise a
- *    `yAxis: [{}]` entry — a y-axis declaring nothing but its own existence,
- *    which is precisely how the COUNT of entries turns on a secondary axis. A
- *    surface that cannot author axis presentation should not be able to reach
- *    the code that reads it.
- */
 import type { ChartSeriesBinding } from './chart-series.js';
 /** Authored spec `ChartSeries` presentation, in the renderer's internal spelling. */
 export interface AuthoredSeriesPresentation {
@@ -76,39 +24,25 @@ export type MergedChartSeries = ChartSeriesBinding & AuthoredSeriesPresentation;
  * One authored `ChartSeries`, minus its `name` — i.e. everything about it that
  * is presentation rather than membership.
  *
- * `type` is narrowed to the three families that COMPOSE on one cartesian plot,
- * because this array reaches the renderer already speaking the internal shape
- * (`ChartRenderer` forwards a `dataKey`-shaped array untouched, so
- * `normalizeChartSchema`'s own identical narrowing never sees it). Without the
- * narrowing a `type: 'pie'` would not merely be inert — it would count as a
- * family disagreement in `effectiveChartFamily`, flip the whole chart into a
- * combo, and then draw that series as a bar anyway.
+ * `type` is narrowed to the three families that COMPOSE on one cartesian plot.
+ * Without the narrowing a `type: 'pie'` would not merely be inert — it would
+ * count as a family disagreement in `effectiveChartFamily`, flip the whole
+ * chart into a combo, and then draw that series as a bar anyway.
+ *
+ * `ChartRenderer` now narrows the same way for every series it receives,
+ * `dataKey`-shaped or not (`01c27c431` fixed the fast path that used to
+ * forward a `dataKey`-shaped array straight through, so `normalizeChartSchema`'s
+ * own identical narrowing never saw it) — so this module is no longer that
+ * narrowing's only line of defense. It stays anyway:
+ * `AuthoredSeriesPresentation.chartType` is a typed, narrower field
+ * (`'bar' | 'line' | 'area'`) this module's own callers read directly, and the
+ * double narrowing downstream is idempotent.
  */
 export declare function seriesPresentation(raw: Record<string, unknown>): AuthoredSeriesPresentation;
-/**
- * One authored `ChartAxis`, minus its `field` — the axis's presentation.
- *
- * `field` is the one DATA key on an axis (it names the plotted column), and
- * dropping it here is what keeps membership with the dataset **structurally**
- * rather than by a guard: `normalizeChartSchema` synthesises series out of
- * `yAxis[].field` when a chart declares no series, so a forwarded `field`
- * would be a live membership channel on an empty selection. With it gone the
- * axis carries scale and chrome only, and the count of entries — which is what
- * turns on the secondary axis (`yAxes.length > 1`) — survives, including for
- * an entry that declares nothing but its own existence.
- *
- * Keys the renderer does not read on a given axis are dropped by
- * `normalizeChartSchema`, the ONE normalization layer (#2880 S1): today it
- * keeps `format`/`title`/`showGridLines` on the x-axis and the full set on the
- * y-axes. That narrowing is deliberately NOT mirrored here — a second copy
- * would drift from the renderer's real capability the moment it grew.
- */
-export declare function axisPresentation(raw: unknown): Record<string, unknown>;
 /**
  * Merge an authored `series[]` array's PRESENTATION onto the bindings the
- * dataset selection derived — the series half of #4229's split, and the whole
- * of it for a surface whose axes are names rather than objects (see the file
- * header).
+ * dataset selection derived — the series half of #4229's split, and the only
+ * half this module lowers (see the file header).
  *
  * The match rule is **by name/key**: an authored `series[].name` is paired with
  * the derived binding whose `dataKey` it equals, and the pairing decides
@@ -136,28 +70,10 @@ export declare function axisPresentation(raw: unknown): Record<string, unknown>;
  */
 export declare function mergeAuthoredSeries(derived: ChartSeriesBinding[], authoredSeries: unknown): MergedChartSeries[];
 /**
- * Merge an authored chart config's PRESENTATION onto the series and axes the
- * dataset selection derived — the one place that happens for a surface whose
- * axes are spec `ChartAxis` OBJECTS (#4229).
- *
- * The series half is {@link mergeAuthoredSeries}; see it for the match rule and
- * for why membership is safe. The axes half reads `xAxis` / `yAxis` through
- * {@link axisPresentation}, which is why a surface spelling those as bare NAME
- * strings must call `mergeAuthoredSeries` directly instead (file header).
- *
- * @param derived the bindings {@link buildChartSeries} produced from the selection
- * @param raw the authored chart config (anything, incl. absent)
- * @returns the merged series, plus the presentation-only axes to spread onto
- *   the chart schema (absent when the author declared none)
- */
-export declare function mergeAuthoredPresentation(derived: ChartSeriesBinding[], raw: unknown): {
-    series: MergedChartSeries[];
-    axes: Record<string, unknown>;
-};
-/**
- * Lower an authored chart config's CHROME (spec `ChartConfigSchema` /
- * `ReportChartSchema` — the same keys on both) onto the chart schema a
- * dataset-bound surface hands the renderer.
+ * Lower an authored chart config's CHROME (spec
+ * `DashboardWidgetChartConfigSchema` / `ReportChartSchema`, both extensions of
+ * `ChartConfigSchema` that keep its chrome keys unchanged) onto the chart
+ * schema a dataset-bound surface hands the renderer.
  *
  * ## Why this is a whitelist and not a spread
  *
@@ -181,20 +97,48 @@ export declare function mergeAuthoredPresentation(derived: ChartSeriesBinding[],
  *     exists to remove.
  *  2. **It does not fight the dataset derivation.** `type` stays out: the
  *     calling surface's own type already picks the chart family, which is the
- *     dataset path's chart-family channel.
- *
- * `aria` is the one declared key with **no reader at all**: `AdvancedChartImpl`
- * has no `aria` prop, and `SchemaRenderer`'s ARIA injection reads the FLAT
- * `ariaLabel`/`ariaDescribedBy`/`role`, never a nested `aria` object. It is
- * therefore left unforwarded on purpose (criterion 1) rather than papered over
- * with a caller-side flattening that would also collide with the accessible
- * name `description` already sets — reported back to objectstack#5175's
- * narrowing half instead.
+ *     dataset path's chart-family channel. The spec agrees on the dashboard
+ *     carrier: since 17.5.0 `DashboardWidgetChartConfigSchema` refuses
+ *     `chartConfig.type` at parse, with `xAxis` / `yAxis` / `series`, none of
+ *     which this whitelist ever lowered (objectui#11315).
+ *
+ * `aria` is not lowered either. No renderer reads it: `AdvancedChartImpl` has
+ * no `aria` prop, and `SchemaRenderer`'s ARIA injection reads the FLAT
+ * `ariaLabel`/`ariaDescribedBy`/`role`, never a nested `aria` object (criterion
+ * 1). And it is no longer declared: spec 17.5.0 retired `ChartConfig.aria` as
+ * a `retiredKey` tombstone (objectstack#17751, objectui#4044), so an authored
+ * one is refused at parse. The accessible name a chart applies is
+ * `description`, above.
  *
  * `title` IS emitted here. A caller that paints the title itself (the report
  * renderer's own `h3` above the chart) must drop it from the result, or the
  * chart draws a second one.
  *
+ * ## `title` / `subtitle` / `description` are `I18nLabel`, and travel as such
+ *
+ * `ChartConfigSchema` types all three as the spec's `I18nLabel` union — a plain
+ * string OR an inline locale map — so all three are lowered by
+ * {@link forwardedI18nLabel}, which hands the authored value on untouched for
+ * the renderer to resolve against the viewer's language. Read that helper for
+ * why resolving cannot happen in this package.
+ *
+ * ⚠️ LEDGERED, by name, as still unresolved after objectui#9038 — not in
+ * that card's scope and not reached by the change above:
+ *
+ *  - **A series `label`** still goes through {@link labelText}'s
+ *    first-string-wins pick, the design objectui#4020 ledgered and a caller
+ *    can override. Not reopened here.
+ *
+ * ✓ CLEARED, objectui#9150 — **the report renderer's own heading.**
+ * `DatasetReportChart` (`@object-ui/plugin-report`) still drops `title` from
+ * this result and still paints its own `h3`, but that read site no longer
+ * narrows `chart.title` to a plain string: it resolves the union through
+ * `pickLocalized` against the viewer's language, like every other `I18nLabel`
+ * on that surface. Kept here rather than deleted because the ledger entry is
+ * what the fixing card was dispatched from, and because the FIRST half of it —
+ * that a caller painting the title itself must drop `title` from this result —
+ * is a live constraint on this whitelist, stated above.
+ *
  * @param raw the authored chart config (anything, incl. absent)
  * @param fieldCategoryColors per-category colours resolved from the category
  *   dimension's own select/lookup option colours, merged UNDER an explicit
@@ -203,3 +147,42 @@ export declare function mergeAuthoredPresentation(derived: ChartSeriesBinding[],
  *   derived chart schema and every undeclared key keeps the renderer's default
  */
 export declare function chartConfigPresentation(raw: unknown, fieldCategoryColors?: Record<string, string> | null): Record<string, unknown>;
+/**
+ * Whether a chart of this family IGNORES `compareTo` — the one declaration of
+ * that rule (objectui#7495).
+ *
+ * Every surface that turns a `compareTo` into a comparison reads this; none
+ * keeps a list of its own. The inline chart path (`@object-ui/plugin-charts`'
+ * ObjectChart) skips the comparison fetch and synthesises no overlay series for
+ * these families, and the dataset widget path (`@object-ui/plugin-dashboard`'s
+ * DatasetWidget) forwards no `compareTo` to the executor for a chart of one of
+ * them, so the comparison pass never runs and no overlay series is appended.
+ *
+ *  - `pie` / `donut` / `funnel` — single-distribution charts: a comparison
+ *    overlay has no meaning on them, and the renderer's pie and funnel arms
+ *    draw only `series[0]`.
+ *  - `scatter` (objectui#7402) — a scatter binds ONE measure: the renderer reads
+ *    y through the single `YAxis dataKey={series[0].dataKey}`, so an overlay was
+ *    painted on the PRIMARY's y and "previous period" landed exactly on top of
+ *    "current". Drawing it honestly needs the multi-measure projection declined
+ *    as option A of objectui#7194; `compareTo` on a scatter returns WITH that
+ *    projection.
+ *
+ * It reads the RENDERER's chart family (`bar`, `pie`, `scatter`, …), not a
+ * dashboard widget type: a caller whose widget types alias a family (the
+ * dashboard maps `bubble` to `scatter` and `pyramid` to `funnel`) maps first and
+ * asks about the family. An absent or unrecognised family does NOT ignore
+ * `compareTo` — the comparison runs.
+ *
+ * Why it lives here: the dashboard reaches `@object-ui/plugin-charts` only as a
+ * devDependency, so this package — a runtime dependency of both — is the one
+ * place both paths can read. Two copies were how the lists drifted apart: the
+ * dashboard's said "scatter only" while the charts package said all four, so a
+ * compare-to pie widget ran a comparison query whose overlay the renderer then
+ * dropped (objectui#7495; objectui#4389 is the precedent that a second copy of
+ * chart-presentation logic is a defect).
+ *
+ * @param chartType the chart family, or `undefined` when none is declared
+ * @returns `true` for `pie`, `donut`, `funnel` and `scatter`; `false` otherwise
+ */
+export declare function chartTypeIgnoresCompareTo(chartType: string | undefined): boolean;

package/dist/utils/chart-presentation.js

@@ -8,8 +8,11 @@
 const isRecord = (v) => !!v && typeof v === 'object' && !Array.isArray(v);
 /**
  * An i18n label is a plain string or a `{ en, zh-CN, … }` record; charts render
- * a string. Same pick `normalizeChartSchema` makes, so a label reads the same
- * on both paths.
+ * a string.
+ *
+ * ⚠️ Its one caller is {@link seriesPresentation}'s `label`. An axis `title`
+ * read this too until `061f5e829` moved it off the pick, and the axis lowering
+ * itself is gone since objectui#11372 (file header).
  *
  * **First-string-wins, deliberately, and deliberately NOT locale-aware** — this
  * package is React-free and holds no i18n provider, so it cannot know which
@@ -27,17 +30,83 @@ function labelText(v) {
     }
     return undefined;
 }
+/**
+ * An authored `I18nLabel` that travels to the renderer **unresolved** — the
+ * chart's own `title` / `subtitle` / `description` (objectui#9038).
+ *
+ * ## Why this does not resolve, and why that is not {@link labelText}'s answer
+ *
+ * These three keys are lowered onto a chart SCHEMA slot that already declares
+ * the union: `normalizeChartSchema` (`@object-ui/plugin-charts`) resolves
+ * `title`/`subtitle`/`description` through `pickLocalized` with the viewer's
+ * language, which `ChartRenderer` reads from `useObjectTranslation` and hands
+ * down (objectui#8943), and `ObjectChart` reads `schema.title` through the same
+ * resolver for its drill heading. So the value's one resolution point is
+ * already downstream of here, holding the one thing this package does not have
+ * — the viewer. Forwarding is what lets that resolver see the value at all.
+ *
+ * Resolving here is not merely unnecessary, it is unavailable: `pickLocalized`
+ * lives in `@object-ui/i18n`, which DEPENDS on this package. Declaring the
+ * reverse edge makes the build graph cyclic (measured: `turbo run build
+ * --filter=@object-ui/core` refuses with `Cyclic dependency detected`), and
+ * that package's entry point is a React provider plus hooks — the layering
+ * this file's header states, arrived at from the other side.
+ *
+ * ⛔ Do NOT "fix" this by reusing {@link labelText}. The two answer different
+ * questions and only one of them is a choice:
+ *
+ *  - `labelText` is a locale-unaware PICK for a slot whose consumer takes a
+ *    plain string. It is wrong for a zh console and is ledgered as such
+ *    (objectui#4020) because a caller that CAN resolve the language overrides
+ *    the merged label — the mitigation depends on the value still existing.
+ *  - The guard this replaced (`typeof v === 'string' && v ? v : undefined`)
+ *    offered no such route: it ERASED the map arm, the `if (title)` guard then
+ *    skipped the assignment, and the chart drew **no heading at all**, in every
+ *    language, with no diagnostic. Nothing downstream could override a key that
+ *    never arrived.
+ *
+ * ## The admission test, and what it deliberately does not decide
+ *
+ * A plain string, or a record carrying at least one usable string entry. That
+ * is the same "is there anything here" question the `if (title)` truthiness
+ * guard always asked, extended to the map arm — it does NOT decide which limb
+ * wins, which stays `pickLocalized`'s alone. Everything else (a number, a
+ * boolean, an array, `''`, `{}`, a record with no string value) is refused
+ * exactly as before, so no key reaches the caller that cannot render, and the
+ * `@returns` contract below — only keys that resolved — still holds.
+ *
+ * The map is forwarded VERBATIM: `InlineLocaleMapSchema` is
+ * `z.record(<tag>, z.string())` and enforcing that belongs at the parse, not in
+ * a renderer-side coercion (AGENTS.md #0.1). A non-string entry falls through
+ * `pickLocalized`'s limbs exactly as an absent one does, which is why admitting
+ * the record on the strength of one usable entry cannot paint `[object
+ * Object]`.
+ */
+function forwardedI18nLabel(v) {
+    if (typeof v === 'string')
+        return v || undefined;
+    if (isRecord(v) && Object.values(v).some((x) => typeof x === 'string' && x)) {
+        return v;
+    }
+    return undefined;
+}
 /**
  * One authored `ChartSeries`, minus its `name` — i.e. everything about it that
  * is presentation rather than membership.
  *
- * `type` is narrowed to the three families that COMPOSE on one cartesian plot,
- * because this array reaches the renderer already speaking the internal shape
- * (`ChartRenderer` forwards a `dataKey`-shaped array untouched, so
- * `normalizeChartSchema`'s own identical narrowing never sees it). Without the
- * narrowing a `type: 'pie'` would not merely be inert — it would count as a
- * family disagreement in `effectiveChartFamily`, flip the whole chart into a
- * combo, and then draw that series as a bar anyway.
+ * `type` is narrowed to the three families that COMPOSE on one cartesian plot.
+ * Without the narrowing a `type: 'pie'` would not merely be inert — it would
+ * count as a family disagreement in `effectiveChartFamily`, flip the whole
+ * chart into a combo, and then draw that series as a bar anyway.
+ *
+ * `ChartRenderer` now narrows the same way for every series it receives,
+ * `dataKey`-shaped or not (`01c27c431` fixed the fast path that used to
+ * forward a `dataKey`-shaped array straight through, so `normalizeChartSchema`'s
+ * own identical narrowing never saw it) — so this module is no longer that
+ * narrowing's only line of defense. It stays anyway:
+ * `AuthoredSeriesPresentation.chartType` is a typed, narrower field
+ * (`'bar' | 'line' | 'area'`) this module's own callers read directly, and the
+ * double narrowing downstream is idempotent.
  */
 export function seriesPresentation(raw) {
     const out = {};
@@ -61,54 +130,10 @@ export function seriesPresentation(raw) {
         out.opacity = raw.opacity;
     return out;
 }
-/**
- * One authored `ChartAxis`, minus its `field` — the axis's presentation.
- *
- * `field` is the one DATA key on an axis (it names the plotted column), and
- * dropping it here is what keeps membership with the dataset **structurally**
- * rather than by a guard: `normalizeChartSchema` synthesises series out of
- * `yAxis[].field` when a chart declares no series, so a forwarded `field`
- * would be a live membership channel on an empty selection. With it gone the
- * axis carries scale and chrome only, and the count of entries — which is what
- * turns on the secondary axis (`yAxes.length > 1`) — survives, including for
- * an entry that declares nothing but its own existence.
- *
- * Keys the renderer does not read on a given axis are dropped by
- * `normalizeChartSchema`, the ONE normalization layer (#2880 S1): today it
- * keeps `format`/`title`/`showGridLines` on the x-axis and the full set on the
- * y-axes. That narrowing is deliberately NOT mirrored here — a second copy
- * would drift from the renderer's real capability the moment it grew.
- */
-export function axisPresentation(raw) {
-    const out = {};
-    if (!isRecord(raw))
-        return out;
-    const title = labelText(raw.title);
-    if (title)
-        out.title = title;
-    if (typeof raw.format === 'string' && raw.format)
-        out.format = raw.format;
-    if (typeof raw.min === 'number' && Number.isFinite(raw.min))
-        out.min = raw.min;
-    if (typeof raw.max === 'number' && Number.isFinite(raw.max))
-        out.max = raw.max;
-    if (typeof raw.stepSize === 'number' && Number.isFinite(raw.stepSize) && raw.stepSize > 0) {
-        out.stepSize = raw.stepSize;
-    }
-    if (typeof raw.showGridLines === 'boolean')
-        out.showGridLines = raw.showGridLines;
-    if (raw.position === 'left' || raw.position === 'right' || raw.position === 'top' || raw.position === 'bottom') {
-        out.position = raw.position;
-    }
-    if (typeof raw.logarithmic === 'boolean')
-        out.logarithmic = raw.logarithmic;
-    return out;
-}
 /**
  * Merge an authored `series[]` array's PRESENTATION onto the bindings the
- * dataset selection derived — the series half of #4229's split, and the whole
- * of it for a surface whose axes are names rather than objects (see the file
- * header).
+ * dataset selection derived — the series half of #4229's split, and the only
+ * half this module lowers (see the file header).
  *
  * The match rule is **by name/key**: an authored `series[].name` is paired with
  * the derived binding whose `dataKey` it equals, and the pairing decides
@@ -149,43 +174,10 @@ export function mergeAuthoredSeries(derived, authoredSeries) {
     });
 }
 /**
- * Merge an authored chart config's PRESENTATION onto the series and axes the
- * dataset selection derived — the one place that happens for a surface whose
- * axes are spec `ChartAxis` OBJECTS (#4229).
- *
- * The series half is {@link mergeAuthoredSeries}; see it for the match rule and
- * for why membership is safe. The axes half reads `xAxis` / `yAxis` through
- * {@link axisPresentation}, which is why a surface spelling those as bare NAME
- * strings must call `mergeAuthoredSeries` directly instead (file header).
- *
- * @param derived the bindings {@link buildChartSeries} produced from the selection
- * @param raw the authored chart config (anything, incl. absent)
- * @returns the merged series, plus the presentation-only axes to spread onto
- *   the chart schema (absent when the author declared none)
- */
-export function mergeAuthoredPresentation(derived, raw) {
-    const config = isRecord(raw) ? raw : {};
-    const series = mergeAuthoredSeries(derived, config.series);
-    const axes = {};
-    const xAxis = axisPresentation(config.xAxis);
-    if (Object.keys(xAxis).length > 0)
-        axes.xAxis = xAxis;
-    // The COUNT of y-axis entries is itself presentation — it is what declares a
-    // secondary axis — so every declared entry keeps its slot even when it
-    // carries nothing but `field` (which is data and does not travel).
-    const yAxisRaw = Array.isArray(config.yAxis)
-        ? config.yAxis
-        : config.yAxis !== undefined
-            ? [config.yAxis]
-            : [];
-    if (yAxisRaw.length > 0)
-        axes.yAxis = yAxisRaw.map(axisPresentation);
-    return { series, axes };
-}
-/**
- * Lower an authored chart config's CHROME (spec `ChartConfigSchema` /
- * `ReportChartSchema` — the same keys on both) onto the chart schema a
- * dataset-bound surface hands the renderer.
+ * Lower an authored chart config's CHROME (spec
+ * `DashboardWidgetChartConfigSchema` / `ReportChartSchema`, both extensions of
+ * `ChartConfigSchema` that keep its chrome keys unchanged) onto the chart
+ * schema a dataset-bound surface hands the renderer.
  *
  * ## Why this is a whitelist and not a spread
  *
@@ -209,20 +201,48 @@ export function mergeAuthoredPresentation(derived, raw) {
  *     exists to remove.
  *  2. **It does not fight the dataset derivation.** `type` stays out: the
  *     calling surface's own type already picks the chart family, which is the
- *     dataset path's chart-family channel.
+ *     dataset path's chart-family channel. The spec agrees on the dashboard
+ *     carrier: since 17.5.0 `DashboardWidgetChartConfigSchema` refuses
+ *     `chartConfig.type` at parse, with `xAxis` / `yAxis` / `series`, none of
+ *     which this whitelist ever lowered (objectui#11315).
  *
- * `aria` is the one declared key with **no reader at all**: `AdvancedChartImpl`
- * has no `aria` prop, and `SchemaRenderer`'s ARIA injection reads the FLAT
- * `ariaLabel`/`ariaDescribedBy`/`role`, never a nested `aria` object. It is
- * therefore left unforwarded on purpose (criterion 1) rather than papered over
- * with a caller-side flattening that would also collide with the accessible
- * name `description` already sets — reported back to objectstack#5175's
- * narrowing half instead.
+ * `aria` is not lowered either. No renderer reads it: `AdvancedChartImpl` has
+ * no `aria` prop, and `SchemaRenderer`'s ARIA injection reads the FLAT
+ * `ariaLabel`/`ariaDescribedBy`/`role`, never a nested `aria` object (criterion
+ * 1). And it is no longer declared: spec 17.5.0 retired `ChartConfig.aria` as
+ * a `retiredKey` tombstone (objectstack#17751, objectui#4044), so an authored
+ * one is refused at parse. The accessible name a chart applies is
+ * `description`, above.
  *
  * `title` IS emitted here. A caller that paints the title itself (the report
  * renderer's own `h3` above the chart) must drop it from the result, or the
  * chart draws a second one.
  *
+ * ## `title` / `subtitle` / `description` are `I18nLabel`, and travel as such
+ *
+ * `ChartConfigSchema` types all three as the spec's `I18nLabel` union — a plain
+ * string OR an inline locale map — so all three are lowered by
+ * {@link forwardedI18nLabel}, which hands the authored value on untouched for
+ * the renderer to resolve against the viewer's language. Read that helper for
+ * why resolving cannot happen in this package.
+ *
+ * ⚠️ LEDGERED, by name, as still unresolved after objectui#9038 — not in
+ * that card's scope and not reached by the change above:
+ *
+ *  - **A series `label`** still goes through {@link labelText}'s
+ *    first-string-wins pick, the design objectui#4020 ledgered and a caller
+ *    can override. Not reopened here.
+ *
+ * ✓ CLEARED, objectui#9150 — **the report renderer's own heading.**
+ * `DatasetReportChart` (`@object-ui/plugin-report`) still drops `title` from
+ * this result and still paints its own `h3`, but that read site no longer
+ * narrows `chart.title` to a plain string: it resolves the union through
+ * `pickLocalized` against the viewer's language, like every other `I18nLabel`
+ * on that surface. Kept here rather than deleted because the ledger entry is
+ * what the fixing card was dispatched from, and because the FIRST half of it —
+ * that a caller painting the title itself must drop `title` from this result —
+ * is a live constraint on this whitelist, stated above.
+ *
  * @param raw the authored chart config (anything, incl. absent)
  * @param fieldCategoryColors per-category colours resolved from the category
  *   dimension's own select/lookup option colours, merged UNDER an explicit
@@ -233,18 +253,20 @@ export function mergeAuthoredPresentation(derived, raw) {
 export function chartConfigPresentation(raw, fieldCategoryColors) {
     const config = isRecord(raw) ? raw : {};
     const out = {};
-    const text = (v) => (typeof v === 'string' && v ? v : undefined);
     if (typeof config.showLegend === 'boolean')
         out.showLegend = config.showLegend;
     if (typeof config.showDataLabels === 'boolean')
         out.showDataLabels = config.showDataLabels;
-    const title = text(config.title);
+    // The three `I18nLabel` slots, carried through unresolved — see
+    // {@link forwardedI18nLabel} for why this package forwards rather than picks,
+    // and for what is still ledgered as unresolved on purpose.
+    const title = forwardedI18nLabel(config.title);
     if (title)
         out.title = title;
-    const subtitle = text(config.subtitle);
+    const subtitle = forwardedI18nLabel(config.subtitle);
     if (subtitle)
         out.subtitle = subtitle;
-    const description = text(config.description);
+    const description = forwardedI18nLabel(config.description);
     if (description)
         out.description = description;
     // A non-positive height would collapse the plot; the container default is the
@@ -278,3 +300,46 @@ export function chartConfigPresentation(raw, fieldCategoryColors) {
     }
     return out;
 }
+/** The families {@link chartTypeIgnoresCompareTo} answers `true` for. */
+const CHART_TYPES_IGNORING_COMPARE_TO = new Set(['pie', 'donut', 'funnel', 'scatter']);
+/**
+ * Whether a chart of this family IGNORES `compareTo` — the one declaration of
+ * that rule (objectui#7495).
+ *
+ * Every surface that turns a `compareTo` into a comparison reads this; none
+ * keeps a list of its own. The inline chart path (`@object-ui/plugin-charts`'
+ * ObjectChart) skips the comparison fetch and synthesises no overlay series for
+ * these families, and the dataset widget path (`@object-ui/plugin-dashboard`'s
+ * DatasetWidget) forwards no `compareTo` to the executor for a chart of one of
+ * them, so the comparison pass never runs and no overlay series is appended.
+ *
+ *  - `pie` / `donut` / `funnel` — single-distribution charts: a comparison
+ *    overlay has no meaning on them, and the renderer's pie and funnel arms
+ *    draw only `series[0]`.
+ *  - `scatter` (objectui#7402) — a scatter binds ONE measure: the renderer reads
+ *    y through the single `YAxis dataKey={series[0].dataKey}`, so an overlay was
+ *    painted on the PRIMARY's y and "previous period" landed exactly on top of
+ *    "current". Drawing it honestly needs the multi-measure projection declined
+ *    as option A of objectui#7194; `compareTo` on a scatter returns WITH that
+ *    projection.
+ *
+ * It reads the RENDERER's chart family (`bar`, `pie`, `scatter`, …), not a
+ * dashboard widget type: a caller whose widget types alias a family (the
+ * dashboard maps `bubble` to `scatter` and `pyramid` to `funnel`) maps first and
+ * asks about the family. An absent or unrecognised family does NOT ignore
+ * `compareTo` — the comparison runs.
+ *
+ * Why it lives here: the dashboard reaches `@object-ui/plugin-charts` only as a
+ * devDependency, so this package — a runtime dependency of both — is the one
+ * place both paths can read. Two copies were how the lists drifted apart: the
+ * dashboard's said "scatter only" while the charts package said all four, so a
+ * compare-to pie widget ran a comparison query whose overlay the renderer then
+ * dropped (objectui#7495; objectui#4389 is the precedent that a second copy of
+ * chart-presentation logic is a defect).
+ *
+ * @param chartType the chart family, or `undefined` when none is declared
+ * @returns `true` for `pie`, `donut`, `funnel` and `scatter`; `false` otherwise
+ */
+export function chartTypeIgnoresCompareTo(chartType) {
+    return typeof chartType === 'string' && CHART_TYPES_IGNORING_COMPARE_TO.has(chartType);
+}