Owner question: automatic updates on or off by default after upstream's version lands? #41

Recommendation: keep automatic updates OFF by default in the fork, also after upstream's version replaces ours.

What this is about: fork PR #5 (server updates itself when quiet) now uses upstream's setting name automaticUpdates,
so the fork can switch to upstream's version when it lands. Upstream turns automatic updates ON by default; the fork
has them OFF unless you switch them on.

The catch: a setting left at its default is never written to the settings file. So on the day upstream's version
replaces ours, every machine that never switched it on would start updating itself (and its provider CLIs) without
anyone choosing that. An update restarts T3, which stops running agents.

Options:

1. Keep OFF in the fork (recommended). At that sync the fork overrides upstream's default back to off (a one-line
   fork change, with a test). You switch it on per machine when you want it.
2. Take upstream's ON default. Less fork code, but every machine starts updating itself at that sync.

Nothing waits on this now; it matters only when upstream merges its automatic-updates PR. Answer here with 1 or 2.