bd5b221a61
Remote-mode installs had every update affordance (About panel Update now, ⌘K Update Hermes, the update-ready toast) pointed at the BACKEND only, so users updated their VPS forever while the desktop app itself sat weeks stale — with no signal it was behind (the skew warning only fired the other way). Reported by Santiago Sarceda: mac app on v0.20.0 kept repro'ing UI bugs fixed on main because 'update' never touched the app. - store/updates.ts: applyEverythingUpdate() orchestrates all targets — active backend first (detailed progress), every other eligible registered gateway via the existing Electron fan-out (cloud rows skip), the client LAST (its apply relaunches the app). startActiveUpdate/ requestActiveUpdate route through it whenever more than one update target exists; single-machine installs keep the one-button flow. - After ANY successful backend update, the client version is re-checked and a one-click 'Update desktop app' warning fires if the GUI is still behind — the reverse-skew signal that didn't exist. - electron: hermes:connections:update-all accepts optional excludeIds so the flow doesn't double-dispatch the active backend / local runtime. - i18n: 7 new updates.* keys across en/zh/zh-hant/ja/ar. - docs: desktop.md Updating section + multi-connection guide. - tests: 10 new cases (gating, ordering, exclusions, failure isolation, memoization, nudge on/off).