Lossless-decks comes online as the first markdown-first engagement — and the shell's hardcoded chrome tokens get refactored to references-only along the way

The Lossless Group becomes its own client. Unlike Calmstorm / Chroma / Humain / Reach — all of which recreated a management-supplied deck — lossless-decks starts from *nothing visual* and generates the deck from per-slide markdown concept files. That workflow earned the corpus a new `narratives/slides-content/` convention (then promptly relocated to per-client-site `context-v/` once we saw the concepts were engagement-specific), four slide concepts authored from Michael's running notes, and an Astro scaffold consuming `@dididecks/shell` that renders the four slides at `/scroll/firm/v1/`. Building it surfaced a separate structural debt: the shell shipped a `--ddd-chrome-*` token system whose defaults were calmstorm-flavored hardcoded white/grey/black RGB values. On lossless-decks's dark mode the floating section indicator rendered as a light-on-dark capsule because the shell's defaults were fighting the consumer's brand. Fixed by rewriting every chrome color and font reference to resolve against the consumer's functional tokens (`--color-surface`, `--color-text`, `--color-border`, `--font-body`, `--font-mono`) — system-tier references functional, never hardcoded, per the discipline the new `setup-new-dddecks-workspace` skill encodes. Same day: SlidePaginator extracted as a standalone shell component with type-to-jump, positioned left of the mode toggle. Same day earlier: high-severity devalue DoS (CVE-2026-42570) patched in deck-shell + splash via astro 6.3.1 → 6.4.4 bump.