The adapter-only `data.*` diagnostic (#5687) covers the visibility gate only — the same constant predicate on `disabled` greys a control out in silence

[os-support-ai]

Found while wiring the disabled / disabledOn fault diagnostic (#6445). Filed unassigned — it is a second diagnostic with its own maintainer ruling and its own copy, not part of that card's wiring.

The gap

reportAdapterOnlyDataPredicate (packages/react/src/utils/visibilityDiagnostic.ts, #5687, ruling 2026-08-22 option A) reports a predicate that evaluated perfectly against the wrong object: at the node tier data is the data-source adapter, not the row, so data.status == 'draft' is a CONSTANT for every row. It is called from evaluateVisibilityPredicate's dev leg only.

The disabled / disabledOn gate — now wired for faults by #6445 — is not covered by it. A node written

{ "type": "button", "disabled": "data.status == 'locked'" }

evaluates cleanly (no fault, so #6445's reporter correctly stays silent), resolves undefined == 'locked' to false… and on the other value of that constant (data.locked == null, !data.assignee, or an adapter that answers nothing) hands the gate a constant true that greys the control out on every row, in every build, with nothing on the console.

Why it was not folded into #6445

Two reasons, both about the message rather than the wiring:

1. Its ruling is scoped to visibility. The 2026-08-22 option A ruling names the visibility gate; extending a dev-only diagnostic to a second gate is a decision, not an implementation detail.
2. Its copy is visibility copy. formatAdapterOnlyDataMessage says "on this surface a constant false hides the node on every row while looking exactly like a gate that said no" — the wrong sentence for a gate whose constant disables rather than hides, and the same asymmetry The disabled / disabledOn node gate has NO fault diagnostic in either build — and its fail-soft polarity greys a control out rather than showing it #6445 had to write new copy for.

So it needs a copy decision of the same kind #6445 made (its GATE_KIND_COPY table is the obvious place, and the module now has the machinery), plus a ruling on whether the extension stays dev-only as #5687 is.

Note on the deprecation clock

#5687's own docblock says this diagnostic "dissolves when #5330's deprecation window closes" (data.* as a spelling for the row). If that window is close, the right answer may be to do nothing here — worth stating explicitly rather than leaving the asymmetry undocumented, which is why this is filed rather than fixed.

Related: #5687 (the leg), #5330 (the deprecation), #6445 (the disabled fault diagnostic that exposed the gap).

[os-support-ai]

Triage (triage seat, hourly round 2026-08-26, session session_01DoScS7Ei3iWc39AgGN36wU): graded needs-user-decision + domain:ui, type Task. Rationale: the card asks to extend a diagnostic whose existing scope is a recorded maintainer ruling (2026-08-22 option A, #5687, named the visibility gate only) to a second gate — extending a ruled scope is a decision, and the card's own deprecation-clock note (#5687 dissolves when #5330's window closes) means "do nothing" is a live option, not negligence. Filing into the decision box rather than the queue.

os-decision-facets

• 实际业务拉动:症状真实且完全静默 —— 一个 adapter-only 常量谓词把控件在每一行、每个构建里灰掉,console 一个字都不说;但发生率未测,且这是 dev-only 诊断面,不影响运行行为。
• 项目长远合理性: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 #5687 自述随 [Decision] Row-predicate spelling contract: does the canon narrow to record.*, or do the bare shorthand and data.* spellings stay? (the uncarried "#4075 step 3" question) #5330 的 data.* 废弃窗口关闭而消解 —— 给一个将死拼写加第二条诊断,是对旧世界的投资;窗口远则值得,近则浪费。裁决应先看窗口时间表。
• 防 AI 犯错:常量谓词「完美求值于错误对象」正是 AI 写元数据 app 批量犯错被掩盖的形状;把它响亮化方向正确,且 The disabled / disabledOn node gate has NO fault diagnostic in either build — and its fail-soft polarity greys a control out rather than showing it #6445 已备好 GATE_KIND_COPY 机制,扩展成本是一条表项 + 一段 copy。
• 创业阶段不扩散:dev-only 诊断扩一个 gate 面很小,但每一次扩展都是 [Decision] Row-predicate spelling contract: does the canon narrow to record.*, or do the bare shorthand and data.* spellings stay? (the uncarried "#4075 step 3" question) #5330 收尾时要拆走的新义务;不扩(B)是零成本选项。
• 选项与推荐:A — 扩到 disabled gate,新 copy 进 GATE_KIND_COPY,保持 dev-only(推荐,条件:[Decision] Row-predicate spelling contract: does the canon narrow to record.*, or do the bare shorthand and data.* spellings stay? (the uncarried "#4075 step 3" question) #5330 废弃窗口不在近期关闭);B — 不扩,记录不对称,等窗口关闭一并消解(若窗口近,推荐 B);C — 扩且转 always-on(⛔ 超出 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 #5687 先例,不推荐)。
• 置信缺口:[Decision] Row-predicate spelling contract: does the canon narrow to record.*, or do the bare shorthand and data.* spellings stay? (the uncarried "#4075 step 3" question) #5330 废弃窗口的时间表本分析未查(它是 A/B 之间的决定性事实);disabled 上 adapter-only 常量谓词的真实发生率未测。

---

Generated by Claude Code

[os-zhuang]

Maintainer ruling recorded — Option A: extend the constant-predicate diagnostic to the disabled gate, dev-only

Provenance: maintainer, 2026-08-27, PM chat decision-inbox batch 5 (adjudication session session_01DKWDdUJ2XNRESVVWUvcpnh), verbatim: 「同意」 — accepting recommendation A with its stated premise affirmed: the #5330 data.* deprecation window is not closing near-term.

Ruled: extend the adapter-only constant-predicate diagnostic (#5687, 2026-08-22 option A) to the disabled / disabledOn gate — dev-only, via #6445's GATE_KIND_COPY machinery, with gate-appropriate copy (the constant-true direction: "greys the control on every row while looking exactly like a gate that said no"). ⛔ C (always-on) stays excluded — outside the #5687 precedent.

Inheritance clause, binding: the extension inherits #5687's dissolution note verbatim — when #5330's deprecation window closes, both legs dissolve together; the new copy entry must carry the same pointer so the teardown finds it.

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

---

Generated by Claude Code