fix(desktop): route update-failure logging through logClient, not console

console.error/console.warn only forward to the server when the client log
level is debug/trace (default: info) — the earlier error-logging fix never
actually surfaced anything, and a real update failure produced zero logs
anywhere. desktop-updater.ts now calls logClient() directly, unconditionally,
plus download-progress events. Also documents the resource-sync-park-systems
branch misconfig (pointed at dev, Stacks are stage-tier) found while chasing
this — full writeup on fleet-deployment-komodo.md.

wiki/decisions/desktop-shell-tauri.md

@@ -176,7 +176,8 @@ Per the user's choices — the operator **keeps OS access** (no fullscreen lockd
     `.env.example` documenting `tauri://localhost,http://tauri.localhost` as required) — even a
     correct Origin header is useless if the server's allowlist doesn't include it. Both fixed
     together; a `resources.toml` change still needs a Komodo sync + Stack redeploy to take effect on
-    a live booth, it isn't automatic from a git push alone.
+    a live booth, it isn't automatic from a git push alone — and see [[fleet-deployment-komodo]] for
+    a real ResourceSync-branch gotcha this exact fix ran into.
 - **`VITE_API_BASE` — desktop vs. browser (regression found + fixed 2026-09-03):**
   `apps/web/.env.production` (committed, shared by both builds) sets `VITE_API_BASE=` (empty) — this
   is correct for the **browser/booth** build (Fastify same-origin, stays relative) since commit