mention that Officer administers the network it just told you to set up

The section explains three ways to get a coordination server and then says
nothing about running one afterwards, which is the part that decides whether
self-hosting is a good idea. Officer's Headscale app is the answer to it, and it
works against headscale and offscale alike.

Written from what the app actually does rather than from the pitch: several
servers registered and switched between, each PROBED rather than remembered — the
comment in ServersView.tsx is explicit that a "not checked" dot is the one thing
that list must never show — and, on the active one, nodes, users, pre-auth keys,
invites and the ACL policy with an assistant, plus a console and diagnostics.

Placed in FOR OFFICER rather than under offscale, because it is true of either
self-hosted option and is the reason picking one is not a commitment to
administering it over ssh.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

scripts/setup/machine-setup/lib/tailscale.sh

@@ -141,6 +141,15 @@ tailscale_networks_help() {
   echo "     internet in the first place. Installed at this point in the run,"
   echo "     before anything that can lock you out, so there is always a second"
   echo "     way in."
+  echo ""
+  echo "     Officer also administers it. Its Headscale app talks to headscale"
+  echo "     and offscale servers alike: register as many as you run, see which"
+  echo "     are actually up — each is probed, not remembered — and switch"
+  echo "     between them. On whichever is active you get the nodes, the users,"
+  echo "     the pre-auth keys, the invites and the ACL policy, with an"
+  echo "     assistant for writing it, plus a console and diagnostics. So the"
+  echo "     server this section sets up is managed from the same place as"
+  echo "     everything else on this machine, rather than over ssh and a CLI."
 }
 
 tailscale_is_installed() { command -v tailscale &>/dev/null; }