SchemaRenderer's node visibility gate resolves a `data.*` predicate against the data-source ADAPTER, so a hoisted `properties.visible` written that way hides the block on every row, silently

[os-sales]

Where this came from

Found while implementing #4807 (row binding for record:alert's own properties.visible). It is one tier up from that card and was deliberately left alone there. Duplicate search run before filing: keyword + symbol sweep over open issues (SchemaRenderer / node-level visible / data.* / adapter / #5330 follow-ups) found nothing.

Facts (read + measured on origin/main 3b147a3)

• packages/react/src/SchemaRenderer.tsx hoists every properties.* value onto the node, so properties.visible arrives at the node-visibility chain as schema.visible and is evaluated there.
• That chain's evaluator is built with data: dataSource — the data-source ADAPTER from SchemaRendererContext, defaulting to the module constant NO_DATA_SOURCE = {} when no provider is mounted. The docblock states this binding deliberately: data is what ${data.total} in a props bag resolves against, and the row must not overwrite it.
• Consequence: an author who writes properties: { visible: "data.status == 'draft'" } on any block gets data.status resolved against the adapter, not the row. It does not throw, so it reads as a real verdict: undefined == 'draft' is a constant false, and the block is hidden on every row.
• Silent in both senses. The dev-only "unresolvable predicate" reporter added by Component-level visibleWhen binds no record on record pages — every record.* predicate fails soft to permanently visible, on every block #5454 keys off a throw; this path never throws, so nothing is printed. And the failure direction is hidden-rather-than-shown, which looks like the author's gate working.

Why it is worth a card rather than a fix-in-place

#5330 ruled B (maintainer, 2026-08-20): canon is record.*, and the row-action shorthand plus legacy data.* are deprecated but kept behind a survey-sized window. usePredicateRecordContext implements exactly that at the useCondition tier. Whether the ruling's reach extends to the node tier is a genuine contract question rather than a mechanical fix, because at that tier data already means something else and something documented:

• binding the row over data there would change ${data.*} interpolation in props bags — the docblock calls that out as "a silent interpolation change nobody asked for";
• leaving it means one authored key (visible) answers differently depending on which tier consults it, which is what finding: record:alert 是唯一没接 #4075/#4077 行绑定的谓词面 —— 裸 { record } 作用域下 row-action 简写与 data.* 拼法 unbound,fail-soft 使作者门控的横幅永远显示 #4807's two-gate composition already makes hard to reason about;
• a third option is to make this case loud instead of changing any verdict — the same move Component-level visibleWhen binds no record on record pages — every record.* predicate fails soft to permanently visible, on every block #5454 made for the throwing paths — and let the deprecation window close on its own.

Reproduction

packages/plugin-detail/src/renderers/__tests__/record-alert.rowBinding.test.tsx (added by #4807) is the standing evidence: its data.* leg has to hold the node gate open with a declared visibleWhen: cel('true') before the row-tier binding is observable at all, and the file's header states why. Dropping that isolation is the reproduction — the block goes hidden on both rows.

Scope note

record:alert was fixed at its own tier by #4807 and is not affected by whatever is decided here for the canonical record.* spelling; only the deprecated data.* spelling is, and only through the node gate. This issue is filed unassigned for triage.

[os-sales]

Cross-reference — this finding is adjacent to #5401 / #5454, and the two must not be conflated.

This card records that SchemaRenderer's node visibility gate resolves data.* against the data-source adapter. #5401 was re-ruled on 2026-08-22 to option B — bind record into that same node-level evaluator so visibleWhen means what packages/spec/src/ui/page.zod.ts:189 advertises — and is now a child of umbrella #5454.

Same evaluator, two different unbound/misbound identifiers:

	resolves against	card
data.*	the data-source adapter	#5687 (this card)
record.*	not bound at node level	#5401 → #5454

Consequence for whoever picks either up: a sweep for one bucket will surface the other if it is written loosely, and the two have different correct fixes. #5401's survey (dispatched now, round 16, survey-only per the ruling's ordering constraint) is instructed to label each site by bucket for exactly this reason. Don't let a data.* site be counted as evidence for the record.* binding change, or vice versa.

---

Generated by Claude Code

[huangyiirene]

Concentration-round first-touch (triage seat): finding → decision inbox (needs-user-decision) — this is an instance the #5330 ruling (2026-08-20, option B) did not explicitly cover: at the node tier, data already means the adapter by documented design, so extending the row-binding there collides with a documented interpolation contract. That reach question belongs to the ruling's owner.

[facets-block]

• 实际业务需求:作者写 properties.visible: "data.status == 'draft'" 得到「所有行全部隐藏」且零信号——失败方向伪装成门在工作;但注意这只影响已废弃的 data.* 拼写,canon record.* 与 finding: record:alert 是唯一没接 #4075/#4077 行绑定的谓词面 —— 裸 { record } 作用域下 row-action 简写与 data.* 拼法 unbound,fail-soft 使作者门控的横幅永远显示 #4807 修好的行级门不受影响。
• 项目长远合理性:节点层 data = adapter 是写进 docblock 的既有契约(${data.total} 插值依赖它);②(把行绑定伸到节点层)正是 docblock 点名的「没人要求的静默插值变更」;①+响亮化让废弃窗口自然关闭。
• 防 AI 写代码犯错:废弃拼写在一个层生效、另一个层恒假,是最难教对的形状;响亮化(报告而非改判)把静默错误变成可见错误,不动任何契约。
• 创业阶段不扩散需求:①+loud 最小——一个检测点(节点门上的 data.* 谓词发 dev 报告),零语义变更;②要动两个已文档化契约。

一句话问题:#5330 的行绑定裁决是否延伸到节点可见性层(那里 data 已按文档指 adapter)——还是维持节点层语义、只把这条废弃拼写的恒假结果变响亮?

推荐 A = 维持节点层语义 + 响亮化(#5454 对 throw 路径的同款处理延伸到这条不 throw 的路径:节点门谓词引用 data. 且解析出 undefined 比较时发 dev-only 报告),置信度中高;废弃窗口(#5330 的 survey window)照原计划关闭时本卡随之消亡。本分析看不见什么:真实元数据里节点层 data.* 谓词的存量(#5330 的 survey 半径是否已覆盖节点层写法)。裁决格式:回「A」/「B」(B = 行绑定伸到节点层,含插值变更)。

---

Generated by Claude Code

[huangyiirene]

Maintainer ruling recorded — A: the node tier keeps its documented data = adapter semantics; the deprecated spelling's constant-false gets loud

Provenance: maintainer, 2026-08-22, live session with the triage seat (「同意所有」, item 16 = A).

State: needs-user-decision → pm:queue (ui seat). Scope: no verdict changes and no interpolation changes — the #5330 row binding does not extend to the node tier (the docblock's "silent interpolation change nobody asked for" stays refused); instead, extend the #5454 reporter posture to this non-throwing path: a node-gate predicate referencing data. that resolves an undefined comparison emits the dev-only unresolvable-predicate report, so the author sees the constant-false instead of shipping it. The card dissolves when #5330's deprecation window closes. Pin: the report fires on the card's reproduction shape; canonical record.* and genuine adapter reads (${data.total}) stay silent.

---

Generated by Claude Code