[squarepots]

Part of #110.

What changed

The updates #236 held back for being younger than three days, now old enough. Lock files only, plus the pnpm pin; no requirement range changes.

• Tauri plugins, Rust and npm sides together: dialog 2.8.4 (rfd 0.17), updater 2.14.1 (base64 0.23, zip 9 in its Windows ZIP extraction path, which GSwitch's NSIS updates do not use) and single-instance 2.5.5. single-instance 2.5.5 releases its lock in cleanup_before_exit instead of on RunEvent::Exit; GSwitch has no RunEvent::Exit handler, and a restart still releases the lock before the new process starts.
• lucide-react 1.63.0.
• brotli 9.1.1, rustix 1.1.6, openssl-probe 0.2.2 and xattr 1.7.0.
• pnpm 10.34.9.

The duplicate windows-sys 0.60 family and base64 0.22 drop out of Cargo.lock.

Why

These are the dashboard's pending minor and patch updates. Every changed version is at least three days old. Only the named crates were updated (cargo update -p ...). A full refresh would also pull in the wasm-bindgen family released yesterday, which only builds for wasm targets and can wait for Renovate's next proposal.

Validation

• Locally on Windows: pnpm run ci:source frontend (184 Vitest tests passed, type check and build) and pnpm run ci:source platform (Tauri debug build, cargo clippy --all-targets --locked -D warnings, cargo test --locked: 189 passed, 2 ignored).
• pnpm install --frozen-lockfile accepts the lockfile.
• The file dialog and update installation were not exercised interactively. This PR's CI builds and tests on Linux, macOS and Windows. The 1.0.34 release workflow then smoke-checks the installers and updater archives.