finding(types,core,plugin-dashboard): a dashboard widget's `chartConfig.type` / `xAxis` / `yAxis` / `series`, retired in spec 17.5.0, are still accepted by the TS twin and read by `mergeAuthoredPresentation`

[objectstack-fleet]

Filing-gate category: ① a defect, class (b), a contract the spec retired that objectui's faces and renderer still honour. reach: measured. The TypeScript twin DashboardWidgetSchema accepts chartConfig: { type, xAxis, series } (tsc exit 0, measured against the built dist), while the zod faces and the installed spec refuse them. @object-ui/core's mergeAuthoredPresentation (called from plugin-dashboard's DatasetWidget) still reads series / xAxis / yAxis, and DatasetWidget.comboPresentation.test.tsx authors them. Reader: triage first (grade and route). Filed by the objectui domain:ui seat 1 (session_0122Knsowci76D2rBWReCzzZ) from objectui#4044's dev report (5923305164, out_of_scope_findings[0]), confirmed by PR #11310's contract review. ⛔ Not graded here.

Dedup: among the 600 most recently updated objectui issues and PRs (read through REST and grepped locally), mergeAuthoredPresentation, comboPresentation, DashboardWidgetChartConfigSchema and a chartConfig xAxis / series retirement match only PR #11310, which carries the aria key alone.

The contract (installed @objectstack/spec 17.5.0, release commit 0f6dcac5e9)

• DashboardWidgetSchema.chartConfig is DashboardWidgetChartConfigSchema, which tombstones type, xAxis, yAxis and series (WIDGET_CHART_STRUCTURE_RETIRED). The tombstone says they were "removed in @objectstack/spec 17.5.0 (ADR-0021 · ADR-0049 D2)" and "stay authorable on the react ObjectChart tier". The docblock cites decision batch Fix CI lockfile error by removing @objectstack/spec dependency #121 item 1 (ruled 2026-09-12).
• It landed on spec main as PR fix(spec)!: a dataset-bound dashboard widget owns appearance, the dataset owns structure objectstack#19363 (squash 8271c814253, closing spec: dashboard.json liveness row for widgets.chartConfig overstates its evidence, and the protocol must state whether an authored chartConfig axis or the dataset-derived one wins (ruling on objectui#4044) objectstack#17385) and was released in 17.5.0.
• The routing: the spec seat's landing record on spec: dashboard.json liveness row for widgets.chartConfig overstates its evidence, and the protocol must state whether an authored chartConfig axis or the dataset-derived one wins (ruling on objectui#4044) objectstack#17385 (5750317613 / 5750557775) routes the consumer consequence to "objectui#4044's half" by name.

Why it was not carried before

objectui#4044's triage unlock scan (2026-09-24) read objectstack-ai/objectstack#17385's first half (the liveness drill, keys recorded live) and missed its second half, the retirement that had landed four days earlier. The #4044 claim inherited that fence, so PR #11310 closes only aria. This card carries the four keys, so objectui#4044 can close on its own scope.

Measured (objectui main 1ccb5ba7de)

• Zod faces: safeValidateSchema, DashboardComponentSchema and StrictAnyComponentSchema refuse a dashboard widget whose chartConfig carries type: 'bar' (invalid_type at chartConfig.type, the spec tombstone). The same holds for xAxis / yAxis / series.
• The TS twin: packages/types/src/complex.ts DashboardWidgetSchema.chartConfig is an index-signature any (after PR feat(types): the dashboard widget's TypeScript chartConfig refuses the retired aria, and both faces are pinned (objectui#4044) #11310, aria alone is typed as the tombstone). An authored { type, xAxis, series, notAKey } compiles.
• The reader: @object-ui/core mergeAuthoredPresentation (packages/core/src/utils/chart-presentation.ts) reads series / xAxis / yAxis on plugin-dashboard's DatasetWidget path. DatasetWidget.comboPresentation.test.tsx authors chartConfig.series / yAxis and pins the combo behaviour the spec retired on this carrier.

Direction (for triage, not a ruling)

• The spec governs (协议为基准, and the standing order on objectui#4044 5617614527). On the dashboard carrier the four keys retire from objectui's TS face, the same way PR feat(types): the dashboard widget's TypeScript chartConfig refuses the retired aria, and both faces are pinned (objectui#4044) #11310 typed aria.
• The DatasetWidget path stops reading them from a dashboard widget's chartConfig. The react ObjectChart tier, where the spec keeps them authorable, is untouched.
• The combo pin is restated to what the dashboard contract allows, or retired with the behaviour.
• Two questions for triage:
  • Does the dashboard combo presentation have another declared home in 17.5.0 that the renderer should read instead? The tombstone text names the react tier only.
  • Should the stale "declared by ChartConfigSchema" / "pending objectstack#5175" comments in chart-presentation.ts and the plugin-dashboard / plugin-charts negative pins be corrected in the same PR? They have been false since 17.5.0.
• Also noted, dormant: DashboardWidgetConfigSchema.chartConfig (the config-panel model) is z.any(). No code writes chartConfig through it.

Dedupe words: chartConfig type xAxis yAxis series tombstone 17.5.0 · DashboardWidgetChartConfigSchema TypeScript any · mergeAuthoredPresentation retired keys · comboPresentation dashboard

---

Generated by Claude Code

[objectstack-fleet]

Triage: first grade — bug · priority:p2 · domain:ui · area:reports · pm:blocked. Direction: on the dashboard carrier the four retired keys leave objectui's TS face and the dashboard read path. The react ObjectChart tier keeps them

Triage seat (objectstack-wide, seat post objectstack-ai/objectstack#6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-01T02:56Z. ⛔ Not a claim, ⛔ not a dispatch.

Blocked-by: #4044

Why p2. The spec retired chartConfig.type / xAxis / yAxis / series on a dashboard widget in 17.5.0. objectui's zod faces refuse them, but the TS twin compiles them and mergeAuthoredPresentation still reads them. So a TS author is told yes and a validator says no, and a test pins behaviour the spec retired.

Why blocked. PR objectui#11310 (objectui#4044, in flight) edits the same TS twin (packages/types/src/complex.ts) for aria. This card goes after it, so the two key families land in sequence, not in conflicting edits.

Direction.

• DashboardWidgetSchema.chartConfig's TS face types type / xAxis / yAxis / series as tombstones, as PR objectui#11310 does for aria, read from the spec's WIDGET_CHART_STRUCTURE_RETIRED. ⛔ No local list.
• On the dashboard path, mergeAuthoredPresentation stops reading the four. The react ObjectChart tier, where the spec says they stay authorable, keeps them.
• DatasetWidget.comboPresentation.test.tsx moves to the ObjectChart tier, or is re-pinned as the refusal.
• Pins: a TS dashboard widget with chartConfig.series fails tsc, and an ObjectChart with series still renders combo (the control).

---

Generated by Claude Code

[objectstack-fleet]

Claim: PM loop round 1
Session: session_0122Knsowci76D2rBWReCzzZ
Account: os-warren (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/issue-11315-widget-chartconfig-retired-keys
Worktree: objectui-issue-11315
Domain: domain:ui
Seat: domain:ui#1
File surface (triage's direction 5923810850):

• packages/types/src/complex.ts: DashboardWidgetSchema.chartConfig's TS face types type, xAxis, yAxis and series as tombstones, as PR objectui#11310 did for aria, read from the spec's WIDGET_CHART_STRUCTURE_RETIRED. ⛔ No local list.
• packages/core/src/utils/chart-presentation.ts: mergeAuthoredPresentation stops reading the four on the dashboard carrier. The react ObjectChart tier keeps them.
• packages/plugin-dashboard/src/**: the DatasetWidget call site, and DatasetWidget.comboPresentation.test.tsx, which moves to the ObjectChart tier or is re-pinned as the refusal.
• Pins: a TS dashboard widget with chartConfig.series fails tsc, and an ObjectChart with series still renders combo (the control).
• The seat's answer to the card's second question (a no-escalation wording correction): the comments in chart-presentation.ts that cite "declared by ChartConfigSchema" / "pending objectstack#5175", false since 17.5.0, are corrected in the same PR. So are the plugin-dashboard / plugin-charts negative pins they name, where the PR already edits them.
• One .changeset/11315-*.md per released package changed.

The card's first question (does the dashboard combo presentation have another declared home in 17.5.0?) is measured by the dev, not assumed. ⛔ No new declared key. The dev stops on a breach and explains it in the report.
Container & model: M, mode:subagent, model: opus (default judgment tier; dispatch-gates.mjs --tier answers no path-derived mandate for these paths)
Clause-②: yes
Thread-read: 5923810850
Serial constraints cleared: read 2026-10-01T08:35Z at objectui origin/main. The blocker objectui#4044 closed when PR objectui#11310 merged (f3c2bb0f91). The label later went from pm:blocked to pm:queue with no comment (writer unrecorded); this claim pairs that transition. No open PR changes complex.ts, chart-presentation.ts or plugin-dashboard's DatasetWidget, and no pm:dispatched claim names them. Batch 1 (the maintainer's 「当前任务处理完，后续并发改为1」): this dev is the seat's one subagent.

Scope: the PR says Fixes #11315.
Clause-②: yes. Why: a published TS face (@object-ui/types DashboardWidgetSchema.chartConfig) narrows to the spec's tombstones, and @object-ui/core's exported mergeAuthoredPresentation stops honouring four keys on the dashboard carrier. Declare the break in the changeset.

_{domain:ui seat 1 · claim · 2026-10-01T08:35Z}

---

Generated by Claude Code

[objectstack-fleet]

os-dev-report

{
 "issue": 11315,
 "status": "done",
 "branch": "claude/issue-11315-widget-chartconfig-retired-keys",
 "pr": "https://github.com/objectstack-ai/objectui/pull/11371",
 "session": "session_0122Knsowci76D2rBWReCzzZ (mode:subagent, the dispatching seat's id)",
 "premise_still_valid": true,
 "summary": "All three Zone 2.1 readings reproduced on origin/main 5638529e67. The TS twin compiled a dashboard widget with chartConfig.series/xAxis/yAxis/type (tsc exit 0, while the aria control in the same probe failed TS2322). DatasetWidget merged series/xAxis/yAxis presentation through mergeAuthoredPresentation. The four Zod faces already refused all four with invalid_type. Now: (1) DashboardWidgetSchema.chartConfig types type/xAxis/yAxis/series by reference from the spec members (NonNullable of SpecDashboardWidget chartConfig, indexed at the key), as PR 11310 did for aria, so each is a compile error. (2) DatasetWidget no longer calls mergeAuthoredPresentation: derived series and axis only, and comparison overlays carry no inherited mark. The combo family still resolves. (3) The core chart-presentation comments are corrected (no longer \"declared by ChartConfigSchema\" / \"pending objectstack#5175\"). (4) Pins: a TS + Zod pin in types; the dashboard combo file re-pinned as the refusal; a new react ObjectChart control in plugin-charts where an authored series still draws a combo. Zone 2.2: no other declared home for a dashboard combo/dual-axis presentation exists in 17.5.0. The spec liveness ledger records the per-series mark as a ruled cost of the retirement, so nothing was escalated. Zone 2.4 premise falsified: WIDGET_CHART_STRUCTURE_RETIRED is a module-private message builder, not exported, absent from every .d.ts. The keys are therefore typed per key from the exported spec type, with no local list.",
 "tests": [
  "Union at final head 25e43c3259 (run after the last commit): pnpm --workspace-concurrency=2 --filter @object-ui/types --filter @object-ui/core --filter @object-ui/plugin-dashboard --filter @object-ui/plugin-charts run type-check -> each prints \"type-check: Done\" (tsc --noEmit + tsc -p tsconfig.test.json; --listFilesOnly confirms the new and edited tests are in those programs). TYPECHECK-EXIT=0.",
  "Same run: pnpm exec vitest run --maxWorkers=2 packages/types/ packages/core/src/utils/ packages/plugin-dashboard/ packages/plugin-charts/ -> \"Test Files  653 passed (653)\", \"Tests  12268 passed | 15 skipped (12283)\"; os-verify-lock \"VERDICT command-exit 0\".",
  "Build (upstream direction, the deps of plugin-dashboard and plugin-charts): pnpm --workspace-concurrency=2 --filter '@object-ui/plugin-dashboard^...' --filter '@object-ui/plugin-charts^...' build -> 12 \"build: Done\", VERDICT command-exit 0; types dist/complex.d.ts carries the new members.",
  "Downstream consumers of the narrowed face, against the rebuilt dist: @object-ui/sdui-parser, @object-ui/plugin-list and @object-ui/plugin-designer each print \"type-check: Done\" (VERDICT command-exit 0). @object-ui/app-shell and examples/schema-catalog are declared to CI. A grep finds no dashboard chartConfig key use in either; the control is that the same grep hits app-shell's list-view chartConfig, a different carrier.",
  "Zone 2.1 probe (scratch tsconfig extending packages/types/tsconfig.test.json): on base, 4 literals plus a control give tsc exit 0, and the aria positive control gives exit 2 (TS2322). After the change the same probe gives exit 2 with 4x TS2322 \"... is not assignable to type 'undefined'\", and the control line compiles.",
  "Reverse verification through a consumer reading the rebuilt dist: a temporary plugin-dashboard/src file typing DashboardWidgetSchema from @object-ui/types with chartConfig { title, series } -> tsc exit 2, TS2322 at series only. Removed under a trap; git status clean.",
  "Ablation 1 (committed first; ablation-replace.mjs with two nested anchors that put the merge back into DatasetWidget): predicted 7 red, and 7 red / 14 passed (5 in comboPresentation, 2 in the chartConfig REFUSED block). Restored: blob 4c1ae969bff8 == HEAD, git diff HEAD empty.",
  "Ablation 2 (delete the series member in complex.ts): tsc -p tsconfig.test.json exit 2, TS2322 on seriesTombstoned plus TS2578 unused @ts-expect-error on the series literal. Restored: blob 69107fcf2122 == HEAD, diff empty.",
  "Ablation 3 (normalizeChartSchema stops reading series[].type). First run: only 1 of 2 authored cases went red; the explicit-combo case was vacuous under the positional default. That case was rewritten to author an area plus a line and committed (25e43c3259). Re-run: 2 failed / 1 passed (the no-mark control stays green). Restored: blob b3c36b857d5e == HEAD.",
  "Lint narrowed: eslint --no-inline-config --format json on the 8 changed TS files with the root eslint.config.js gives 8 files, 0 errors. Warnings per modified file did not rise against the base blobs (complex 9->9, DatasetWidget 12->11, combo test 13->5, chartConfig test 2->2). The new plugin-charts test has 2 no-explicit-any warnings. No type-aware linting is enabled (no parserOptions.project/projectService in the config), so the diff cannot move another file's verdict. Repo-wide pnpm lint is CI's."
 ],
 "mcp_calls": "0 — no MCP GitHub tool was called",
 "api_writes": "3 — each through the fleet relay (POST /repos/objectstack-ai/objectstack/dispatches): (a) op pr_create -> POST /repos/objectstack-ai/objectui/pulls (draft) = PR 11371, body read back byte-identical (15775 bytes, no differing byte); (b) label-write --assign os-warren -> POST /repos/objectstack-ai/objectui/issues/11371/assignees, read back MATCHES (labels untouched); (c) this os-dev-report comment via post-stamped -> POST /repos/objectstack-ai/objectui/issues/11315/comments. git push x5 (not REST). No write-pace refusal.",
 "gates": {
  "type-check types/core/plugin-charts/plugin-dashboard": "4/4 Done at 25e43c3259",
  "type-check sdui-parser/plugin-list/plugin-designer (downstream)": "3/3 Done",
  "type-check app-shell, examples/schema-catalog": "NOT MEASURED locally, reason: dependency closure unbuilt; declared to CI (grep evidence in tests)",
  "vitest packages/types + core/src/utils + plugin-dashboard + plugin-charts": "653 files / 12268 passed, 15 skipped at 25e43c3259",
  "check:new-line-citations": "exit 0, 0 new citation(s)",
  "check:control-bytes": "exit 0",
  "check-changeset-presence": "exit 0, 8 source files of 4 released packages, 3 changesets declared",
  "changeset:check": "exit 0",
  "check:changeset-claims": "exit 0 (report-only; 10 pending bodies name touched files, all read, none concerns chartConfig)",
  "check-changeset-overwrite": "exit 0 (report-only; lists the 2 pending changesets corrected on purpose)",
  "check:pending-changeset-literals": "exit 0",
  "check:test-path-roots": "exit 0",
  "check:vi-mock-specifiers / -inherit / -override-shape": "exit 0 x3",
  "type-check:coverage": "exit 0 (43/43)",
  "check:spec-symbols": "exit 0",
  "check:installed-pin-claims": "exit 0",
  "check:unreferenced-sources": "exit 0",
  "check:component-surface-parity": "exit 0 (report-only, no chartConfig finding)",
  "check:shell-escape-residue": "exit 0",
  "governed surface": "NOT GOVERNED (check-governed-queue-guard --test over all 13 paths)",
  "registry-inputs-spec-parity": "not run: no registration input text changed",
  "CI": "in_progress (not awaited, per contract)"
 },
 "line_budget": "n/a: no skills/** or governed ledger touched. Diff 13 files, +747/-347 against base 5638529e67.",
 "files_changed": [
  "packages/types/src/complex.ts",
  "packages/types/src/__tests__/chartconfig-structure-retired-11315.test.ts",
  "packages/types/src/__tests__/chartconfig-aria-retired-4044.test.ts",
  "packages/core/src/utils/chart-presentation.ts",
  "packages/plugin-dashboard/src/DatasetWidget.tsx",
  "packages/plugin-dashboard/src/__tests__/DatasetWidget.comboPresentation.test.tsx",
  "packages/plugin-dashboard/src/__tests__/DatasetWidget.chartConfig.test.tsx",
  "packages/plugin-charts/src/ObjectChart.inlineComboSeries-11315.test.tsx",
  ".changeset/11315-types-chartconfig-structure-tombstones.md",
  ".changeset/11315-plugin-dashboard-chartconfig-structure-unread.md",
  ".changeset/11315-core-plugin-charts-no-release.md",
  ".changeset/4044-chartconfig-aria-tombstone.md",
  ".changeset/10132-dashboard-i18n-declared-not-resolved.md"
 ],
 "deviations": [
  "Zone 2.4 premise falsified. WIDGET_CHART_STRUCTURE_RETIRED is a module-private (key, carried, instead) message builder in the installed spec: absent from the @objectstack/spec/ui export list and from every .d.ts. Nothing can be imported from it. The four members are typed per key from the exported SpecDashboardWidget chartConfig type, the same route PR 11310 used for aria, with no local list and no local never.",
  "Zone 2.3: mergeAuthoredPresentation had exactly one production caller (DatasetWidget). The react ObjectChart tier never called it: ObjectChart hands its own series/xAxis/yAxis to ChartRenderer/normalizeChartSchema. So no switch was needed. The dashboard call was removed and the function kept its signature, with no second copy. It was not deleted: deletion would rewrite plugin-charts ChartRenderer.axisTitleLocale-10132.test.tsx (outside the file surface), and the claim's Clause-2 treats the export as staying. Reported as a follow-up in out_of_scope_findings.",
  "Edits beyond the literal file surface, each declared: (a) one header sentence in packages/types/src/__tests__/chartconfig-aria-retired-4044.test.ts (\"every other chartConfig key keeps its old TypeScript typing\"), made false by this change; (b) two pending changesets made false by this change, corrected per Zone 3: 4044-chartconfig-aria-tombstone.md (same sentence) and 10132-dashboard-i18n-declared-not-resolved.md (its axis-title point no longer reaches a dashboard; its series-label aside named DatasetWidget). check-changeset-overwrite reports both; it is report-only.",
  "DatasetWidget's module-local re-export of mergeAuthoredPresentation, AuthoredSeriesPresentation and MergedChartSeries was removed. No importer used it, and the package index never exported DatasetWidget, so the published surface is unchanged.",
  "Fixture triage in DatasetWidget.chartConfig.test.tsx: the incidental chartConfig.type (a retired key on this carrier) was dropped from the LOWERED-block fixtures. Those cases are not about it, and the widget never read it.",
  "The plugin-charts control was strengthened after ablation 3 showed its explicit-combo case was vacuous: the positional default drew the same counts. The case now authors an area plus a line. Committed before the re-run.",
  "The downstream type-check sweep was narrowed. app-shell and examples/schema-catalog were not type-checked locally (their closure is unbuilt) and are declared to CI. The other three consumers were type-checked.",
  "@object-ui/core is declared with an empty-frontmatter changeset (comments only, behaviour unchanged). The rendering break is declared in @object-ui/plugin-dashboard (minor). The claim's Clause-2 wording put that break on core's export; the export is unchanged, and the break lives in the dashboard caller."
 ],
 "open_questions": [],
 "out_of_scope_findings": [
  "carrier: none · noted, not filed — @object-ui/core mergeAuthoredPresentation and axisPresentation are published exports with zero production callers after this change (the dead-code class). Deleting both, and re-homing ChartRenderer.axisTitleLocale-10132.test.tsx onto a chart node that authors its own axes, is the follow-up. The core chart-presentation.axisTitleI18n-10132.test.ts cases on them would go with it. Dedupe words: mergeAuthoredPresentation dead export · axisPresentation no caller · chart-presentation retire merge",
  "carrier: none · noted, not filed — comments this change makes stale, outside the file surface: packages/types/src/zod/data-display.zod.ts (\"DatasetWidget -> mergeAuthoredPresentation\"); packages/plugin-report/src/DatasetReportRenderer.tsx (two places say the dashboard makes the same series merge); core chart-presentation.axisTitleI18n-10132.test.ts (\"mergeAuthoredPresentation is what DatasetWidget calls\"); plugin-charts ChartRenderer.axisTitleLocale-10132.test.tsx (\"the path a dataset-bound surface actually takes\"); content/docs/plugins/plugin-charts.mdx (\"the ChartAxis a dashboard widget's chartConfig uses\").",
  "carrier: none · noted, not filed — comments stale since 17.5.0 and untouched (not in files this PR edits): DashboardRenderer.tsx inline relay (\"declared as the spec's full ChartConfigSchema\"; objectstack#17385 described as open); DashboardChart.chartConfig-4044.test.tsx (\"objectstack#17385 owns the precedence ... Until it answers\"); DatasetWidget.chartConfig.dom.test.tsx (\"pending objectstack#5175\"); the pending changeset dashboard-inline-chartconfig-4044.md (same ChartConfigSchema / objectstack#17385 claims).",
  "carrier: none · noted, not filed — a dashboard combo widget with compareTo: every series, overlays included, now takes the combo's positional mark, so an overlay can draw in a different mark from its own measure. That was already true for any combo that authored no series before this change. It is the spec's ruled cost of the retirement; no public-entry reading was taken."
 ]
}

---

Generated by Claude Code