validate-functional-completeness walks only top-level views containers — object-nested list / listViews (ADR-0017) never reach the view completeness rules

[claude]

Measured on origin/main (a39b02a6) while implementing #14106, by running runAuthoringRules('validate', { normalized: normalizeStackInput(stack) }) — the exact path os validate takes (packages/cli/src/commands/validate.ts) — over the same two list views in the two authorable container shapes:

where the list views live	gantt view with no gantt: block
top-level views: [{ object: 'duly_task', listViews: { schedule: { type: 'gantt' } } }]	view/layout-without-binding at views[0].listViews.schedule.gantt (as designed)
object-nested objects: { duly_task: { …, listViews: { schedule: { type: 'gantt' } } } }	nothing — 0 findings

Why

packages/lint/src/validate-functional-completeness.ts walks objects[].fields for the field rules and only stack.views[] containers for the list-view rules. An object's built-in named list views (ObjectSchema.listViews, packages/spec/src/data/object.zod.ts — ADR-0017 nested "Object has-many View", ADR-0047 segmented tabs) and its default list slot are never handed to checkViewCompleteness. normalizeStackInput does not hoist them into stack.views either (views is not in MAP_SUPPORTED_FIELDS; the conversion layer does not move views), so on the normalized pre-parse stack the wrapper receives, object-nested list views are invisible to the whole view/* completeness family — view/layout-without-binding and, after #14106 lands, view/tree-without-parent-field.

The sibling reference-integrity rules already walk both doors: lint-view-refs.ts (containerFromObject) and validate-list-view-field-refs.ts (the objects[].listViews.* loop, resolving the object as data.object ?? obj.name). The completeness walk is the one member of the family that stopped at the top-level container, which is exactly the shape validate-functional-completeness.test.ts's own docblock warns about: "a completeness gate that walks half the stack is exactly that: green, and blind to the other half."

Expected

validateFunctionalCompleteness walks objects[].list and objects[].listViews.* through checkViewCompleteness with the object itself as the bound object (an inline data.object may retarget, per ADR-0047), reporting where as object "<name>" › listViews.<key> and path as objects[<i>].listViews.<key>.<block>, so an object-nested timeline / gantt / tree view authored without its binding gets the same warning the top-level container form gets today. A fixture pair in both spellings (map-form and array-form objects).

Scope note

Deliberately not folded into #14106 (that card is domain:spec, and its dispatch declared the lint edit as wiring only); this is a packages/lint walk defect and lands in the lint lane. #14106 remains open until its own PR merges; this issue does not depend on it.

---

Generated by Claude Code

[huangyiirene]

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

Lands in: packages/lint/src/validate-functional-completeness.ts — walk objects[].list and objects[].listViews.* through checkViewCompleteness with the object itself as the bound object (an inline data.object may retarget, per ADR-0047), reporting where / path in the object-nested spelling the card gives. The two sibling rules already walk both doors (lint-view-refs.ts's containerFromObject, validate-list-view-field-refs.ts's objects[].listViews.* loop) — this is the one family member that stopped at the top-level container, and its own test docblock names the failure: "a completeness gate that walks half the stack is exactly that: green, and blind to the other half." Fixture pair in both spellings (map-form and array-form objects) is part of the deliverable.

p2: an author using the ADR-0017 nested door — the door the object schema itself offers — gets no diagnostic at all for a gantt / timeline / tree view with no binding block, while the same view in the top-level container is flagged. Warning-severity family, so no gate strength moves.

⚠️ Serial with #14106 (pm:dispatched, spec seat): that card adds view/tree-without-parent-field to the same rule family and its dispatch declares the lint edit as wiring only. This card widens the walk those rules run on ⇒ land after #14106 merges and re-derive, so the new rule is carried through both doors by construction rather than by a second edit.

Size/model suggestion: S–M, opus.

---

Generated by Claude Code

[claude]

Claim: session session_01WLJQhde67SeTccsmnBVarV (domain:devx execution seat, seat post #6023) — R1 wave 7 (concurrency raised to 5 by the maintainer, 2026-09-02 「并发加到五」).

• Branch: claude/issue-14320-completeness-walk-object-nested-views
• Worktree: ../objectstack-14320 (dedicated per-task worktree, off origin/main)
• Domain: domain:devx (packages/lint)
• File surface: packages/lint/src/validate-functional-completeness.ts (the list-view walk at :103–139 on origin/main f35821044, re-verified just now: for (const [vi, container] of entriesOf(stack.views).entries()) at :124 is the only container loop; objects[].list / objects[].listViews.* are never handed to checkViewCompleteness) + validate-functional-completeness.test.ts (fixture pair in map-form and array-form object spellings). ⛔ lint-view-refs.ts / validate-list-view-field-refs.ts are READ as the sibling precedent (containerFromObject, the objects[].listViews.* loop), not edited.
• Serial constraint from triage 5503579454 discharged: view/layout-without-binding covers only 3 of the 6 view types that have a binding block — timeline, tree and map fall through the same trapdoor #14106 is CLOSED and its view/tree-without-parent-field rule is on origin/main (validate-functional-completeness.test.ts:98/:226), so the widened walk carries both binding rules through both doors by construction.
• Container & model: subagent lane (S–M), opus — triage suggested S–M / opus; tier readout from scripts/pm/dispatch-gates.mjs --tier packages/lint/src/validate-functional-completeness.ts: "no path-derived mandate — floor sonnet · default opus · ceiling fable".
• Clause ②: not reached — warning-severity author-time lint family, no gate strength moves, no contract accept/reject behaviour. Accept-set narrowing on a lint rule ⇒ the corpus before/after count over the shipped example apps (PR fix(lint): refuse dotted list-view field references at author time (#14282) #14368 precedent, mutated CONTROL) is required evidence.
• Serial constraints: [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 (in flight, same seat) holds validate-widget-bindings.ts only — disjoint; object-graph.ts free, not needed here.

---

Generated by Claude Code