feat: integrate Google semantic search and branded desktop launcher

docs/VALIDATION.md

@@ -5,7 +5,7 @@ All local tests run on CPU; no GPU provider is configured.
 
 ## Current integration checkpoint (2026-10-12)
 
-- `cargo test --workspace --locked`: 39 default tests passed. Four asset-dependent
+- `cargo test --workspace --locked`: 41 default tests passed after final core integration. Four asset-dependent
   or explicit benchmark tests remain opt-in; a default pass does not run them.
 - Native desktop tests: 7 passed with SEARCHI_FORCE_CPU=1 and WebView2 GPU disabled.
 - Frontend: 7 async-state tests passed, Prettier passed, TypeScript/Vite build passed.
@@ -18,6 +18,15 @@ All local tests run on CPU; no GPU provider is configured.
   blocked because browser bootstrap and native screen capture are unavailable.
   No visual match or complete UI interaction verification is claimed.
 
+Final UI integration: the branded compact launcher, local Inter/Fluent assets,
+themes and motion implementation passed frontend build, formatting, and seven
+state tests. Native launch succeeded; accessibility text showed real controls
+and a warmed Google CPU worker. UI input and screenshots remain blocked by
+Windows access/capture errors, as recorded in design-qa.md. Workspace formatting
+and strict all-target Clippy passed. The fixed full-corpus first-input report
+is in crates/searchi-core/benchmarks/results/windows-cpu-full-candidate-first-final.json;
+all 40 measured filename inputs were below 50 ms in that run.
+
 The active parallel development branches of work may add tests or change counts
 after this checkpoint. Run the documented checks again after integration.