Tauri IPC Debug

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: Your project should maintain docs/tauri-ipc-debugging.md (and related command maps). Read those first if present.

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

Rules (non-negotiable)

1. invoke is not HTTP — Browser Network tab will not show Tauri commands. External API calls appear in the terminal running tauri dev.
2. Single IPC seam — Prefer one adapter module (e.g. safe-invoke.ts) that wraps @tauri-apps/api. Debug there before scattering invoke.
3. Secrets in Rust — Bearer/tokens read in commands from keyring/file store, not passed from UI each call.
4. Keyring fallback ≠ IPC failure — keyring read failure with file fallback is often expected on Linux without Secret Service.
5. Verify with evidence — Quote ipc logs, db logs, or handler eprintln! before claiming root cause.