test(metadata-protocol): migrate the dashboard fixtures and pin the four new unauthorable columns

The publish-gate and runtime-gate boards authored `chartConfig.type` / `.xAxis`
/ `.yAxis` / `.series`, which the parse door now refuses. They keep an
APPEARANCE `chartConfig` rather than dropping the key, so the fixtures still
exercise it. The #17502 unauthorable-columns pin gains the four tombstoned
columns at the same depth as `chartConfig.aria`.

Claude-Session: https://claude.ai/code/session_01LvwGppdonww4zGLWZo5rho
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

packages/metadata-protocol/src/protocol.dashboard-dataset-publish-gate.test.ts

@@ -83,7 +83,15 @@ const legitBoard = () => ({
             dataset: 'orders_ds',
             dimensions: ['status'],
             values: ['order_count'],
-            chartConfig: { type: 'bar', xAxis: { field: 'status' }, yAxis: [{ field: 'order_count' }] },
+        // ⚠️ The `chartConfig` on these two widgets carried `type` / `xAxis` /
+        // `yAxis` / `series`, which are refused on a dataset-bound widget since the
+        // chart-structure ownership ruling (ADR-0021; 2026-09-12): the dataset
+        // decides which series exist and which column each one reads. The board is
+        // still a legitimate three-widget board — the bindings it used to restate
+        // are the `dimensions` / `values` on the very same widgets — so the fixture
+        // keeps an APPEARANCE `chartConfig` rather than dropping the key, which is
+        // what keeps this fixture exercising the key at all.
+            chartConfig: { title: 'By Status', showLegend: false },
         },
         {
             id: 'by_region',
@@ -92,7 +100,7 @@ const legitBoard = () => ({
             dataset: 'orders_ds',
             dimensions: ['region'],
             values: ['order_count'],
-            chartConfig: { type: 'donut', series: [{ name: 'order_count' }] },
+            chartConfig: { title: 'By Region' },
         },
     ],
 });

packages/metadata-protocol/src/protocol.meta-types-unauthorable-columns.test.ts

@@ -280,18 +280,29 @@ describe('#17502 — the served repeater row offers no column the parse door ref
         expect(overDropped).toEqual([]);
 
         // Non-vacuity: without this the two assertions above pass over a ledger
-        // that read nothing at all. `dashboard` is the type that exercises both
-        // depths — the five repeater-row columns pinned above, and three
-        // top-level tombstones — so the ledger is proven to reach a row shape
-        // and not only the surface. Sorted, so key ORDER is not what is pinned.
+        // that read nothing at all. `dashboard` is the type that exercises every
+        // depth — the five repeater-row columns pinned above, three top-level
+        // tombstones, and FIVE inside the widget's own `chartConfig` — so the
+        // ledger is proven to reach a row shape and not only the surface.
+        // Sorted, so key ORDER is not what is pinned.
         expect([...(removedByType.get('dashboard') ?? [])].sort()).toEqual([
             ...RETIRED_WIDGET_COLUMNS.map((k) => `dashboard.properties.widgets.items.properties.${k}`),
             'dashboard.properties.refreshInterval',
             'dashboard.properties.aria',
             'dashboard.properties.performance',
-            // [#17751, arrived with main] `ChartConfigSchema.aria` retired one
-            // level deeper than the widget row, inside `chartConfig`.
+            // [#17751] `ChartConfigSchema.aria` retired one level deeper than the
+            // widget row, inside `chartConfig`.
             'dashboard.properties.widgets.items.properties.chartConfig.properties.aria',
+            // [#17385] The four STRUCTURE keys, tombstoned on the widget's own
+            // `chartConfig` carrier (`DashboardWidgetChartConfigSchema`) when the
+            // ownership ruling landed: on a dataset-bound widget the dataset
+            // decides which series exist and which column each one reads
+            // (ADR-0021; 2026-09-12). Same depth as `aria` above, and the same
+            // reason for being here — a `retiredKey()` keeps the key in the
+            // walked shape, so the served payload must drop the column.
+            ...['type', 'xAxis', 'yAxis', 'series'].map(
+                (k) => `dashboard.properties.widgets.items.properties.chartConfig.properties.${k}`,
+            ),
         ].sort());
     });
 

packages/metadata-protocol/src/protocol.runtime-gate-stored-universe.test.ts

@@ -121,12 +121,20 @@ const threeWidgetBoard = (dataset: string) => ({
         {
             id: 'by_status', type: 'bar', title: 'By status', dataset,
             dimensions: ['status'], values: ['order_count'],
-            chartConfig: { type: 'bar', xAxis: { field: 'status' }, yAxis: [{ field: 'order_count' }] },
+        // ⚠️ The `chartConfig` on these two widgets carried `type` / `xAxis` /
+        // `yAxis` / `series`, which are refused on a dataset-bound widget since the
+        // chart-structure ownership ruling (ADR-0021; 2026-09-12): the dataset
+        // decides which series exist and which column each one reads. The board is
+        // still a legitimate three-widget board — the bindings it used to restate
+        // are the `dimensions` / `values` on the very same widgets — so the fixture
+        // keeps an APPEARANCE `chartConfig` rather than dropping the key, which is
+        // what keeps this fixture exercising the key at all.
+            chartConfig: { title: 'By status', showLegend: false },
         },
         {
             id: 'by_region', type: 'donut', title: 'By region', dataset,
             dimensions: ['region'], values: ['order_count'],
-            chartConfig: { type: 'donut', series: [{ name: 'order_count' }] },
+            chartConfig: { title: 'By region' },
         },
     ],
 });