/* ── BASE RESET ──────────────────────────────────────────────────────────── */ *, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; } html, body { height: 100%; background: var(--bg); color: var(--text); font-size: 14px; line-height: 1.5; } /* ── BOOT SCREEN ─────────────────────────────────────────────────────────── * The boot screen is hardcoded to the dark scheme regardless of the user's * actual theme. Reasoning: the boot screen renders the moment parses, * before any async work happens. At that point we know the user's theme * scheme ONLY if it's in localStorage (set by the inline bootstrap), * which on first-OAuth-login (or new device, or cleared site data) is * empty. If we let the boot screen track data-scheme, it paints with * variables.css defaults (dark), then applyTheme() switches to the user's * actual theme — producing a visible flash. By locking the boot screen to * dark colors AND a dark-filter logo, it's a stable splash that doesn't * change. The themed app reveals after boot fades out (boot.js end of * boot()), and the user only ever sees a CLEAN transition from * theme-neutral splash to themed app — no broken intermediate states. * * Hardcoded colors here match :root's dark defaults in variables.css. */ #boot { position: fixed; inset: 0; z-index: 9999; background: #0b0e14; display: flex; flex-direction: column; align-items: center; justify-content: center; gap: 18px; } /* Force the dark-scheme filter on the boot logo so the per-scheme rules * in components.css (which key off [data-scheme="…"] on ) don't * tint it amber/cream/etc. while we're still on the dark splash. */ #boot .app-logo { filter: invert(1) hue-rotate(180deg) !important; } /* Match the dark scheme's --text3 (used for boot-msg) and --border (used * for boot-bar track) so they look right against the locked dark bg. */ #boot .boot-msg { color: #4b5a7a; } #boot .boot-bar { background: #1e2740; } #boot .boot-fill { background: #3b82f6; } .boot-logo { /* Holds the docman SVG. The font properties below were inherited from when this slot was a text wordmark; they no longer apply visually but are kept for any text-fallback path. Width: the user's docman_logo.svg is auto-traced from a raster source — its paths carry hundreds of small Bezier segments that anti-alias visibly at heavy downscale. 1254 px source rendered at 320 px is a 3.9× downscale; the "MANAGE. PROTECT. EMPOWER." text element (font-size 56 in source) lands at ~14 px on screen, which is comfortably above the legibility threshold. At the previous 200 px it was ~9 px and looked soft. */ width: 320px; font-size: 28px; font-weight: 800; letter-spacing: -1px; color: var(--text); } .boot-logo span { color: var(--accent); } /* The boot logo is an inline THEME-AWARE