Symptom

9 of 10 Roborazzi screenshot scenarios rendered on white/near-white backgrounds with Material3 light tokens instead of ChirpyDarkColorScheme. Only dashboard__empty (which passed darkTheme = true explicitly) rendered correctly dark.

Root cause

DarkBlueGrayTheme defaults darkTheme to isSystemInDarkTheme(). In the headless Compose Desktop test environment used by Roborazzi, isSystemInDarkTheme() always returns false — there is no system dark-mode preference to detect. All scenario calls that omitted the parameter therefore silently rendered in light mode, making the screenshots evaluate a theme users never see.

Fix

Added darkTheme = true explicitly to every DarkBlueGrayTheme { } call in Scenarios.kt and NodeCatalogScreenshots.kt that is meant to capture the production dark-mode appearance. Theme-variant scenarios (theme__light__*, ftue__pin-entry__light*) that intentionally use darkTheme = false were left unchanged.

Prevention

• Always pass darkTheme = true explicitly in Roborazzi test fixtures. Never rely on isSystemInDarkTheme() in a headless test environment.
• CI screenshot baselines should be reviewed in dark mode after any theme change to catch silent regressions before they accumulate.