feat: add multimodal search and granular performance diagnostics

SKILLS.md

@@ -42,7 +42,7 @@ Use stable Rust and Node.js 24+. Before Windows VM tests or launch:
 
 ```powershell
 $env:SEARCHI_FORCE_CPU = '1'
-$env:WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS = '--disable-gpu'
+$env:WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS = '--disable-gpu --disable-accelerated-video-decode'
 ```
 
 From the repository root:
@@ -74,6 +74,9 @@ cargo test -p searchi-semantic --test gemma_cpu -- --ignored --nocapture
 Record actual outputs, hardware, corpus size, background preparation, first-input
 latency and warm latency in the relevant validation report. Unexecuted platform
 checks stay open. Compilation alone is not UI interaction verification.
+Use the opt-in measured search APIs and docs/PERFORMANCE.md for granular traces.
+Keep basic and debug overhead separate; do not sum nested stages or parallel
+lanes, or label DOM updates as actual paint. Retain raw measurement samples.
 
 ## Commit and hand off