In `@Ginger/Ginger/Drivers/DriversWindows/ConsoleDriverWindow.xaml`:
- Line 102: Replace the plain Content of ColorButton with the same structured
XAML the other toolbar buttons use: create an inline StackPanel containing an
ImageMakerControl (or a small Ellipse/colored dot matching the runtime colored
swatch) and a TextBlock label so the initial visual matches what
ApplyConsoleTextColor/InitializeCommonUI will set at runtime; keep the existing
x:Name="ColorButton", Click="ColorButton_Click", Style, Margin and tooltips, and
ensure the inline content uses the same sizing/margins as sibling buttons so
first-paint appearance is consistent with the other controls.

In `@Ginger/Ginger/Drivers/DriversWindows/ConsoleDriverWindow.xaml.cs`:
- Line 34: Remove the unused using directive `using System.Windows.Markup;` from
the top of ConsoleDriverWindow.xaml.cs (it’s not referenced anywhere in the
file); update any usings ordering if needed and run a build/IDE cleanup to
ensure no other references depend on `System.Windows.Markup`.
- Around line 76-90: Replace the fragile parallel arrays _consoleTextPalette and
_consoleTextPaletteNames with a single structured collection (e.g., an array or
list of a small record/struct or tuple like { Color, Name }) and update uses to
read the color and name from that single collection using
_consoleTextPalette[_consoleTextPaletteIndex].Color and .Name; update any code
that references the old arrays (including _consoleTextPaletteIndex) to use the
new combined type so the palette and its label cannot fall out of sync.
- Around line 73-74: The init-time cast in InitTextBlocks that sets _colorText
is invalid because ColorButton.Content starts as a string and later is replaced
by a TextBlock, so _colorText stays null; fix by removing the cached _colorText
and instead obtain the TextBlock from ColorButton.Content when needed (e.g.,
inside ApplyDarkTheme and ApplyLightTheme before calling SetValue) or change the
XAML to make the button content a named TextBlock (so you can reference it
directly); update ApplyConsoleTextColor, ApplyDarkTheme, and ApplyLightTheme to
read the live TextBlock from ColorButton.Content (or use the new named element)
before updating Foreground, and remove the _colorText field and its
InitTextBlocks assignment if you choose the on-demand approach.
- Around line 92-108: ApplyConsoleTextColor currently replaces
ColorButton.Content with a fresh TextBlock and sets Foreground on both Runs,
which discards theme styling; instead, modify the existing ColorButton.Content
TextBlock (or create one only if absent) and update only the dot Run's
Foreground to the palette brush while leaving the label Run without an explicit
Foreground so it inherits the button's themed Foreground; locate
ApplyConsoleTextColor, ColorButton.Content, the created
System.Windows.Documents.Run("● ") and Run($"Text Color: ...") and change the
logic to reuse/update the existing TextBlock.Inlines (or when creating new runs,
set Foreground only on the dot and omit Foreground on the label) so theme
changes still apply.