lint(devx): view/page 谓词(visibleWhen/visibleOn 等)的裸标识符构建期静态校验 —— #5149 裁决拆单

[hotlong]

按 #5149 维护者裁决(2026-08-06 08:29Z 裁决评论 + 10:39Z 半裁落地评论「诉求 3 拆 devx 另立单——已放行」)代立。本单未认领,标签交分诊(预判落点 packages/lint → devx 车道)。

要求(裁决原文口径)

把裸标识符解析校验扩到 view/page 的谓词表达式(visibleWhen / visibleOn 及同族):谓词里引用的标识符必须能在绑定约定下解析(值绑定在 record. / previous. 等命名空间下),裸字段名(如 status == 'active' 而非 record.status == 'active')在构建期报 error 级或 gating——坏谓词根本发不出去。

为什么现有两道闸都放行(#5149 Repro 1 实测)

• ADR-0032 的标识符闸不遍历 views;
• ADR-0089 D3b 只查别名/错根,不查裸标识符。

两闸之间正好漏掉「作者按文档示例写了裸字段名 → 谓词永远解析失败 → 控制台 fail-open 静默显示」这条链。运行时半边(每谓词 warn 一次)由 #5149 已放行诉求 2 落地中;本单是构建期半边,两半边独立可落。

验收建议

• Conditional-visibility predicates (visibleWhen / visibleOn) fail OPEN and silently — a broken predicate is indistinguishable from no predicate #5149 Repro 1 的谓词形状(裸字段名)在 lint 下必红;
• record. 前缀的正确写法必绿;
• 与 #4649 的「记录对已声明字段全量」只落在两个接缝上 —— 另外三处求值仍是稀疏绑定 #4953(服务端 CEL 全量 vs 稀疏绑定语义分叉)不合并——不同层,但实现时值得读它避免把「稀疏绑定下合法」的形状误杀。

Refs:#5149(来源单与裁决)、ADR-0032、ADR-0089 D3b、#4953(相邻非重复)。

[claude]

Triage: pm:queue + domain:devx.

Landing site (read, not guessed): packages/lint ⇒ domain:devx per the SKILL domain table. Anchored concretely — packages/lint/src/validate-visibility-predicates.ts is the file that already owns visibleOn / visibleWhen on the view/page surface (with its own test file next to it), and packages/lint/src/validate-expressions.ts is the bare-identifier machinery this ruling wants extended to it. Both are in packages/lint, one lane, no split needed.

Queued rather than escalated: the maintainer already ruled on 2026-08-06 (#5149, 08:29Z ruling + 10:39Z half-landing comment splitting requirement 3 out to devx). Nothing left to decide — the acceptance criteria in the body are statable in one sentence, so this is dispatchable as filed.

Dedup (three repos, open issues + open PRs): no duplicate. Adjacent, deliberately not converged:

• Conditional-visibility predicates (visibleWhen / visibleOn) fail OPEN and silently — a broken predicate is indistinguishable from no predicate #5149 (pm:queue, repo:objectui, target:v17) — the source issue; its requirement 2 (runtime warn-once) is the console half and lands in objectui. This issue is the build-time half in packages/lint. Different repos, independently landable, which is why the ruling split them.
• #4649 的「记录对已声明字段全量」只落在两个接缝上 —— 另外三处求值仍是稀疏绑定 #4953 — adjacent, not duplicate (server-side CEL vs sparse-binding semantics); the body already flags it as required reading so the new rule does not reject shapes that are legal under a sparse binding.
• lint object/missing-name-field 谓词不读 nameField,却仍采信 ADR-0079 已退役的 titleFormat——照平台自己的迁移建议做反而多得一条告警 #6108 (pm:queue) and packages/lint 绕过 @objectstack/formula 直接 parse CEL —— 两个解析入口对「什么能解析」会给出不同答案 #4812 (pm:dispatched, domain:engine-core) also touch packages/lint. packages/lint 绕过 @objectstack/formula 直接 parse CEL —— 两个解析入口对「什么能解析」会给出不同答案 #4812 is in flight and is about lint parsing CEL directly instead of going through @objectstack/formula — same package, and a bare-identifier resolution rule is exactly the kind of code that would sit on top of whichever parser wins. The executing lane should serialize this behind packages/lint 绕过 @objectstack/formula 直接 parse CEL —— 两个解析入口对「什么能解析」会给出不同答案 #4812 or confirm the file surfaces are disjoint before dispatching (SKILL step 3, same-package serialization).

本评论来自分诊座位 Routine(#5474 试点),不构成认领。

---

Generated by Claude Code