Revert the desktop hotkey: a new crate needs a Cargo.lock this machine cannot write

`42e06da` added `tauri-plugin-global-shortcut` to Cargo.toml without updating
Cargo.lock, and every cargo invocation in CI passes `--locked`. Both desktop
jobs failed on the same line before compiling anything:

    error: cannot update the lock file ... because --locked was passed

So this says nothing about whether the code is right — clippy never ran. The
gate did exactly its job.

There is no Rust toolchain on this workstation (rule 10 — CI verifies), and a
lockfile is the one artifact CI is deliberately forbidden to generate. Hand-
writing the entries is not a real option: it needs the exact checksum and the
whole transitive tree, and a wrong checksum fails harder than a missing one.

Reverted rather than left red, because a red `dev` blocks everything behind it
and the Android half of #1899 is green and unaffected at c8318c3. The work is
intact in 42e06da and comes back with `git revert 5e0c...` once the lockfile
exists — nothing here needs rewriting.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01K3MMqUtzX1TJgA1oypvm1c

frontend/src/desktop/bridge.ts

@@ -5,13 +5,6 @@
 
 interface TauriGlobal {
   core: { invoke: <T>(cmd: string, args?: Record<string, unknown>) => Promise<T> };
-  // Also from `withGlobalTauri`. Needed because quick capture puts the app in TWO
-  // windows, each with its own Pinia stores — a note saved in one is invisible to
-  // the other until something says so, and an event is the only channel between
-  // them that does not involve polling SQLite.
-  event?: {
-    listen: <T>(event: string, handler: (e: { payload: T }) => void) => Promise<() => void>;
-  };
 }
 
 declare global {
@@ -199,49 +192,3 @@ export const updates = {
    */
   install: () => invoke<void>("update_install"),
 };
-
-
-// --- Quick capture (#1899) ---------------------------------------------------
-
-/**
- * The stored hotkey and whether the OS actually accepted it.
- *
- * They disagree more often than you would like: a combination can be saved and
- * refuse to register because a window manager or another app already holds it,
- * and on Wayland a compositor may refuse global grabs entirely. `registered:
- * false` alongside a non-empty `shortcut` is precisely that case, and the UI has
- * to say so — a hotkey that silently does nothing is worse than none, because
- * there is nothing to look at and nothing to fix.
- */
-export interface CaptureShortcut {
-  /** The stored combination, or "" when quick capture is off. */
-  shortcut: string;
-  registered: boolean;
-}
-
-/** Offered as a starting point, never applied on the user's behalf. */
-export const SUGGESTED_CAPTURE_SHORTCUT = "CommandOrControl+Shift+N";
-
-/** Fired at the main window after a capture is saved. */
-const CAPTURED_EVENT = "thoughtsync://captured";
-
-export const capture = {
-  shortcut: () => invoke<CaptureShortcut>("capture_shortcut_get"),
-  /** Pass "" to turn quick capture off. Rejects if the system refuses it. */
-  setShortcut: (shortcut: string) => invoke<CaptureShortcut>("capture_shortcut_set", { shortcut }),
-  /** Hide the capture window; `saved` decides whether the board is told to reload. */
-  done: (saved: boolean) => invoke<void>("capture_done", { saved }),
-};
-
-/**
- * Run `handler` whenever a note is captured in the other window.
- *
- * Returns an unlisten function, or a no-op on the web build and on any desktop
- * runtime that does not expose the event API — the board simply keeps showing
- * what it has until its next load, which is a stale list rather than a broken one.
- */
-export async function onCaptured(handler: () => void): Promise<() => void> {
-  const events = window.__TAURI__?.event;
-  if (!events) return () => {};
-  return events.listen(CAPTURED_EVENT, () => handler());
-}