Pacenote v0.6.6

A team hub now installs from one command Pacenote writes, and Pace switches to it as soon as it answers.

brew update && brew upgrade --cask pacenote

Team hub

Install it from Pacenote. In Settings > Messengers > Slack > Team hub (or setup's "Join your team's hub"), "No hub yet? Install one on a Linux server" writes one command for the server, for the address members will use and who can use it. The command holds no secret.
On the server. The command runs deploy/hub/install.sh from this release: it writes compose.yaml and hub.env in ~/pacenote-hub, asks for the Slack app's two tokens on the server's terminal without showing them and checks them with Slack, starts the hub with Docker, and waits until it answers. Run it again to update the hub; the tokens stay.
Pace switches by itself. Copied from Settings while Pace answers on your own Slack app, the command carries this Mac's pairing as a hash. The hub pairs it once when it first starts, and Pacenote switches Pace to the hub the moment it answers, with no code to send in Slack. Otherwise this Mac pairs with a code once the hub is up.
Back to the app. The installer ends with a pacenote://hub/connect link: a click in most Mac terminals opens Pacenote on that hub, which fills in the address and asks before anything changes.