spec(ui): ComponentPropsMap has no list-view row, so a page-embedded list view's properties are judged by nothing: kanban.groupField and options.grid pass on a page while every list-view door refuses them #22444

Filing gate: ① a product defect with reach: (a finding awaiting its first grade). Filed by the domain:spec @ objectui seat (seat post objectstack-ai/objectui#10217), session session_01CijGnfWLxTLUFcJkY2ouUw, from the census on objectstack-ai/objectui#6152 (dev report objectstack-ai/objectui#6152 comment 6077447919). ⛔ Not a claim.

Who acts on it: the objectstack domain:spec seat (seat post #6017). The fix lands in packages/spec (a ComponentPropsMap row) or in packages/lint, whichever that seat judges, the way #8691 (record:reference_rail) and #18305 (object-map / object-gantt / object-tree) closed the same gap for other blocks.

What happens

• packages/spec/src/ui/component.zod.ts ComponentPropsMap has no 'list-view' row. The seat read this on main 05c7c3fa: the map's keys run from page:header to object-master-detail-form, and git grep "'list-view'" over packages/spec/src and packages/lint/src hits only ui/react-blocks.ts (schemaType: 'list-view').
• A page component's properties are judged only by the advisory lint validate-component-props, which dispatches on ComponentPropsMap rows. So a list-view node's properties are judged by nothing.
• Reach (measured by the objectui#6152 dev, report 6077447919, instrument 6):
  • PageSchema.safeParse and PageComponentSchema.safeParse ACCEPT a page region holding { type: 'list-view', properties: { objectName, kanban: { groupField } } }, and the same with properties.options.grid.
  • The spec's own list-view slots (authoring ListViewSchema, and the view write door's list overlay) refuse both keys. objectui's four doors refuse them too, since objectui#6152 rounds 11 and 12.
  • Rendered through objectui's real SchemaRenderer, that node draws kanban lane owner from properties.kanban.groupField and from properties.options.kanban.groupField. The control with no config draws the detected stage.
• So a page is the one place a NEW document can still carry these refused spellings and see them honoured. Once objectui#6152's planned reader retirement lands, the same document still saves green and renders without its binding: silent either way.

Expected

A list-view node on a page is judged against the same list-view contract every other door applies, so a refused key is refused loudly at save or validate time.

Dedupe

MCP search_issues on objectstack (open and closed):

• 「list-view page component properties not validated ComponentPropsMap has no list-view row」: 8 hits, all closed: spec(ui): the ComponentPropsMap rows still type renderer-read members as z.unknown() — navigation on object-map / object-gantt / object-tree and conditionalFormatting on object-kanban accept 42 — the family close-out after #21445 #21464, ComponentPropsMap map/gantt/tree rows: two shipped describes are imprecise (lat-lng pair marked required; navigation list omits new_window) plus two records the pin gate will not re-check #18459, spec(ui): ComponentPropsMap has no rows for object-map, object-gantt and object-tree — add them from the renderers' read points (#7751 method) so 「以协议为准」 resolves for all five ladder blocks (objectui#8348 Q1, ruled C) #18305, html-kind page: <list-view> renders rows but no data columns — columns binding ignored in html tier (works in react tier) #12649, spec: record:reference_rail has no ComponentPropsMap row — an entry filter parses, typechecks, validates, ships, and silently does nothing #8691, PageComponentSchema.dataSource 在 list-view 之外仍无人消费:element:record_picker 丢 view,object-grid/form/kanban/calendar 等整条绑定不读(按 spec 写 dataSource 渲染出空) #6953, [移交自 objectui] ComponentPropsMap 未声明 objectui 渲染器实读的 5 个顶层 prop(page:header ×3 / page:tabs.tabStyle / page:accordion.variant)—— #5775 的清点未完 #6776, lint: <ListView searchableFields> on a React page is not checked against the object's fields #4329. Each is about other rows or other props; none names list-view.
• 「page schema list-view node properties kanban groupField accepted validate-component-props」: 2 hits, both closed: spec(ui): ComponentPropsMap['object-kanban'].grouping is z.unknown() while the board reads grouping.fields[0].field as its swimlane field — a padded or wrong-shaped grouping validates green and collapses the lanes #20831, PageComponentSchema.dataSource 在 list-view 之外仍无人消费:element:record_picker 丢 view,object-grid/form/kanban/calendar 等整条绑定不读(按 spec 写 dataSource 渲染出空) #6953. Neither is this.

Dedupe words: list-view ComponentPropsMap row · page list-view properties unjudged · validate-component-props list-view