[flexdinesh]

• Behavior owner and resulting change:
  • ServerStatus.tsx (was ServerMetrics.tsx): the bordered CPU/RAM chip looked interactive (accent border on hover) but did nothing. It is now an icon-only compact ghost trigger in the status bar: success check when ready, reduced-motion-safe spinner while connecting, error alert when /api/v2/metrics is unreachable. Hover, focus + Enter, or tap opens a Base UI popover titled by the state with a "Diffx server process" section listing CPU and RAM. Future system info goes in further popover sections.
  • Header hover: --hover (#eeeef4 / #282930) was indistinguishable from the header's --shell-canvas (#edeef2 / #292a30), so header ghost actions showed no hover. New --shell-hover token gives header hover/expanded states a visible surface in both themes.
  • Header alignment: the header sat below the shell's 6px top gutter, leaving 16px above icons but 10px below them. It now replaces that gutter (flush with the window edge, still 36/44px tall), so controls center between the window edge and the islands (10px/10px).
• Contracts/invariants affected; local/remote implications: frontend only; metrics endpoint and polling unchanged; both modes share the status bar. Header height tokens and header = toolbar = drawer tab strip heights preserved; islands start 6px higher.
• Validation results; remaining risks:
  • mise run check on rebased branch: passes (90/90 browser, all Go packages, contracts, design guard).
  • New browser tests: status popover on hover and keyboard, unreachable-server state, header hover surface in light/dark, header flush with window and islands.
  • Risk: mobile drawer tab strip keeps its 6px inset, so it now sits 6px below the header row (heights still match).
• Intentional architecture/design changes and rationale: DESIGN.md adds --shell-hover, header gutter placement, and the server status pattern.
• UI evidence: checked light, dark and 390px mobile; Impeccable detector clean; no Pierre geometry changes.