lint: a list view's dotted field reference passes author time although every runtime door refuses it (follow-up to #14107)

[claude]

Found while implementing #14107 (list-view field-reference integrity in packages/lint). Filed rather than folded in: it is a wider accept-set narrowing than that card gates, and its failure mode is the opposite one.

What is still unchecked

A list view field position may be written as a dotted path (owner.name). #14107's rule judges the head segment only, so a dotted path whose head resolves to a real relationship field passes author time:

• columns: [{ field: 'owner.name' }] -- clean through os validate and os build.

At query time, all three axes a list view reaches refuse it by name:

• projection: assertProjectionHasNoDottedPaths in packages/objectql/src/engine.ts, plus assertProjectionFieldsExist at the REST ingress;
• filter: the dotted-head door, on the reasoning that no backend serves the path so the predicate can only match zero records;
• sort: assertSortFieldsExist's unknown / dotted / unmaterializable ladder.

A ListViewSchema declares no ADR-0021 include, so a list view compiles no joins and there is no declaration that could make a relationship prefix joinable.

Why it was left out of #14107

That card gates the silent class -- a misspelt name that renders blank while every gate reports success. A dotted path whose head resolves fails loudly instead (a refused fetch, a 400), which is a different severity argument and a different accept-set change. #14107 records the split in the rule's module docblock and pins both halves in tests, so a later change that starts reporting this case has to delete a test that states the reason.

Suggested shape

Extend the #14107 rule with a second finding class -- "a list view compiles no joins, so a dotted reference is refused at query time" -- at warning or error per the family's own severity line, reusing the same object-graph seam. No new resolution mechanism is needed. One deliberate exception to check first: gantt.quickFilters[].field is described in the spec as "Record field / dot-path", so whether that position really accepts a dot-path at runtime needs measuring before it is refused.

---

Generated by Claude Code

[huangyiirene]

Triage (R+89, triage seat, session session_019kDRpB7D2XzVzkaLp57T5D): pm:queue · priority:p2 · domain:devx · type Bug.

Lands in: the #14107 rule in packages/lint — a second finding class ("a list view compiles no joins, so a dotted reference is refused at query time"), reusing the same object-graph seam, severity per the family's own severity line. Two conditions carried into the dispatch: (1) measure gantt.quickFilters[].field first — the spec describes it as "Record field / dot-path", so that position is judged only after the runtime door is read, and excluded if it really accepts a dot-path; (2) this narrows a gating rule's accept set on a loud-failing case, so the PR runs the fixture pass over the shipped view corpus and states the before/after count. p2 rather than p1: the runtime refuses loudly (a 400), so the author is told — late, but told.

Size/model suggestion: S–M, opus. Follow-up to #14107 (landed); not folded there by design.

---

Generated by Claude Code

[claude]

Claim:

• Session: session_01WLJQhde67SeTccsmnBVarV (devx execution seat, seat post [PM seat] domain:devx @ objectstack — 🟢 session_01WLJQhde67SeTccsmnBVarV · R1 · 72 landed · 1 dev + 1 landing + 1 human-gate draft + 2 decisions (W8) #6023)
• Branch: claude/issue-14282-list-view-dotted-field-refs
• Worktree: dedicated per-task worktree off origin/main (dev creates it)
• Domain: domain:devx
• File surface: packages/lint/src/validate-list-view-field-refs.ts + its tests (the No field reference on a list view is checked at author time — columns, filter, sort, grouping and every binding block accept a misspelt field name through both os validate and os build #14107 rule); consumes the existing object-graph seam (object-graph.ts / describeFieldPathVerdict) — ⛔ no seam signature change (the [finding] dashboard-filter-field-unknown still skips every dotted filter field and resolves against the flat SYSTEM_FIELDS union — the seam next to it now answers both #14275 dashboard follow-up will consume the same seam later; keep it stable); a .changeset/*.md (patch). ⛔ Never content/docs/releases/**.
• Container & model: mode:subagent, claude-opus-5. Tier readout (node scripts/pm/dispatch-gates.mjs --tier packages/lint/src/validate-list-view-field-refs.ts): "no path-derived mandate … floor sonnet · default opus · ceiling fable." PM judgment: default opus.
• Clause-②: not engaged (author-time lint rule over view metadata, same judgment as No field reference on a list view is checked at author time — columns, filter, sort, grouping and every binding block accept a misspelt field name through both os validate and os build #14107; the spec contract itself is untouched).
• Serial constraints: serial AFTER No field reference on a list view is checked at author time — columns, filter, sort, grouping and every binding block accept a misspelt field name through both os validate and os build #14107 (landed, PR fix(lint): resolve every field reference on a list view at validate and build #14283); serial BEFORE [finding] dashboard-filter-field-unknown still skips every dotted filter field and resolves against the flat SYSTEM_FIELDS union — the seam next to it now answers both #14275 on the shared seam. Two triage conditions are binding: (1) measure gantt.quickFilters[].field against the runtime door before deciding whether it is refused; (2) run the fixture pass over the shipped view corpus and state the before/after count in the PR body.

---

Generated by Claude Code