Symptom

Screenshot scenarios named theme__light__* and ftue__pin-entry__light rendered with the dark color scheme despite being called with DarkBlueGrayTheme(darkTheme = false).

Root cause

DarkBlueGrayTheme accepted a darkTheme: Boolean parameter but passed ChirpyDarkColorScheme to MaterialTheme unconditionally — the parameter was never read. No light color scheme existed in the codebase.

The parameter was introduced in commit 4cde543 (fix #197) when the FTUE PIN-entry light-mode screenshots were added, but the corresponding color scheme was never created and the branch was never wired.

Fix

• Added ChirpyLightColorScheme in composeApp/src/commonMain/kotlin/krill/zone/app/ChirpyLightTheme.kt using Material3 lightColorScheme() with Chirpy light-mode palette values.
• Updated DarkBlueGrayTheme in KrillTheme.kt to select the scheme via if (darkTheme) ChirpyDarkColorScheme else ChirpyLightColorScheme.

Prevention

• Any @Composable that accepts a darkTheme parameter must branch on it before the parameter can be considered “wired.” A parameter that is only forwarded in callsites but never read is dead code.
• KrillThemeTest now asserts that the two schemes have distinct backgrounds and that the light one is brighter, catching any future accidental no-op swap.