`data-table` accepts a `bind` and silently renders its header over an empty body

[os-support-ai]

Found while censusing bind producers and consumers for #6357 (PR #6574). Not that card's defect — filed separately per its dispatch.

The fact

bind is the data-scope binding vocabulary: a path string resolved by useDataScope(). Ten production sites read it. data-table is not one of them — it reads its rows from an inline data array on the node and never calls the hook.

So a bind on a data-table node is accepted by every gate and does nothing:

• the TS side accepts it (BaseSchema's [key: string]: any);
• the zod side accepts it (BaseSchema is .passthrough(), and DataTableSchema is BaseSchema.extend(…), which inherits that);
• nothing reads it at render.

The result is a table that draws its header over an empty body — no error, no warning, no diagnostic.

This is already documented and already pinned — it just has no card

• skills/objectui/rules/protocol.md:162 states it verbatim: "data-table does NOT: it reads its rows from an inline data array on the node, so a bind on it is ignored and the table renders its header over an empty body — no error, no warning."
• packages/components/src/__tests__/skill-guide-data-table-binding.test.tsx pins the behaviour, including the measured detail that "the bound array never reaches the renderer at all" — the body is one row, the empty state spanning the table.

So the behaviour is known and asserted. What is missing is a decision about whether it should stay.

Why declaring bind centrally did not change this

PR #6574 declares bind on BaseSchema (the #6357 census concluded it belongs there). That does not touch this: the key was accepted on every node before the declaration existed, via the index signature and .passthrough(). The declaration narrows the key's value to a string; it cannot refuse the key on a node that ignores it. Recording that explicitly so this is not read as a regression from that PR.

What needs deciding

Three shapes, not obviously one answer:

1. Make data-table a reader — call useDataScope(schema.bind) like the other nine. Consistent with the vocabulary the protocol teaches, but it is a behaviour change on a published component: a node carrying both data and bind would need a stated precedence.
2. Reject it loudly — refuse bind on data-table at parse time. Blocked on the same ceiling as everything else in this class: .passthrough() means a per-node strict shape is needed first (finding(types): BaseSchema's [key: string]: any leaves every component schema open, so a "declare the surface" fix can never reject a misspelled TOP-LEVEL key #5155 / finding(types): ObjectViewSchema's table and form slots declare ZERO properties — the same Omit-under-index-signature collapse as #6151, in property position #6269).
3. Diagnose it at render — the repo already has a diagnostic channel for exactly this shape of silent failure (packages/plugin-grid's column-spelling diagnostic, visibilityDiagnostic.ts).

Leaning 3 then 1, but this is a published-surface behaviour question rather than a mechanical fix, which is why this is a finding and not a patch.

Reproduce

grep -rn "useDataScope" packages --include='*.tsx' --include='*.ts' | grep -v __tests__
grep -rn "useDataScope" packages/components/src/renderers/data-display/data-table.tsx   # no hits
sed -n '160,166p' skills/objectui/rules/protocol.md

Refs: #6357, PR #6574. Adjacent ceiling: #5155 / #6269.

[os-support-ai]

Triage: routed — needs-user-decision + domain:ui, type Feature. This is a published-component behaviour question (whether data-table should honour, refuse, or diagnose bind), which sits on the manual floor — the card itself says it is a decision, not a patch. Decision analysis below in Chinese per convention; the facet block marker is written in literal spelling for the sanitizer.

os-decision-facets

一句话问题:页面作者给数据表写了数据绑定,预览出来表格只有表头、一行数据都没有,也没有任何提示 —— 作者以为是自己数据的问题,其实是这个表格根本不认「绑定」这个词,而平台的技能文档已经在教用户绕这个坑,等于把缺陷当使用说明卖。

选项 × 真实代价 × 业务直译:

• A. 渲染时诊断(复用 plugin-grid 现成的诊断通道):作者写错当场看到「data-table 不读 bind,请用 data」。业务上 = 把「文档里的坑」变成「界面上的提示」。代价:不修根因,表格依旧不认绑定;几行代码,不改任何已发布行为。
• B. 让 data-table 认 bind(和其它九个组件同词表):业务上 = 作者学一个词表就够,像表单、列表一样绑数据。代价:已发布组件的行为变化 —— 现有应用里同时写了 data 和 bind 的页面会变样,必须先裁「两个都给时听谁的」。
• C. 响亮拒收:今天做不了 —— 被 .passthrough() 天花板挡着(finding(types): BaseSchema's [key: string]: any leaves every component schema open, so a "declare the surface" fix can never reject a misspelled TOP-LEVEL key #5155/finding(types): ObjectViewSchema's table and form slots declare ZERO properties — the same Omit-under-index-signature collapse as #6151, in property position #6269 先行),不是本卡的可选项。
• D. 维持现状(只靠技能文档教绕):零成本,但每个新作者/每次 AI 生成都要再撞一次。

四棱:

• ① 项目长远合理性:A 不扩契约不加特例;B 才是词表真正统一的终态,但它是产品方向,可在 A 落地后单独裁 —— A 不堵 B 的路。
• ② 实际业务拉动:实测有 —— skills/objectui/rules/protocol.md:162 专门写了这个坑、还有 pin 测试锁着这个行为,平台已经在为它付教学成本,说明真实作者真的撞。
• ③ 防 AI 犯错:AI 生成页面最容易写出「带 bind 的 data-table」——今天无错无警,空表静默上线;A 让出错时作者与 AI 当场看到具名提示,响亮优于静默。
• ④ 创业阶段不扩散:A 复用既有诊断通道,近零增量;B 是行为扩张且带优先级新决定,defer 不亏。

推荐 A(诊断先行),回退 B(若裁词表统一优先,则同笔裁定 data 与 bind 并存时的优先级)。置信缺口:本分析未 census 生产应用里有多少 data-table 节点真带着 bind(拉动强度未量化);也看不见 PR #6574 把 bind 声明进 BaseSchema 之后作者预期是否会向「处处可绑」漂移(那会加重 D 的静默代价)。

裁后执行:裁 A ⇒ 转 pm:queue,派发词点名 visibilityDiagnostic.ts 先例与 pin 测试同步更新;裁 B ⇒ 需另立 data/bind 优先级裁决后再入队;裁 D ⇒ 关 not planned,重开免费。

---

Generated by Claude Code

[os-zhuang]

Maintainer ruling recorded — Option A: diagnose at render; the vocabulary question stays open for a later ruling

Provenance: maintainer, 2026-08-27, PM chat decision-inbox batch 3 (adjudication session session_01DKWDdUJ2XNRESVVWUvcpnh), verbatim: 「同意」 — accepting the triage recommendation A (2026-08-26T14:11Z facet block).

Ruled: data-table receiving a bind gets a loud render-time diagnostic ("data-table does not read bind; it reads its rows from the inline data array"), reusing the existing diagnostic-channel precedent (packages/plugin-grid's visibilityDiagnostic.ts). No behaviour change to the published component; the trap stops being silent.

Dispatch notes: update the pin (packages/components/src/__tests__/skill-guide-data-table-binding.test.tsx) to assert the diagnostic alongside the existing behaviour, and refresh skills/objectui/rules/protocol.md:162 to mention the diagnostic (the skills/** net-line budget applies). ⛔ Option B (making data-table a useDataScope reader) is NOT part of this card — if vocabulary unification is wanted later it needs its own ruling, including data-vs-bind precedence. Option C stays blocked on the .passthrough() ceiling (#5155/#6269).

State: needs-user-decision → pm:queue.

---

Generated by Claude Code