feat(themes): add hermes-agent teal/gold skin (#3357)

[rodboev]

Thinking Path

• The hermes-webui appearance picker ships a "Nous" dark skin with a blue-steel palette (--bg:#0A0E14, --accent:#4682B4), which was designed to echo the Nous Research brand colors, not the Hermes agent dashboard.
• The Hermes agent dashboard and marketing pages use an emerald-green and warm-gold palette; users who run both the dashboard and the WebUI have no built-in way to match them visually.
• Issue Using the teal and gold theme from Hermes agent's dashboard for the "nous" skin #3357 proposes recoloring the existing "nous" dark variant to use this palette. The maintainer (nesquena-hermes) redirected the approach: instead of overwriting a shipped skin, add a new data-skin="hermes-agent" value so both palettes remain available and the change is purely additive.
• The maintainer also flagged the typography changes in the original CSS (font-family, font-size, line-height) as out of scope for a color-palette PR, recommending they be split into a separate discussion. Those properties are omitted here.
• The full registration pattern for a new skin covers five locations: static/style.css (palette + component overrides), static/boot.js (_SKINS array), static/index.html (pre-paint whitelist), static/i18n.js (all cmd_theme help strings), and api/config.py (_SETTINGS_SKIN_VALUES allowlist). The most recently merged skin (Neon) skipped the last two, creating an inconsistency this PR addresses for the new skin while noting the pre-existing gap.
• The skin is dark-only. In light mode it falls back to the default palette. The maintainer accepted this explicitly.
• The Zeus PR (feat(skins): add Zeus skin — OLED-near-black dark surfaces with default gold accent #3328) has since merged, touching the same arrays in boot.js, index.html, i18n.js, and api/config.py. This PR is branched from a post-Zeus master, so no rebase conflict.

What Changed

• static/style.css: new :root.dark[data-skin="hermes-agent"] palette block inserted after the Zeus skin section (before Geist Contrast). Variables use the emerald/gold palette from the issue body with typography properties stripped. Component-level overrides follow the Nous/Neon pattern: new-chat button in gold, gold-tint scrollbar, tool-card borders, tree viewer in gold family, session badge colors, diff/MCP status, and lightbox controls.
• static/boot.js: {name:'Hermes Agent', value:'hermes-agent', colors:['#C89A5A','#0F1714','#22342C']} added to _SKINS after the Zeus entry.
• static/index.html: 'hermes-agent':1 added to the pre-paint skins whitelist to prevent flash-of-wrong-skin on first load.
• static/i18n.js: all 12 locale cmd_theme strings updated to append /hermes-agent to the skin list (after zeus). This closes a pre-existing gap where skins added to boot.js and index.html were never added to the help text.
• api/config.py: "hermes-agent" added to _SETTINGS_SKIN_VALUES. This allows the skin to be set via the /theme command and persisted through the server-side settings normalization path.
• tests/test_hermes_agent_skin.py: new test file with 5 tests: 4-file registration, emerald surface values, gold accent values, dark-only constraint (no light root block), and i18n locale count (12, accounting for both ASCII and full-width parens in Chinese locales).
• tests/test_zeus_skin.py: updated the stale test_zeus_i18n_lists_skin_in_all_locales assertion from count("zeus)") == 10 to count("/zeus/") == 12, since hermes-agent now follows zeus in the slug list and the locale count was already 12.

Why It Matters

Users who run the Hermes agent dashboard alongside the WebUI see two visually unrelated UIs with no way to match them. This skin closes that gap as an opt-in palette change that is purely additive, with zero risk to existing skins. Closes #3357.

Verification

C:\Apps\hermes\hermes-agent\venv\Scripts\python.exe -m pytest tests/test_hermes_agent_skin.py -v --timeout=60
C:\Apps\hermes\hermes-agent\venv\Scripts\python.exe -m pytest tests/ -v --timeout=60

Manual: open Settings -> Appearance -> Skin. Confirm "Hermes Agent" appears in the picker with gold/emerald swatches. Select it; verify the dark emerald palette renders in the chat pane and sidebar. Switch to another skin and back to confirm no style bleed. Confirm light mode falls back to the default palette (no light variant registered).

Risks / Follow-ups

• Neon/Hepburn inconsistency not fixed: api/config.py._SETTINGS_SKIN_VALUES currently omits "neon" and "hepburn". This PR adds "hermes-agent" using the full pattern but does not retroactively fix the existing gap. A follow-up PR can add "neon" and "hepburn" to config.py.
• --blue aliased to --accent: components using var(--blue) for informational affordances (links, info badges) render gold instead of blue. This is intentional for visual cohesion with the emerald/gold palette; if the maintainer prefers distinct informational coloring, --blue can be set to a muted teal separately.
• Typography: font-family, font-size, and line-height from the original issue palette are intentionally absent per maintainer guidance. A follow-up PR can propose typography changes independently.
• Zeus test fix bundled: the test_zeus_skin.py assertion update fixes a pre-existing stale count (10 vs 12 locales) alongside the pattern change needed for hermes-agent. If this PR is reverted, the zeus test would revert to the stale assertion. Noted for awareness.

Model Used

Claude Opus 4.8 via Claude Code CLI

[greptile-apps]

Greptile Summary

This PR adds a new hermes-agent dark skin with an emerald/gold palette, wiring it into all five required registration points (style.css, boot.js, index.html, i18n.js, api/config.py) and covering it with five new tests.

• New skin registered across all layers: palette variables, swatch entry, pre-paint whitelist, /theme command help strings in all 12 locales, and the server-side allowlist — following the full pattern that Neon and Hepburn had previously skipped.
• Zeus test corrected as a side-effect: the stale count(\"zeus)\") == 10 assertion (which always missed the 2 full-width-paren Chinese locales) is replaced with count(\"/zeus/\") == 12 now that hermes-agent follows zeus in the slug list.
• Dark-only design: no light-mode palette block is registered; users on light mode fall back to the default palette, which was explicitly accepted by the maintainer.

Confidence Score: 4/5

Safe to merge — the change is purely additive CSS and minor registration bookkeeping with no risk to existing skins or runtime behavior.

The implementation follows the established skin registration pattern across all five required files, the new test suite covers palette values and the dark-only constraint, and the Zeus test fix corrects a pre-existing locale miscounting bug. The only gaps are a missing CHANGELOG entry (required by AGENTS.md for user-visible changes) and a test function that names itself 'all files' but only asserts three of the five registration locations — meaning a future accidental deletion of the CSS block or the i18n slug would not be caught by that specific test.

tests/test_hermes_agent_skin.py — the registration test function misses CSS and i18n.js assertions

Important Files Changed

Filename	Overview
static/style.css	Adds :root.dark[data-skin="hermes-agent"] palette block and component-level overrides following the established Nous/Zeus/Neon pattern; scoped entirely to dark mode.
static/boot.js	Appends the Hermes Agent entry to _SKINS with an explicit value:'hermes-agent' field (required because the display name contains a space) and correct swatch colors.
static/i18n.js	Appends /hermes-agent to the skin list in all 12 locale cmd_theme strings; also implicitly fixes the pre-existing gap where Neon and Hepburn were absent.
api/config.py	Adds "hermes-agent" to _SETTINGS_SKIN_VALUES, enabling the skin to be set via /theme and persist through server-side settings normalization.
tests/test_hermes_agent_skin.py	New test file with 5 tests covering palette values, dark-only constraint, and i18n locale count; test_hermes_agent_skin_is_registered_in_all_files only asserts 3 of the 5 registration locations (missing CSS and i18n.js), making the function name misleading.
tests/test_zeus_skin.py	Updates stale locale count from 10 to 12 and switches from "zeus)" to "/zeus/" now that hermes-agent follows zeus in the slug list.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[User selects Hermes Agent skin] --> B{Theme mode?}
    B -->|dark| C[index.html pre-paint script sets data-skin=hermes-agent]
    B -->|light or system-to-light| D[No light palette block - Falls back to default]
    C --> E[style.css applies emerald/gold variables and component overrides]
    A --> G[boot.js _SKINS - Renders gold/emerald swatches in picker]
    A --> H[api/config.py allowlist - i18n.js help strings across 12 locales]

Loading

_{Reviews (1): Last reviewed commit: "feat(themes): add hermes-agent teal/gold..." | Re-trigger Greptile}

[nesquena-hermes]

Shipped in v0.51.281 (Release IW) 🎨

Thank you @rodboev — your skin is now live. We renamed it from "Hermes Agent" to Verdigris (the green-bronze patina on aged copper) to match our existing skin-naming convention (Slate, Graphite, Sienna, Poseidon…) and avoid a self-referential product name; the palette and all your component-level accents are unchanged. Your authorship is preserved via a Co-authored-by trailer on the release commit.

The branch had drifted behind master (it predated ~13 releases), so we re-applied the skin surgically onto current master across all 5 registration sites (config allowlist, boot.js swatch, index.html FOUC map, i18n ×12 locales, scoped CSS palette) plus your test file. We also corrected tests/test_zeus_skin.py since zeus is no longer the trailing skin token.

Selectable now via Settings → Appearance or /theme verdigris. Closing as merged (via the rename); closes #3357.