The editor__datapoint Roborazzi screenshot showed multiple panels stacked at the same Z-position — DataPoint type chips, help text, time-range chips, and radio buttons all overlapping in one pile.
EditDataPoint emits its children at the top level without wrapping them in a Column. It relies on NodeEditorContainer’s outer scrollable Column to provide vertical layout in production. The screenshot scenario called EditDataPoint directly inside a Surface, which uses Box layout internally — so all emitted composables stacked on top of each other.
Updated editorDatapoint() in Scenarios.kt to wrap EditDataPoint in a Column with verticalScroll, PADDING_LARGE, and Arrangement.spacedBy(SPACING_LARGE) — mirroring exactly what NodeEditorContainer provides in the production path.
Editor composables that emit multiple top-level children should either (a) self-wrap in a Column like EditFilter and EditTrigger do, or (b) document that the caller must supply a Column context. Screenshot scenarios for editors that rely on caller-provided layout must reproduce that context (scrollable Column + padding), not bare Surface.