/* The default venus sheet — a FALLBACK skin for a bundle that ships no
   generated stylesheet of its own; structure emits k-/role-/var- classes
   and this resolves them. Swap the file to reskin; the .v app never
   changes.

   EVERY RULE HERE IS :where()-WRAPPED, i.e. specificity ZERO, and that is
   load-bearing. The value-compiled sheet an app generates from its theme
   (vlib/style-css.v) is itself all `:where(...)` — so while these
   selectors were bare classes they outranked the whole theme system, and
   a token change simply did not land: `.k-card` held #161b22 and
   `.k-button` held a #21262d that is not even a theme token, no matter
   what the app's `__default_theme__` said. It cost the neutral-palette
   port (venus/v0/DESIGN-PARITY.md step 2) a full round of "the colours
   changed everywhere except the cards and the buttons". Zero specificity
   plus document order means a generated sheet now always wins, and this
   file still dresses an app that has none. */
:root {
  --bg: #0e1116;
  --panel: #161b22;
  --line: #30363d;
  --fg: #e6edf3;
  --dim: #8b949e;
  --accent: #58a6ff;
  color-scheme: dark;
}
* {
  box-sizing: border-box;
}
html {
  width: 100%;
  height: 100%;
}
body {
  width: 100%;
  height: 100vh;
  height: 100dvh;
  margin: 0;
  padding: 24px;
  background: var(--bg);
  color: var(--fg);
  font:
    15px/1.5 ui-monospace,
    SFMono-Regular,
    Menlo,
    monospace;
}
#app {
  width: 100%;
  height: 100%;
  min-width: 0;
  min-height: 0;
}
:where(.k-card) {
  background: var(--panel);
  border: 1px solid var(--line);
  border-radius: 8px;
}
:where(.k-button) {
  font: inherit;
  background: #21262d;
  color: var(--fg);
  border: 1px solid var(--line);
  border-radius: 6px;
  padding: 6px 14px;
  cursor: pointer;
}
:where(.k-button:hover) {
  border-color: var(--accent);
}
:where(.role-title) {
  font-size: 18px;
  font-weight: 600;
}
:where(.role-caption) {
  color: var(--dim);
}
:where(.var-danger:hover) {
  border-color: #f85149;
  color: #f85149;
}