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/router/index.ts

@@ -24,15 +24,6 @@ const router = createRouter({
         { path: "timeline", name: "timeline", component: () => import("../views/TimelineView.vue") },
       ],
     },
-    {
-      // The quick-capture window (#1899). Its own route because it is its own
-      // WINDOW — no shell, no nav, one field. Desktop only: there is no global
-      // hotkey in a browser tab and nothing to summon it.
-      path: "/capture",
-      name: "capture",
-      component: () => import("../views/CaptureView.vue"),
-      meta: { requiresAuth: true, requiresDesktop: true },
-    },
     {
       path: "/settings",
       name: "settings",
@@ -98,13 +89,6 @@ router.beforeEach(async (to) => {
   if (to.meta.requiresDesktop && !isDesktop()) {
     return { name: "board" };
   }
-  // The capture window is opened at `index.html?capture=1` rather than at
-  // `/capture`, because the bundled assets are served as files and a path with no
-  // file behind it 404s in the production build — it only routes under the dev
-  // server. A query string survives that, and this is where it becomes a route.
-  if (to.query.capture === "1" && to.name !== "capture") {
-    return { name: "capture" };
-  }
   // Deliberately NOT applied to /login and /register: bouncing those on desktop
   // would loop against the requiresAuth guard above the moment a session is
   // missing. Nothing on the desktop navigates to them any more (AppShell's sign-out