← Commit history

Publish 2.3.1

John Lauer ·afab7d8236 · ·parent 55f44cb
4 files changed +14−12
README.md+8−8
@@ -39,13 +39,13 @@ Every scheme has a product label (what users see) and a slug (the frozen storage  The comparison that actually matters when you pick a theme: the same live Claude chat, same content, captured five times with only `workbench.colorTheme` changed (applied live through adom-vscode, no reload). The background is what dominates your eye all day; the text color is what you read non-stop. Exact values under each column. -![The five schemes side by side](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/theme-compare-v3.png)+![The five schemes side by side](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/theme-compare-v4.png)  ### Is "(Brighter Text)" honest? The measured delta  Fair question, asked and verified 2026-08-02: in the 5-column comparison the two Dark variants look nearly identical, because a 12.3:1 vs 16.0:1 text lift compresses at small sizes (both are "light gray on dark"; the jump is 10 points of perceptual lightness, carried entirely in thin glyph strokes). The pixels in the shipped screenshots confirm the lift is real: glyph cores measure 190 luma (Dark) vs 218 luma (Brighter Text), a 15 percent lift exactly tracking the designed #c9d1d9 to #e6edf3 move. Same sentence, same background, zoomed: -![Dark vs Brighter Text, same sentence zoomed](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/brighter-zoom.png)+![Dark vs Brighter Text, same sentence zoomed](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/brighter-zoom-v2.png)  If a bigger delta is ever wanted, the knob is the fg anchor in the generator (one value), but past ~14:1 dark-mode text starts to halo, and Brighter Text already sits at 16:1, so push with care. @@ -55,7 +55,7 @@ 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. -![Active tab vs chat body, measured, all themes + control](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/seam-validation-v2.png)+![Active tab vs chat body, measured, all themes + control](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/seam-validation-v3.png)  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. @@ -65,31 +65,31 @@ Each screenshot below is the real Hydrogen Desktop window, captured 2026-08-02 b  ### Adom Studio (the default) -![Adom Studio](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/scheme-studio-v3.png)+![Adom Studio](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/scheme-studio-v4.png)  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) -![Adom Studio Dark (Brighter Text)](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/scheme-studio-bright-v3.png)+![Adom Studio Dark (Brighter Text)](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/scheme-studio-bright-v4.png)  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 -![Adom Studio Dark](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/scheme-studio-dark-v3.png)+![Adom Studio Dark](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/scheme-studio-dark-v4.png)  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 -![Adom Kickstand](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/scheme-kickstand-v3.png)+![Adom Kickstand](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/scheme-kickstand-v4.png)  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 -![Adom Slate](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/scheme-slate-v3.png)+![Adom Slate](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/scheme-slate-v4.png)  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. 
package.json+1−1
@@ -1,7 +1,7 @@ {   "slug": "adom-theme",   "name": "adom-theme",-  "version": "2.3.0",+  "version": "2.3.1",   "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-v5.png"   },   "name": "adom-theme",-  "version": "2.3.0",+  "version": "2.3.1",   "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.0",+  "version": "2.3.1",   "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"