Marimo ships this rule:
.dark, .marimo:is(.dark *) {
--csstools-color-scheme--light: ;
color-scheme: dark
}
When a .dark class is present anywhere in the tree (auto-applied from
OS prefers-color-scheme, saved user preference, or explicit toggle),
marimo flips the entire token set to dark values via CSS light-dark().
The floating outline panel, context-aware sidebar, and any bg-background
wrapper then render with #181c1a near-black instead of our cream,
with slate/black text that's unreadable.
Force color-scheme: light !important globally on html/body/.marimo/.dark
and repeat every token definition block with .dark / html.dark / body.dark
in the selector list so our editorial cream palette wins by equal
specificity + later load order regardless of any ancestor .dark class.
Also clear --csstools-color-scheme--light back to initial so the
light-dark() fallback resolves to the light value in every scope.
081613998a
