You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
plus lazy/source on sections and layout.renderStrategy: progressive. None of these is a real authoring surface:
FormSectionSchema (packages/spec/src/ui/view.zod.ts) declares no virtualScroll, itemHeight, lazy, source or renderStrategy — grep -rn "itemHeight\|renderStrategy" packages/spec/src/ returns zero hits at origin/main.
The audit trail already flagged this passage: docs/audits/2026-06-handwritten-docs-accuracy-followups.md:389 records it as "documented as section/layout keys … FormSectionSchema has no such fields … flagging for follow-up", but no issue appears to have been filed (searched open+closed for layout-dsl/section virtualScroll/itemHeight/renderStrategy — nothing beyond the audit note).
The followup note pointed at PerformanceConfigSchema (responsive.zod.ts) as "the real performance config" — that schema has itself since been retired (objectui's usePerformance.ts header records the spec schema behind it was retired in 17.0.0-rc.1), so the note's own remedy is stale too.
Fix that lands here: rewrite/remove the affected layout-dsl.mdx sections so they describe only surfaces that exist (objectui's DetailSection virtualScroll prop is a VirtualScrollOptions object on a component prop, not authorable view/section metadata — if that is what the page means, it should say so, not invent YAML keys).
Found during the #7176 census (retiring the view-level
virtualScroll); this is a different surface and was deliberately left out of that PR.content/docs/protocol/objectui/layout-dsl.mdx(~lines 940-985, the "Performance Optimization" family of sections) documents YAML like:plus
lazy/sourceon sections andlayout.renderStrategy: progressive. None of these is a real authoring surface:FormSectionSchema(packages/spec/src/ui/view.zod.ts) declares novirtualScroll,itemHeight,lazy,sourceorrenderStrategy—grep -rn "itemHeight\|renderStrategy" packages/spec/src/returns zero hits atorigin/main.docs/audits/2026-06-handwritten-docs-accuracy-followups.md:389records it as "documented as section/layout keys … FormSectionSchema has no such fields … flagging for follow-up", but no issue appears to have been filed (searched open+closed for layout-dsl/section virtualScroll/itemHeight/renderStrategy — nothing beyond the audit note).PerformanceConfigSchema(responsive.zod.ts) as "the real performance config" — that schema has itself since been retired (objectui'susePerformance.tsheader records the spec schema behind it was retired in 17.0.0-rc.1), so the note's own remedy is stale too.list.striped/list.bordered/list.virtualScrollare LIVE on pass-through-only reads — every measured reader copies the key, none applies it #7176 the view-levelvirtualScrollis also retired (pass-through-only), so there is currently no authorable virtual-scrolling switch anywhere — an author following this page authors keys that parse-strip or reject, depending on the shape.Fix that lands here: rewrite/remove the affected layout-dsl.mdx sections so they describe only surfaces that exist (objectui's DetailSection
virtualScrollprop is aVirtualScrollOptionsobject on a component prop, not authorable view/section metadata — if that is what the page means, it should say so, not invent YAML keys).Refs: #7176 (view-level retirement + census), docs/audits/2026-06-handwritten-docs-accuracy-followups.md:389.
Generated by Claude Code