[Feature]: Improve Hermes Desktop look & feel — design-system polish and interaction ergonomics

Present state

The desktop app has matured into a full workbench — panes, plugins, command palette, themes, A2A. But the visual density and interaction affordances have not kept pace with that functionality. For an always-on agent the chrome is the product: right now the layout reads cluttered, hierarchy is weak, and common actions are buried. I use this app daily and the friction is real, not cosmetic.

I checked existing desktop work — #52500 (UX/profile-scoped state), #49413 (accessibility), #49574 (chat readability/fonts), plus the locale/translation PRs. Those are good and specific. No one is addressing the overall design system and interaction ergonomics that this issue targets, so I don't believe this duplicates them.

What I want (in rough priority order)

1. Design tokens reference — Publish a short, authoritative list of the theme variables the app already exposes to plugins (--ui-*, etc.) so plugin authors and the built-in surfaces share one consistent design language instead of guessing. Explicitly document: text/background/stroke/accent, spacing scale, radius, type scale, focus ring. This is the highest-leverage change; everything below inherits from it.

2. Visual hierarchy — A consistent type scale, stronger text contrast, and aligned spacing across panes (workspace, sessions, files, logs). Today the hierarchy reads flat; key vs. secondary info is hard to tell apart at a glance.

3. Density & spacing audit — Tighten per-pane padding/margins so more session content is visible without endless scrolling in a maximized window.

4. Primary-action affordances — Make New Session / Resume / Switch Profile / Run Skill first-class. Today these ship behind menus; on the highest-frequency actions, one click from the top bar (or a very discoverable keybind) reduces the daily cost materially.

5. Tool-call visibility — Make in-flight tool calls visually distinct from finished ones, and surface the working state (streaming, sandbox/approval pending, long-running command) inline so it's obvious what the agent is doing and why it's waiting.

6. Keyboard-first — Ensure every frequent action has a discoverable shortcut and the command palette (⌘K) covers settings toggles, not just navigation.

Scope / effort

Medium — mostly presentational (theme tokens + top-bar / command-palette wiring + a docs page). Low risk to agent functionality; a few targeted changes land much faster than a redesign.

Why this matters

I'm filing this because I keep hitting it. A workbench-class agent earns trust when the interface disappears into the work; when the user has to hunt for controls or squint at dense, low-contrast UI, that's a tax on every session. I'd love to see a pass that makes Hermes Desktop feel as polished as it is capable.

Happy to provide screenshots / specific spots that feel most cluttered if useful — just ask.