← Commit history
Publish 2.3.2
4 files changed
+32−10
README.md+26−6@@ -55,46 +55,66 @@ The design intent (John, 2026-08-02): the active tab should share the chat body' **Status: PASS as of 2.3.0, by the one-ground contract.** Claude chats paint `sideBar.background` when resumed from history and `editor.background` in fullEditor (command-opened) mode, so the only rule that makes the active tab flow into EVERY chat, both modes, plus every file editor, is to unify the grounds: `sideBar.background`/`foreground` take the editor ground and text in all five themes. The active tab keeps 2026's anchor equality with the editor ground, so tab == chat == file body everywhere, and inactive tabs keep the raised 2026 chrome tone so the active one is unmistakable. (The interim 2.2.0 contract matched only the history mode; superseded the same day once the fullEditor mode was measured.) The sidebar/editor boundary is carried by the border, not a fill change. +**The three-panel consistency proof** (Adom Studio, one real screenshot, pixel-verified): an ACTIVE history-resumed chat, an INACTIVE history-resumed chat, and a BRAND-NEW command-opened chat side by side. Before the one-ground contract, the new-mode chat would render a different ground than the history chats; measured now, all three bodies are the identical Adom Studio ground (#161b22, capture-shifted #181b21 in all three panels), and every chat tab flows into its body.+++  One more measured nuance (2026-08-02): Claude Code has TWO chat surface modes, history-resumed (paints `sideBar.background`) and fullEditor/command-opened (paints `editor.background`). The one-ground contract above makes them identical by construction, so the mode difference is invisible in Adom themes. Two operational notes for future auditors: VS Code caches computed theme data per extension VERSION, so editing theme files under an unchanged version renders nothing (bump to bust); and right after a theme switch, webviews restyle asynchronously, so tabs can wear different themes for a beat. Both are normal. -Each screenshot below is the real Hydrogen Desktop window, captured 2026-08-02 by driving HD's own Settings window: each scheme was selected in Settings > Appearance and Applied, which repaints HD's frontend AND pushes the mapped editor theme in one action. That flow doubled as the theme system's end-to-end unit test, and all five schemes passed on every axis: HD shell scheme attribute, the editor receiving the correct (current) theme label, and the chat body rendering the declared sideBar value within capture tolerance (downscaling shifts solid colors up to 3 channel counts; the hex values in this document are ground truth). Composition standard: sidebar closed, no editor tabs, one Claude conversation fully open. Each is the real window (VS Code plus the AI chat on the left, the wiki on the right) captured with that scheme applied end to end, then pixel-verified against the scheme's expected editor background before it was allowed on this page.+Each screenshot below is the real Hydrogen Desktop window, captured 2026-08-02 by driving HD's own Settings window: each scheme was selected in Settings > Appearance and Applied, which repaints HD's frontend AND pushes the mapped editor theme in one action. That flow doubled as the theme system's end-to-end unit test, and all five schemes passed on every axis: HD shell scheme attribute, the editor receiving the correct (current) theme label, and the chat body rendering the declared sideBar value within capture tolerance (downscaling shifts solid colors up to 3 channel counts; the hex values in this document are ground truth). Composition standard: sidebar closed, one Claude conversation open and ACTIVE with a second conversation as the inactive background tab, so every shot also proves the active vs inactive tab colors (active tab = the ground, flowing into the chat; inactive tab = the raised chrome tone). Each is the real window (VS Code plus the AI chat on the left, the wiki on the right) captured with that scheme applied end to end, then pixel-verified against the scheme's expected editor background before it was allowed on this page. ### Adom Studio (the default) -+ The flagship. The editor sheet is `#161b22` and the surrounding chrome drops back to `#0d1117`. Attention lands on the content, not the frame. The chat renders in Satoshi (an AI conversation is prose), the code blocks in JetBrains Mono. ### Adom Studio Dark (Brighter Text) -+ Same ramp as Adom Studio with the grounds swapped: deep `#0d1117` everywhere, panels raised on `#161b22`. A build-time guard ([check-scheme-parity.sh](https://github.com/adom-inc/hydrogen-desktop/blob/main/scripts/check-scheme-parity.sh)) fails the build if these two schemes ever differ by anything other than that swap. The relationship is a contract, not a hope: tune one and the guard makes you tune both. ### Adom Studio Dark -+ The original palette, tuned for long sessions: same grounds as Bright but with the quieter secondary text (`--text-2` drops from `#c9d1d9` to `#8b949e`). In CSS this is the base `:root` block; it deliberately has no override block of its own. ### Adom Kickstand -+ The brand identity palette. Menus, dropdowns, and other overlay chrome use a muted navy `#0e1c31`, which is a derivation (a 45/55 mix of the brand navy `#00204f` into the `#191919` ground), not a new color. Full-strength navy chrome read as "that weird blue" and was demoted. Prose leads with Familjen Grotesk, the headline face. One documented correction (2026-07-26): the firm's neutral Black ground stays byte-exact, but the chrome grays we derived from it carry a few points of blue, because a pure neutral gray sitting beside the blue-tinted sibling schemes is perceived as warm brown even when the pixels measure exactly neutral. ### Adom Slate -+ Cool blue-grey (`#17212e` ground) for people who find the black-on-black families too severe. Its code stack leads with Cascadia Code, which ships with Windows, so it never depends on our font install step. --- +## Fonts from the Settings window (and how that is even possible)++VS Code color themes cannot carry fonts, so the pack alone could never deliver Satoshi or JetBrains Mono. HD does it with two mechanisms working together, both visible in the Settings window's Appearance section:++1. **Delivery: the workspace serves the fonts itself.** `install-brand-fonts.sh` (run by the golden-image bake, re-runnable after code-server upgrades) copies the woff2 files into code-server's own workbench directory and injects an `@font-face` block into `workbench.html`. The editor fetches the fonts over HTTP from code-server, so a fresh machine needs no Windows font install and can never silently fall back because a machine missed a setup step.++2. **Selection: HD pushes VS Code settings keys.** The Editor Code Font and Editor Prose Font pickers write `editor.fontFamily`, `terminal.integrated.fontFamily`, `debug.console.fontFamily` (code face) and `chat.fontFamily`, `markdown.preview.fontFamily` (prose face). The chat pair was mapped by decompiling the Claude Code extension: `chat.fontFamily` is the conversation PROSE and `chat.editor.fontFamily` is the chat's CODE BLOCKS; getting those two backwards renders prose in the system font while code blocks go proportional. "Match theme" follows the scheme's pairing (Satoshi prose + JetBrains Mono code for the Studio family); an explicit pick overrides it for every scheme.++The pickers, in the real Settings window:++++And the proof it works, live: the same Claude chat with prose on Match theme (Satoshi) versus switched to Segoe UI from the Settings window, no reload:+++ ## 2. Backgrounds and foregrounds: the token sheet Backgrounds and foreground text colors are the two things that matter most, so here is the whole generated table, rendered from the live [styles.css](https://github.com/adom-inc/hydrogen-desktop/blob/main/src/routes/styles.css) rather than typed by hand:
package.json+1−1@@ -1,7 +1,7 @@ { "slug": "adom-theme", "name": "adom-theme",- "version": "2.3.1",+ "version": "2.3.2", "type": "skill", "description": "THE Adom application theme: five colour schemes with exact tokens, slugs vs labels, font pairings, the VS Code theme pack (adom.adom-theme, version-locked to this package), migration rules, and the guards. Hydrogen Desktop is the reference implementation.", "discovery_triggers": [
page.json+4−2@@ -52,7 +52,7 @@ "path": "screenshots/hero-v6.png" }, "name": "adom-theme",- "version": "2.3.1",+ "version": "2.3.2", "description": "THE Adom application theme: five colour schemes with exact tokens, slugs vs labels, font pairings, the VS Code theme pack (adom.adom-theme, version-locked to this package), migration rules, and the guards. Hydrogen Desktop is the reference implementation.", "discovery_pitch": "Implementing or matching Adom's look in any app: load this first. Exact tokens for all five schemes, the slug/label contract, font pairings and delivery traps, and the guard scripts.", "files": [@@ -83,7 +83,9 @@ "reference/install-brand-fonts.sh", "reference/check-scheme-parity.sh", "reference/check-installed-themes.sh",- "reference/check-vscode-theme-names.sh"+ "reference/check-vscode-theme-names.sh",+ "reference/gen-adom-studio-v2.mjs",+ "reference/reference-2026-dark.json" ], "scripts": { "install": "./install.sh",
vscode/package.json+1−1@@ -2,7 +2,7 @@ "name": "adom-theme", "displayName": "Adom Theme", "publisher": "adom",- "version": "2.3.1",+ "version": "2.3.2", "description": "The Adom brand theme family for VS Code. Generated from the Adom theme tokens and version-locked to the adom-theme wiki package, so the editor and the app can never disagree about a colour.", "engines": { "vscode": "^1.70.0"