finding(types,plugin-charts): ObjectChartSchema anchors nothing — ObjectChart is published as `props: any`, and four keys its own producers write are declared on neither copy

[claude]

Found while implementing objectui#7891 (removing ObjectView's undeclared chart.config
forward). Filed rather than folded into that PR: it is the MECHANISM that made #7891's
defect invisible, it lives in packages/types/ and packages/plugin-charts/ — both
outside that card's file surface — and acting on it is a design decision, not a rung.

What is measured, on origin/main f5d2acc

ObjectChartSchema exists twice and is exported from both — the TS interface
(packages/types/src/objectql.ts:2840) and the zod schema
(packages/types/src/zod/objectql.zod.ts:939). Neither anchors anything, for two
independent reasons.

1. The component they describe takes props: any.

packages/plugin-charts/src/ObjectChart.tsx:275
export const ObjectChart = (props: any) => {

and the published .d.ts carries that through verbatim:

packages/plugin-charts/dist/ObjectChart.d.ts:58
export declare const ObjectChart: (props: any) => React.JSX.Element;

So every schema={{ … }} literal handed to ObjectChart is type-checked against
nothing at all. MEASURED: removing both as any casts from the two object-chart
literals in packages/app-shell/src/views/ObjectView.tsx leaves tsc --noEmit GREEN,
over a program --listFiles confirms contains that file. The casts were inert; they read
as load-bearing and were not. That is why #7891's undeclared config rung survived from
the day it was written until someone read the spec by hand.

2. Four keys the producers actually write are declared on neither copy.

ObjectView's two object-chart literals write, between them, xAxisKey, series,
aggregate and filter. None of the four appears on the TS interface or the zod schema.
They are not dead either — packages/plugin-charts/src/ChartRenderer.tsx:132-134 reads
schema.series and schema.xAxisKey by name. The zod copy sits on BaseSchema, which is
.passthrough(), so they arrive and are read while their VALUES go unchecked.

3. A drift between the two copies, in passing. The zod schema declares colors (the
overloaded positional-palette / value-map union); the TS interface does not.

Why this is worth a card

objectui#6576's 2026-08-31 ruling (option A) anchored ObjectGallerySchema to
ObjectGalleryProps.schema precisely so a published widget schema would stop being a
document nothing reads, and pinned the read census in
__tests__/widget-schema-anchors-6576.test.ts. ObjectChart was not given that
treatment. ObjectChartSchema is what #6576 called the before-state: a published shape
with no prop type bound to it.

It is also the OTHER DIRECTION from objectui#7559. That card owns the input side — a
missing rung is invisible because viewDef is an untyped record. This is the output side:
an EXTRA, undeclared rung is invisible because the consuming component's props are any.
Same silence, opposite sign, different seam. It is likewise not objectui#7690, which is
about the SDUI ChartSchema's axis-config object dialect — a different schema and a
different key set.

What is NOT decided

Do not open with "declare the four keys". ADR-0049 is enforce-or-remove and both arms are
live per key: series and xAxisKey have real read sites, but whether they are AUTHORABLE
on an object-chart node — as opposed to internal keys the relay computes, which is what
series: vals.map(...) looks like — is exactly the question objectui#7891 turned out to
hinge on. A liveness read per key, with lit controls, comes first. Anchoring the prop type
(#6576's option A) and declaring the keys are separable decisions and may want separate
cards.

Repo: objectstack-ai/objectui. Related: objectui#7891, objectui#6576, objectui#7559,
objectui#7690.

---

Generated by Claude Code

[claude]

PM 分级（domain:ui lane 席）：domain:ui · package: types · package: plugin-charts · priority:p2 · pm:awaiting-maintainer

⛔ 本车道不派这张卡，理由是 Clause-②，不是优先级：

• 把 ObjectChart 的 (props: any) 换成一个真类型，会收窄一个已发布组件的接受面；
• 给已发布的 ObjectChartSchema（TS 与 zod 两份）补声明 xAxisKey / series / aggregate / filter，会扩大公开面；
• 两份拷贝之间 colors 的漂移要收敛，同样落在已发布形状上。

三条都是 Clause-② yes ⇒ 按本会话的常设约束转人工/总监席，agent 席位不裁。

⭐ 先例已经存在，接手的人不必重新推导

objectui#6576 在 2026-08-31 的裁定（option A）正是为这件事定的形状：把 ObjectGallerySchema 锚到 ObjectGalleryProps.schema，好让一个已发布的 widget schema 不再是「无人读的文档」，并把读取普查钉进 __tests__/widget-schema-anchors-6576.test.ts。ObjectChart 没有得到同样处理，所以本卡描述的就是 objectui#6576 所称的 before-state。

⇒ 这不是一个开放的设计题，更像是把一条已有裁定应用到第二个组件上。但它仍然是 Clause-② yes，所以仍然不由本车道下手。

⭐ 为什么这张卡比它看起来重要

它是 objectui#7891 那个缺陷得以隐形的机制，而不是同类的第二个实例：因为 ObjectChart 收 props: any，交给它的每一个 schema={{ … }} 字面量都在对空气做类型检查。objectui#7891 那两个 as any 读起来像是承重的，实测是惰性的 —— 两个全删后 tsc --noEmit 仍绿（program 经 --listFiles 确认含该文件）。

⇒ 那条未声明的 config 之所以从写下的那天活到今天，不是因为没人看，是因为没有任何仪器在那一层看。修 objectui#7891 关掉了那一个实例；本卡关的是让下一个实例同样隐形的机制。

与已 landed 的 objectui#7891 的关系

objectui#7891 / PR objectui#7948 只删了 ObjectView 上那两处未声明的 chart.config 转发，⛔ 没有给任何已发布 schema 加键、没有在 ListView 补档、没有跨仓改动 —— 边界正确，本卡是它明确留下的那一半。

---

Generated by Claude Code

[huangyiirene]

状态转换：pm:awaiting-maintainer → needs-user-decision（2026-09-09）

维护者回批逐字：「B 桶 · 要你的判断，应转 needs-user-decision —— 23 张 转决策卡」。

判据：欠判断不是动作 —— 公开类型契约。ObjectChartSchema 什么都没锚住：ObjectChart 以 props: any 发布，而它自己的生产者写的四个键在两份拷贝上都没声明。补声明是公开类型契约的收紧（今天 any 让任何读法都编译通过），⇒ 属 clause-② 面，恒交维护者。

按 objectstack SKILL.md:110/:126：决定待做 = needs-user-decision。⇒ 此前为误分类。

同笔摘 pm:awaiting-maintainer；domain:ui、package: types、package: plugin-charts、finding、priority:p2 留下。

⚠️ 根因见 objectstack #17017。

---

Generated by Claude Code

[os-bill]

维护者速读

事情:图表组件 ObjectChart 对外发布的签名是 props: any,而它的 schema(ObjectChartSchema,TS 与 zod 两份)什么都没锚住:生产者实际写的四个键(xAxisKey、series、aggregate、filter)两份都没声明,渲染器却按名读它们;两份拷贝之间 colors 还有漂移。实测:把 ObjectView 里两处 as any 去掉,tsc 照样绿——类型检查等于没有。这正是 #7891 那个未声明键能潜伏到有人手读 spec 才被发现的机制。

选项:A(推荐) 照 objectui#6576 对 gallery 的做法:把 ObjectChartSchema 锚到 ObjectChart 的 props 类型,声明生产者写的四个键(值类型按渲染器读法收紧,不从字面量抄),两份拷贝的 colors 收敛,加读普查 pin。B 保持 any。C 只声明四个键、不锚 props——声明了仍没有人检查。

你要做的:回一个字母,A / B / C。

• ① 项目长远合理性:A 让「已发布 widget schema 必须锚到 props」在 chart 上也成立(finding(types): two widget prop types declare their schema as a hand-rolled inline object with no BaseSchema in its ancestry #6576 已定的形状),缩小特例;B 让一份已发布 schema 永久是无人读的文档。
• ② 实际业务拉动:ObjectView 两处字面量在写、ChartRenderer 在读这四个键——不是投机面。
• ③ 防 AI 犯错:今天 AI 写错键 tsc 绿、运行时静默;A 后编译期响亮拒绝。
• ④ 创业阶段不扩散:A 不加能力,只把已存在的读写声明出来;C 半做。
  推荐 A(回退 C)。置信缺口:四个键的精确值类型需从渲染器读法推导,本席未逐键核。

裁后执行

• A ⇒ objectui domain:ui 回 pm:queue,finding 摘;Clause-②: yes(已发布类型契约从 any 收紧 + 声明面加键),契约复审档复核,changeset minor。
• B ⇒ 关 not planned。
• C ⇒ 同 A 的派发令去掉锚 props 一项。

总监席第 20 场(session_01Tep4AYXZvyBA7jsvne5KZV)按决策箱勤务补齐速读与四棱块,2026-09-09T05:3xZ;⛔ 非裁决。

---

Generated by Claude Code

[os-bill]

Ruling recorded — A: anchor ObjectChartSchema to ObjectChart's props and declare the keys its producers write (director seat, summon #20, decision batch #108 item 3, 2026-09-09T05:4xZ)

Provenance (who / verbatim / where): maintainer, live PM chat with this seat (session_01Tep4AYXZvyBA7jsvne5KZV, os-bill), 2026-09-09T05:4xZ, replying to batch #108 in which this card was item 3 with the 速读 and four-facet block at 5596356234 recommending A. Reply, verbatim: 「7424 查 「什么在飞」 就应该查open的呀，直接关闭。 其他同意。」 — item 3 = A.

Ruled. As objectui#6576 did for the gallery: ObjectChart's props are typed by ObjectChartSchema (no props: any on the published .d.ts); the four keys the producers write and the renderer reads — xAxisKey, series, aggregate, filter — are declared on both copies (TS interface and zod), with value types derived from ChartRenderer's reads, ⛔ not copied from ObjectView's literals; the two copies' colors drift converges; a read-census pin in the widget-schema-anchors family covers the chart. B (keep any) and C (declare without anchoring) refused.

Execution. Card → pm:queue in domain:ui in one write; finding dropped (graded). Dispatch shape: Clause-②: yes (a published type contract narrows from any and its declared face gains keys) — carrier on card and PR, CONTRACT_REVIEW_TIER review before enqueue; changeset @object-ui/types + @object-ui/plugin-charts minor; the inert as any casts in ObjectView are removed in the same PR so the anchor is measured, not asserted.

---

Generated by Claude Code