Update and reconnect

Four static directions for one explicit flow. The version warning transforms in place, reports server-owned progress, suppresses routine connection noise while resuming, and disappears only when the replacement server is ready on the target version.

My default pick: A It exposes all three steps without taking much vertical space or inventing extra UI.
A

Horizontal step rail

Dense, persistent, and easy to scan at a glance.
Downloading1 / 3
The update starts without adding a second banner.
Download
Install
Resume

Downloading the matching server version.

Installing2 / 3
Progress follows the update RPC, not elapsed time.
✓Download
Install
Resume

Installing and verifying t3@0.0.31.

Resuming3 / 3
Routine relay errors stay in diagnostics while resuming.
✓Download
✓Install
Resume

Waiting for bb-1 to accept commands.

B

Vertical checklist

Most explicit. Better when the update may take several minutes.
Downloading1 / 3
Each completed boundary stays visible.
•Downloading serverNow
Installing update
Resuming bb-1
Installing2 / 3
The active line changes only on a real server event.
✓Downloaded serverDone
•Installing updateNow
Resuming bb-1
Resuming3 / 3
The last step ends on the lifecycle ready event.
✓Downloaded serverDone
✓Installed updateDone
•Resuming bb-1Now
C

Single active status

Smallest footprint. The previous steps are implied by progress.
Downloading1 / 3
Minimal content above the composer.
Downloading server1 of 3

You can keep using this thread.

Installing2 / 3
One line replaces the previous line.
Installing update2 of 3

The server stays online until installation finishes.

Resuming3 / 3
The composer remains visibly unavailable during restart.
Resuming bb-13 of 3

Waiting for the new server to accept commands.

D

Environment row

Keeps progress attached to the machine, not to the current conversation.
DownloadingConnections
The chat warning can link to Connections instead of owning progress.
bb-1
T3 Connect
Downloading t3@0.0.311 / 3
InstallingConnections
Every view reads the same environment-scoped operation.
bb-1
T3 Connect
Installing t3@0.0.312 / 3
ResumingConnections
No raw endpoint error appears while this operation is active.
bb-1
T3 Connect
Resuming bb-13 / 3

Shared terminal behavior

Update complete

The new server reports ready on 0.0.31. The progress UI disappears and the composer becomes available.

Could not resume bb-1

The update remains attached to the failed stage. Generic connection details stay available in Connections.

Try again

Behavior contract

  1. The existing version warning transforms in place after the user starts the update.
  2. Downloading and installing advance only when typed server progress events arrive.
  3. Resuming suppresses routine reconnect errors but leaves them available in diagnostics.
  4. Success requires the replacement server lifecycle ready event on the requested version.