Tauri IPC Debug — collab-finder

Mission: Fix desktop shell issues fast by tracing one layer at a time. Do not patch random files until the failing layer is identified.

Canonical doc (read first): docs/tauri-ipc-debugging.md
Context: docs/tauri-ipc-and-intent-engine.md · docs/tauri-commands.md

Pair with tauri-agentic for architecture; finder-reactor for guard/cycle logic; x-agent-resources for X API 400/401 after IPC proves Rust ran.

Rules (non-negotiable)

1. invoke is not HTTP — Browser Network tab will not show search_x_recent. X API calls appear in the terminal running pnpm tauri dev.
2. Single IPC seam — Only src/adapters/tauri/safe-invoke.ts imports @tauri-apps/api. Debug there before scattering invoke elsewhere.
3. Bearer never on each search — Rust reads storage in commands. "Not configured" → secrets/keyring/file, not missing invoke args.
4. Keyring fallback ≠ IPC failure — [secrets] keyring read failed (falling back to file store) is expected on Arch without Secret Service.
5. Verify with evidence — Quote [ipc →/←], [db], [x], or handler eprintln! before claiming root cause.