ui: paint the whole frame from the brand palette, so a light terminal theme cannot bleed through

[ellipsis-dev]

The palette was only hardcoded halfway. The CLI paints its own near-black canvas (theme.canvas), but most text reached ink with no color prop, often a bare dimColor. Ink leaves an uncoloured <Text> on the terminal's default foreground — which under a light theme is near-black, on our near-black canvas. The transcript body is the worst of it: styleFor left textColor undefined for the assistant, tool, tool_result, thinking, system, notice and summary kinds, i.e. most of a session. Reported by a user whose light-theme terminal made agent unreadable.

1. Every <Text> carries a brand hex. Secondary copy takes theme.muted instead of dimColor — \x1b[2m is dropped outright by a fair number of terminals once a 24-bit foreground is also set, which is the same reason the live pulse already swapped colours rather than dimming. A new spanColor() in transcriptRows is the one choke point where a transcript span becomes a colour: pulse off-beat, dim, and no-colour-at-all all resolve to real hexes there, so RowLine loses its three dimColor props and styleFor is untouched. Both composers' parent <Text> now sets a colour, so typed text isn't left on the terminal default and the inverse caret has a known pair to swap.

2. theme.ts quantizes the surfaces before ink sees them. chalk resolves a hex whose channels differ to the 256-colour cube, whose darkest step above black is rgb(95,95,95); it only reaches the 24-rung greyscale ramp when r == g == b. The brand surfaces are warm greys, so on a terminal that does 256 colours but not truecolor (Terminal.app, tmux without RGB, mosh) all three collapsed onto cube index 59 at once: the canvas painted mid grey and every surface step — with it every "you are here" highlight — disappeared. surfaceFor() averages the channels below truecolor, putting each surface on its own rung (234/235/236). Truecolor is untouched; 16-colour terminals render both spellings as palette black.

3. Markdown tables lose chalk.red heads and cli-table3's border: ['gray'] — the last two colours resolving through the user's own palette (cli-table3 can only colour borders by chalk name). Heads are bone + bold; the rules are painted muted after the table is drawn.

npm run typecheck clean, 402/402 tests, npm run build clean. New test/theme.test.ts pins the surface-collapse regression; the markdown colour tests were confirmed to fail before the fix.

Note: the reporter described the screen as "all red", and I could not reproduce a literally all-red frame — the only literal reds in the CLI were the markdown table headers (chalk.red, fixed here) and error text. What is fully explained and fixed is the "super difficult to read": near-black text on our near-black canvas, plus the mid-grey surface collapse on 256-colour terminals. A screenshot would confirm nothing is left.

---

Origin: written and verified as a handoff in ellipsis-dev/ellipsis#6048 (§7 there explains why it shipped as a patch — sandbox tokens could not reach this repo at the time). Applied here with git am onto 9d479f1, then re-verified: typecheck clean, 402/402, build clean, and the collapse reproduced (59,59,59 authored → 234,235,236 quantized) before and after.

🤖 Generated with Claude Code