The connect__step2 screenshot scenario clipped the fourth relationship option (“Make parent”) off the bottom of the frame. The nightly UX audit flagged this as a possible fixed-height overflow in the wizard’s association list.
Capture-height artifact, not a production bug. captureScreen() defaults to a 1024×768 px canvas (384dp at density 2.0). The four RelationshipOption composables with their multi-line descriptions, node badges, and Connect button total ~560dp — more than the default canvas height. In production the wizard lives inside NodeEditorContainer’s verticalScroll Column, so all four options are reachable by scrolling; the screenshot simply never gave the content enough vertical room to expand.
Added CONNECT_STEP2_HEIGHT_DP = 700 constant to CaptureScreen.kt (mirrors the DASHBOARD_HEIGHT_DP precedent) and passed heightDp = CONNECT_STEP2_HEIGHT_DP to the connectNodesStep2 captureScreen() call in Scenarios.kt. The regenerated PNG shows all four options fully rendered.
When a new screenshot scenario renders a Column whose height is content-driven rather than fixed, set an explicit heightDp large enough to fit the full content — or add a verticalScroll wrapper in the capture harness. The DASHBOARD_HEIGHT_DP constant and the existing comment in CaptureScreen.kt document this pattern; check it before publishing a new scenario whose content might exceed 384dp.