@sailorbridge/client 0.2.2 → 0.2.3

package/README.md

@@ -17,6 +17,30 @@ writable and its `bin` directory is on `PATH`. Prefer a user-owned Node install
 from tools such as nvm/asdf over `sudo npm install -g`. Linux and macOS are the
 supported targets; Windows packaging support is deferred.
 
+Upgrade an npm-installed client and reload a running managed host daemon in one
+step:
+
+```bash
+sailorbridge upgrade
+```
+
+The command installs `@sailorbridge/client@latest`, compares the running and
+installed versions, and restarts the product-managed user systemd unit or
+LaunchAgent when it is running. If the host runs in the foreground or under
+another supervisor, the command prints the exact manual restart action. An npm
+failure is returned immediately with npm's stderr unchanged.
+
+The host daemon also keeps itself current: the relay broadcasts the latest
+released client version on every register/heartbeat, and `host run` upgrades
+through the same npm channel when the host is idle (active sessions defer the
+update; after 24 hours of continuous activity it upgrades at the next job gap).
+A failed attempt is logged and reported to the relay as `update_error`, then
+retried on a cooldown. Opt out with `sailorbridge host run
+--disable-auto-update` or `"auto_update": false` in
+`~/.sailorbridge/host-config.json` — but hosts below the relay's minimum
+supported version are refused at the handshake (HTTP 426) until upgraded, so a
+disabled host must be kept current manually.
+
 For a managed host daemon, use the compiled single-binary path instead of a
 Node-based global install. Build or download the native `sailorbridge` binary,
 then log in once — `login` installs and starts the user service itself:
@@ -63,6 +87,7 @@ Common commands:
 ```bash
 sailorbridge --help
 sailorbridge login
+sailorbridge upgrade
 sailorbridge workflow
 sailorbridge mailbox peek "$SAILORBRIDGE_AGENT_NAME"
 sailorbridge mailbox ack MESSAGE_ID --lease-token LEASE_TOKEN