The current dashboard at dashboard/app.js (~4768 lines, Preact, no build step) grew organically without a central design. Before we integrate it into a proper component framework, we want feedback on the design anchor mockup:

→ design/agent-dashboard.html (merging in #19) — drag into your browser; static HTML, no JS framework, ~3300 lines.

What we want input on:

1. Positioning — the mockup positions the dashboard as a companion to the TUI, not a replacement. Chat is first-class (because the TUI has rendering issues on legacy PowerShell), but the dashboard owns long-form reading / charts / multi-file editing / inventory browsing. Right framing? Or should the dashboard be primary?

2. Sidebar grouping — 14 panels grouped (workspace · observe · configure). Too many? Wrong groupings? What would you cut?

3. Chat panel — full composer, command palette (⌘K), approval modal mirrored from the TUI, slash popover anchored to the composer. What pattern would you have used instead?

4. Overview cockpit — 4 KPIs + current session + cost trend + recent plans + tool feed + system health. Which number do you actually look at first?

5. Inventories pattern (Tools / MCP / Skills / Memory / Permissions) — one filter+table+detail-drawer for all five. Right unification or premature abstraction?

6. Charts — stacked area for cost-by-source, donut for share, sparklines on KPIs. Helpful or just visual noise?

7. Editor panel — file tree + tabs + CodeMirror; "see what the agent is about to do" framing, NOT a VS Code replacement. Right scope?

8. Anything in the mockup you would cut entirely.

Stuff already on the maintainer's mind that would override design polish:

• Issue #11 — Preact insertBefore reconciler crash; needs root-cause before redesign reaches code
• Splitter / drag-resize between panes (deferred from 0.12)
• MCP callbacks surfaced into the dashboard
• i18n (deferred)

Not all feedback ships, but everything will be read. Replies in English or 中文 都行.