Two related changes to address "two separator lines stacked between
the bars and the dapui panes":
1. 2-row bars again. Only the OUTWARD edge of each bar draws a
separator (sep/content for status bar, content/sep for control
bar). The INWARD edge yields to dapui's pane winbar row — dapui
always renders a 1-row header with the pane title
(🧊 Call Stack, 👀 Watches, etc.) and that acts as the visual
divider. Drawing our own separator there was producing two
bright rows of chrome stacked on top of each other.
2. Theme-agnostic separator color. User's objection was that it
looked dark in their nightfox theme; before I flipped it to
FloatBorder which happened to be bright in nightfox, but that's
not portable to other themes. Now derive TurboDebugBarSeparator.fg
at runtime from WinBar.fg — the color every theme uses for
pane-title chrome, which is specifically what dapui renders for
its pane headers. Theme-agnostic: in ANY theme, our bar edges will
match that theme's pane-title chrome color. Re-applied on
ColorScheme so theme swaps stay in sync. Falls back to
WinSeparator link if WinBar has no fg (rare).
Removed `default = true` from the derived set_hl call — with it, the
placeholder link I set in the default highlights table wins because
"default" means "only set if not already defined". Unconditional set
is needed for the derive to actually take effect.
Also: Watches icon 👁️ → 👀 per user preference.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
swaitsandClaude Opus 4.6
ffe561402f