fix(ui): align composer model and voice controls

[sunheyi6]

What changed

• Rebind the composer model and thinking-level selectors to Maka palette tokens, including their popovers.
• Present both selectors as flat, borderless toolbar controls while retaining a themed keyboard-focus state.
• Hide voice capture and realtime voice buttons until the corresponding connection and model are configured.
• Refresh the shell settings mirrors when Settings closes so voice control visibility updates without restarting.
• Add focused coverage for unconfigured, independently configured, and whitespace-only voice routes.

Why

The Astryx selector subtree inherited neutral theme colors from its closer Theme wrapper, so the model controls stayed white/gray after a Maka palette change. Voice callbacks were also always passed to the composer, which made the buttons render before a usable voice route existed.

User impact

Composer model controls now match the selected theme and no longer look like nested form fields. Voice controls appear only when their related Settings configuration is complete.

Validation

• npm --workspace @maka/desktop run typecheck
• npm --workspace @maka/desktop run build:main
• node --test apps/desktop/dist/main/__tests__/voice-composer-availability.test.js
• npm --workspace @maka/desktop run build:renderer
• git diff --check

[Astro-Han]

P2. The realtime half is dead plumbing. realtimeVoiceConfigured has no reader; voiceComposerAvailability().realtime and the realtimeVoiceState prop wired in app-shell feed Composer props that are marked @deprecated and never rendered. The capture half is a real simplification: the separate effect collapses into refreshShellSettings. Keep that, drop the realtime state, or actually render the control.

P3. The useShellAppearance docstring still says closeSettings re-reads only the default permission mode; it now calls refreshShellSettings().

[Astro-Han]

Review: MERGE-READY ✅ (2 independent reviewer passes)

DeepSeek review of the full diff plus the incremental commit (a38c1af0, drop dead realtime voice-route state) on top of the previously approved head:

• Incremental commit is clean: realtimeVoiceConfigured state, voiceComposerAvailability().realtime field, and app-shell wiring removed completely (zero grep hits); the capture gating path is untouched and behavior-preserving.
• Gating equivalence verified: the three refresh triggers (mount / external change / settings close) fully cover the old effect's triggers with one fewer duplicate subscription; trim-based checks are verbatim-equivalent to the old contract.
• CSS token binding verified: all 11 Astryx target tokens and 7 Maka source tokens exist; Popover has no createPortal, so token cascade reaches the popover; oklch(from …) is supported by Electron 43.
• No merge conflicts with current main (merge-tree clean); tests pass; CI green (changes/typecheck/test/e2e).

Non-blocking P3 (optional, do not gate):

1. Two dead prop wirings remain (realtimeVoiceState/onToggleRealtimeVoice at app-shell.tsx:2228/2236, never read by Composer) — the realtime cleanup should ideally include these two lines; safe to remove in a follow-up.
2. voiceComposerAvailability returns a single-field { capture } object — could be a plain boolean; cosmetic.
3. On settings-refresh failure, a stale-true mic visibility can persist (pre-existing trade-off of the shared refresh path, not introduced here).

None block merging.