Symptom

The nightly UX audit detected dashboard node card subtitles (id=client-fixture state=EXECUTED) rendering in a visibly fixed-width/monospace typeface, clearly distinct from the proportional sans-serif used for card titles in the same composable.

Root cause

The NodeRow composable in Scenarios.kt (screenshot test helper) used raw fontSize = 11.sp without a style parameter for the subtitle Text. Without an explicit style, Compose resolves fontFamily from LocalTextStyle — which may fall through to platform defaults on the desktop JVM target rather than consistently using FontFamily.Default from DarkBlueGrayTypography. The title Text had the same raw-fontSize pattern.

There was no explicit fontFamily = FontFamily.Monospace in the composable — the monospace appearance was a side-effect of bypassing the typography system entirely.

Fix

• Changed subtitle Text from fontSize = 11.sp to style = MaterialTheme.typography.bodySmall, which bakes in fontFamily = FontFamily.Default from the theme.
• Changed title Text from fontSize = 14.sp to style = MaterialTheme.typography.titleSmall for the same reason.
• Added an intent comment explaining this is diagnostic fixture text for screenshot identification, not production UI.
• Added KrillThemeTest assertion that no DarkBlueGrayTypography role uses FontFamily.Monospace.

Prevention

• Always use style = MaterialTheme.typography.* for Text composables. Never pass raw fontSize/fontWeight/letterSpacing without a base style — raw values bypass the typography system and leave fontFamily unresolved, allowing platform-specific rendering.
• KrillThemeTest.no typography style uses FontFamily Monospace now guards against accidentally baking monospace into any typography role.