From 1b76c51fbb2263473fe85a1c5f14ce0d48d991ab Mon Sep 17 00:00:00 2001
From: Jaap-Jan de Wit | DodoTech <jaap-jan@dodotech.dev>
Date: Sat, 8 Aug 2026 00:49:59 +0200
Subject: [PATCH] Name v5b's deep chrome, its track and its magenta in the
 palette

---
 src/DodoSSH.Client.Shell/Theme/Palette.axaml | 65 ++++++++++++++++++++
 1 file changed, 65 insertions(+)

diff --git a/src/DodoSSH.Client.Shell/Theme/Palette.axaml b/src/DodoSSH.Client.Shell/Theme/Palette.axaml
index eeb2199..92fdcbf 100644
--- a/src/DodoSSH.Client.Shell/Theme/Palette.axaml
+++ b/src/DodoSSH.Client.Shell/Theme/Palette.axaml
@@ -232,4 +232,69 @@
   <FontFamily x:Key="MonoFont">avares://DodoSSH.Client.Shell/Assets/Fonts#JetBrains Mono,ui-monospace,Cascadia Mono,Consolas,monospace</FontFamily>
   <FontFamily x:Key="IconFont">avares://DodoSSH.Client.Shell/Assets/Fonts#Material Icons</FontFamily>
 
+  <!--
+    ── v5b ─────────────────────────────────────────────────────────────────────────────────────────────
+    A fidelity pass rather than a new design: the titlebar and the nav rail are redrawn closer to what
+    v3's own mock actually specifies, and the eight values below are what that redraw needed and did not
+    already have a name for. They arrived together because the source notes' table did, not because they
+    are one idea — read each on its own.
+
+    DeepChrome is one step darker than Chrome itself, #0B0B14 against #10111E, and it is what the titlebar
+    and the nav rail are painted in now instead of Chrome. The two used to share Chrome's value; the mock
+    draws the window's own furniture — the bar at the top, the rail down the side, the strip a session
+    sits in, a host's header row, the status bar at the foot — one shade below every screen it frames, so
+    the frame reads as the thing holding the glass rather than as another pane of it. Only the titlebar and
+    the rail are repainted in this pass; the session shell's header row and the status bar are wave B's.
+
+    Track is rgb(20,21,36), and it is not Hover: the two are close enough to be mistaken for a rounding
+    error and are not one. Hover, #14151E, is what a row goes to under the pointer everywhere this palette
+    already reached. Track is a half-step warmer and is what three specific things ask for instead — the
+    segmented switcher's own resting track, the rail row a pointer sits over, and (in wave B) a selected
+    file row — because the mock draws those three at a value Hover does not quite match, and "close enough"
+    is how a screenshot next to the mock finds the seam this file exists to prevent.
+
+    Pane is rgb(10,10,18), the file and terminal surface's replacement for TerminalSurface in this design:
+    darker and cooler rather than warmer, which is the same swap the surfaces above went through when v3
+    turned the whole palette near-black. Not renaming TerminalSurface itself, because nothing has repainted
+    a terminal pane yet — this key exists so wave B's SFTP panes have a name to reach for when they do.
+
+    SearchPill is the titlebar's own field, rgb(20,20,31) — close to Field's #101019 and a distinct value
+    the mock states for this one control, with BorderMid as its resting border and Accent replacing it
+    under the pointer. Kept separate from Field for the reason Raised and Chrome stay separate from each
+    other: the day the search pill needs to move again, a shared key would have to be pulled apart first.
+
+    KbdChip, rgb(35,35,58), is the fill behind the keyboard-shortcut hint inside that pill — CTRL K, not
+    the mock's ⌘K; see TitleBar.axaml. Distinct from Chip's #1A1A28 because the two are asked to sit near
+    each other in the one place both appear and a shared value would read as one shape rather than two.
+
+    Magenta, rgb(221,18,150), is SFTP's own colour: the top border of an active SFTP tab in wave B's session
+    shell, and the check square beside a shown vault in the rail's popover below. Named for what it looks
+    like rather than for a job, because it is about to do two unrelated ones and a name tied to either would
+    be wrong for the other — the same reasoning Chip's own name follows.
+
+    TerminalTabAccent, rgb(124,92,255), is a second read of the window's own Accent — close to #5D42DE and
+    not equal to it — reserved for exactly one thing: the top border of an active terminal tab in wave B's
+    session shell, so SSH's own tab reads as a different colour from SFTP's magenta one at a glance. Added
+    now, alongside the rest of this table, rather than when wave B first draws a tab; it is unused until
+    then, which is stated here so the next reader does not go looking for what has not been wired up yet.
+
+    AvatarGradient is the rail's own user chip: a 134.668-degree sweep through three violets, #4A37A9 into
+    #8D51E7 into #AB49EC, behind the two-letter initials the chip draws from whichever name is actually
+    signed in. A LinearGradientBrush rather than three stops guessed at a round angle, because Avalonia's
+    gradient axis is start-point-to-end-point rather than degrees, and the coordinates below are what the
+    mock's own angle resolves to.
+  -->
+  <SolidColorBrush x:Key="DeepChrome" Color="#0B0B14" />
+  <SolidColorBrush x:Key="Track" Color="#141524" />
+  <SolidColorBrush x:Key="Pane" Color="#0A0A12" />
+  <SolidColorBrush x:Key="SearchPill" Color="#14141F" />
+  <SolidColorBrush x:Key="KbdChip" Color="#23233A" />
+  <SolidColorBrush x:Key="Magenta" Color="#DD1296" />
+  <SolidColorBrush x:Key="TerminalTabAccent" Color="#7C5CFF" />
+  <LinearGradientBrush x:Key="AvatarGradient" StartPoint="14%,0%" EndPoint="86%,100%">
+    <GradientStop Color="#4A37A9" Offset="0" />
+    <GradientStop Color="#8D51E7" Offset="0.46" />
+    <GradientStop Color="#AB49EC" Offset="1" />
+  </LinearGradientBrush>
+
 </ResourceDictionary>