Chrome-style silent updater: no prompt, no progress UI, no buttons.
On startup we check for updates (8s timeout), and if one is found
we download + verify + apply + relaunch — total ~3-5s on a fast
connection. The user sees the new version's window instead of the
old one, period.
Errors that do warrant a dialog (apply failed mid-write, sha256
mismatch, can't relaunch) still surface as a message box so the
user knows their copy is on the previous version. 'No update' and
network timeouts stay silent.
Split timeouts so a 60s download doesn't get killed by the 8s
check budget.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
root
15495d41ea