UX audit screenshots for editor__trigger and editor__filter showed all content (value field, body text, “Add Input Node” button) flush at x=0 with no horizontal inset.
The scenario tests rendered EditTrigger and EditFilter directly inside a bare Surface, with no horizontal padding. In production these composables are always hosted inside NodeEditorContainer, which wraps all tab content in a Column with padding(CommonLayout.PADDING_LARGE) on all sides. The scenario tests omitted that inset, so screenshots showed the x=0 flush that doesn’t exist in the real app.
Wrapped the composable in Box(Modifier.padding(horizontal = CommonLayout.PADDING_LARGE)) inside the editorTrigger and editorFilter scenario tests, matching the horizontal inset that NodeEditorContainer supplies in production.
When adding a new “bare composable” editor scenario (one that renders an Edit* composable directly rather than through NodeSummaryAndEditor/NodeEditorContainer), always ask: does this composable rely on its caller for horizontal padding? If yes, apply Box(Modifier.padding(horizontal = CommonLayout.PADDING_LARGE)) in the scenario wrapper so the screenshot reflects actual production insets.