v1.1.29 — Updater auto-syncs after every upgrade

Added

• In-app upgrades now auto-recreate the updater. Throwaway-pattern helper container: after the main upgrade is healthy + prune runs, scripts/upgrade.sh spawns a detached alpine container that sleeps 5s then runs docker compose up -d --build updater from outside the dying updater. The helper survives because the docker daemon owns it directly. Updater syncs to the target version within ~30s of upgrade completion.

  The whole upgrade is now top-to-bottom built in — no SSH, no manual docker compose ever. CLI runs (no /.dockerenv) skip the helper since host bash already recreated the updater as part of the main compose up.

Removed

• Drift warning in the Updates card. v1.1.24 added neutral copy explaining backend/updater version drift with a manual host command. v1.1.29's auto-recreate makes the drift self-resolve, so the warning was dead UI cruft. Asking users to run docker compose up -d --build updater was never the right answer.
• "Streaming progress below" toast description. Confusing when the user isn't on the Settings page. Toast title alone (Installing v1.1.X) is the right signal.

Bootstrap caveat

Same pattern as every prior upgrade-path fix: v1.1.28's upgrade.sh (which runs the v1.1.28 → v1.1.29 upgrade) doesn't have the helper. That specific upgrade still leaves the updater stale one last time. From v1.1.29 → vNext onward, every in-app upgrade auto-syncs the updater.