finding: `object-grid.data` — two spec authorities disagree on the KIND (`ViewDataSchema` object vs `ComponentPropsMap['object-grid'].data` array), so whichever the declaration matches, the other refuses it

[yinlianghui-tw]

Found while implementing #4971 (the declared-arm ⊆ spec-accepted gate). Filed unassigned, not claiming. Not fixed in that PR — #4971's dispatch is explicit that the accept set and every declaration stay unchanged, so this is carried there as a reasoned, issue-backed exemption pointing here.

Two entries of the same contract, opposite kinds

Both are @objectstack/spec@17.2.0, both describe object-grid's data:

spec authority	kind	its own description
ViewDataSchema — what ObjectGridSchema.data?: ViewData (packages/types/src/objectql.ts:556) resolves to	object, discriminated on provider (object / api / value / schema), each arm strict	inline rows live at { provider: 'value', items: [...] }
ComponentPropsMap['object-grid'].data	array (z.array(z.unknown()).optional())	'Static inline rows — bypasses the object query'

Measured on the installed pin:

ComponentPropsMap['object-grid'].safeParse({ data: [{ id: 1 }] }) → success
ComponentPropsMap['object-grid'].safeParse({ data: { provider: 'value', items: [] } })
 → [{"expected":"array","code":"invalid_type","path":["data"],
 "message":"Invalid input: expected array, received object"}]

The declaration (plugin-grid/src/index.tsx:225, type: 'object') matches the first authority — deliberately, and it is pinned there: #5090 / PR #5108 changed it from 'array' to 'object' against ViewDataSchema's own verdicts, and packages/plugin-grid/src/__tests__/gridDataInputContract.test.ts holds it. So it is the ComponentPropsMap entry that now refuses the published arm.

Why this is not a re-file of #5090

#5090 was declaration-vs-contract with ONE contract. This is contract-vs-contract: the fix #5090 landed is what makes the second authority's disagreement visible, and no change to the declaration can satisfy both — 'object' is refused by ComponentPropsMap, 'array' is refused by ViewDataSchema and by tsc (TS2322, measured on #5090). Flipping the declaration back would re-open #5090 exactly.

Why it matters

ComponentPropsMap is the authority the repo-wide parity gates read (apps/console/src/__tests__/registry-inputs-spec-parity.test.ts — both key-name directions and, since #4971, the arm direction). While the two disagree, one of them is teaching authors a shape the other refuses, and the gate that would notice has to be told to look away on this key.

Resolution is upstream, not here

This repo does not edit @objectstack/spec (AGENTS.md #0 / #0.1) — the two entries have to converge on one kind upstream. The likely shape (not a decision this card can take): ComponentPropsMap['object-grid'].data becomes ViewDataSchema, which is what ObjectGridSchema already resolves to and what the designer publishes; the array form is the deprecated staticData shortcut the #4648 carve-out already refuses to publish.

How to re-derive

sed -n '225p' packages/plugin-grid/src/index.tsx
grep -n 'data?: ViewData' packages/types/src/objectql.ts
pnpm exec vitest run apps/console/src/__tests__/registry-inputs-spec-parity.test.ts # the #4971 arm gate; entry `object-grid.data:object`
pnpm exec vitest run packages/plugin-grid/src/__tests__/gridDataInputContract.test.ts # the #5090 pin, against ViewDataSchema

Deleting the exemption entry in registry-inputs-spec-parity.test.ts is what closes this card — the gate's stale-exemption test demands it the moment the two authorities converge.

[claude]

Triage: → needs-user-decision + domain:spec — contract-vs-contract inside @objectstack/spec itself: ViewDataSchema (object, provider-discriminated; the authority #5090 ruled and pinned the declaration against) versus ComponentPropsMap['object-grid'].data (bare array, described as 'static inline rows — bypasses the object query'). Not a re-file of #5090, and not blanket-inheritable from it either: the props-map entry's own describe-text suggests a deliberate second semantic, so this is a decision, not a queue card. Type: Bug.

① 项目长远合理性:同一个键在同一份 spec 里两种 KIND 是最贵的契约债 —— 谁消费 ComponentPropsMap 谁就拒绝已 pin 的合法行为;收敛到 ViewDataSchema(#5090 已裁的权威)是缩小特例。
② 实际业务拉动:实测 { provider:'value', items:[…] }(pinned 合法形)被 ComponentPropsMap 拒绝 —— 任何走 props-map 校验的工具链(sdui-parser / os validate)会把合法页面判红。
③ 防 AI 犯错:两个权威并存时,AI 修代码必然「修向离它最近的那个」,而且两个方向都有测试可绿 —— 单一权威 + 删 #4971 豁免条目才封死这条错路。
④ 创业阶段不扩散:若「裸数组 = 静默直通 inline rows」真有独立用途,也应显式并入 ViewDataSchema 的 value 臂,而不是留第二个 KIND;默认收敛、不新增。
推荐:A = ComponentPropsMap['object-grid'].data 对齐 ViewDataSchema(object),沿 #5090 权威;B = 保留 array 并在 ViewDataSchema 增 array 臂(需真实拉动证据)。回一个字母即可。
置信缺口:未盘点 array 形今天是否有真实消费方(生成物/模板里写裸数组 data 的页面);有则 A 需带迁移面。

---

Generated by Claude Code

[os-steve]

Maintainer ruling (2026-08-25, batch adjudication, batch 4; verbatim: 「同意」): Option A — ComponentPropsMap['object-grid'].data converges onto ViewDataSchema (the #5090-ruled, pinned authority); the bare-array form is the deprecated shortcut the #4648 carve-out already refuses to publish. Migration check (bare-array authors in generated artifacts/templates) rides the upstream change.

Execution is upstream in @objectstack/spec — filed as objectstack-ai/objectstack#12039 (family-folded with ui#6206's key, spec lane queue, Clause-② yes).

Blocked-by: objectstack-ai/objectstack#12039

Unlock criterion (cross-repo, consumer-installable): a released spec version carrying the convergence reaches this repo's installed pin — not merely the upstream merge. On unlock, this card's close is exactly the #4971 stale-exemption deletion: remove object-grid.data:object from registry-inputs-spec-parity.test.ts and let the gate verify convergence. State transition: needs-user-decision → pm:blocked.

---

Generated by Claude Code