Verify relocated Linux desktop resource discovery and CPU worker startup

docs/LINUX-DESKTOP.md

@@ -23,3 +23,22 @@ This proves native compilation and local loader dependency resolution, not
 native UI interaction, runtime resource discovery, clean-machine deployment,
 installer packaging, Wayland shortcut operation or broad Linux compatibility.
 No Linux desktop download is published. Native graphical checks remain open.
+
+## Relocated startup
+
+The release binary started outside the build tree in an owned `bin/` directory
+with resources under `lib/searchi/`, as required by Tauri's product name.
+An isolated test profile reused a copied index and verified local model cache.
+The bundled Google process was observed with `--device cpu --role query
+--threads 1`; the desktop remained alive afterward. Owned test process groups
+were terminated. No user installation or system configuration was changed.
+
+An owned Xvfb display plus `LIBGL_ALWAYS_SOFTWARE=true`, `GALLIUM_DRIVER=llvmpipe`
+and WebKit compositor/DMABUF-disable flags were used. Mesa's software setting is
+[documented upstream](https://docs.mesa3d.org/envvars.html). No pixel rendering,
+keyboard/preview interaction or actual foreground latency is asserted here.
+Initial fixture attempts failed because a filesystem-socket readiness check did
+not suit WSL and then because resources used the Cargo name instead of product
+name. Those were test-layout corrections; the final normal-discovery run passed.
+Raw ignored report: `.searchi/qa/linux-desktop-startup-013.json`, SHA-256
+`23bfebbd916e1d1e051efd58c5286b193b15014ebfcbaa621e6a5c650338bba5`.