Ship floating launcher, automatic discovery and bounded media search improvements

tools/desktop-capture/README.md

@@ -22,6 +22,7 @@ then warms its retained CPU worker before listening on 127.0.0.1:1431.
 
 ```powershell
 $env:SEARCHI_FORCE_CPU = '1'
+$env:SEARCHI_EXTRACT_WORKER = (Resolve-Path target/release/searchi-extract-worker.exe).Path
 cargo run --manifest-path tools/desktop-capture/backend/Cargo.toml -- --root .searchi/readme-capture/files --db .searchi/readme-capture/index.sqlite --models .searchi/models/embeddinggemma2 --worker .searchi/runtime/cpu/Release/searchi-gemma-worker.exe --dist apps/desktop/dist --ffmpeg .searchi/media-runtime/bin/ffmpeg.exe --ffprobe .searchi/media-runtime/bin/ffprobe.exe
 ```
 
@@ -46,12 +47,14 @@ loaded fonts, image pixels, and genuine worker inference counters in debug mode.
 
 ## Artifacts and limits
 
-Outputs under docs/screenshots are search-light.png, search-dark.png,
+Outputs under docs/screenshots are launcher-empty.png, search-light.png, search-dark.png,
 media-search.png and performance-details.png, plus capture-manifest.json. The
 manifest contains actual fixture queries, counts/selection, measured response
 metrics, device/model, viewport, PNG SHA256, runner/browser versions, Git base
 commit and dirty-state flag. The base commit does not identify uncommitted
-source exactly. The ephemeral API token is never saved in the manifest.
+source exactly. It also records the actual frontend package version and built
+index SHA-256. The compact empty-bar capture has no manufactured results and
+uses the genuine ready backend. The ephemeral API token is never saved in the manifest.
 
 Captures are **browser-rendered production UI with the actual CPU engine**.
 They omit native window chrome. They do not establish native WebView visual QA,