@sailorbridge/client 0.2.2 → 0.2.4

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
@@ -80,6 +105,10 @@ sailorbridge worker serve --worker dev-1 --workdir "$PWD"
 sailorbridge supervise --agent ab_hand --cli codex --cwd "$PWD" --i-own-this-agent
 ```
 
+`worker list`, `worker run`, and `worker job` are member-runtime commands;
+`worker serve` instead uses a worker enrollment credential. The paired host
+credential created by `login` authorizes neither surface.
+
 The package ships only the built CLI/runtime files under `dist/src/` plus this
 README. It deliberately does not publish `src/`, `tests/`, or `dist/tests/`.
 Create a release tarball with `npm run pack:staged`; it stages the current build without
@@ -146,9 +175,11 @@ SAILORBRIDGE_MAX_CONCURRENCY=1
 `SAILORBRIDGE_CAPTAIN_ID` is required by `worker list`, `worker run`, and
 `worker job`; it must be a numeric string. `worker list` and `worker run` also
 require `SAILORBRIDGE_SESSION` so an unbound admin credential cannot
-accidentally discover workers across teams. A paired host credential can
-supply the captain id, but it does not contain a session, so list/run still
-need `SAILORBRIDGE_SESSION`. Agent routing uses the separate
+accidentally discover workers across teams. These commands require a
+member-runtime credential; a paired host credential is not a member credential
+and is rejected before any relay request. Use the console Workers page to list
+workers, or run the command inside a member workspace where the product provides
+the token, captain id, and session. Agent routing uses the separate
 `SAILORBRIDGE_AGENT_NAME`.
 
 `SAILORBRIDGE_HOST_ID` and `SAILORBRIDGE_HOST_DISPLAY_NAME` identify the
@@ -197,8 +228,9 @@ status never completes a SailorBridge task lifecycle.
 `https://www.sailorbridge.com`. The command displays the one-time code and
 polls until approval. The stored credential contains a host-scoped relay key
 (`key_scope: "host"` plus `host_id`) and is used as a fallback when
-`SAILORBRIDGE_RELAY_URL` or `SAILORBRIDGE_TOKEN` are not set. Raw host keys are
-written to the credentials file only. Data commands default to
+`SAILORBRIDGE_RELAY_URL` or `SAILORBRIDGE_TOKEN` are not set. Worker data
+commands reject this host-scoped fallback before any relay request. Raw host
+keys are written to the credentials file only. Data commands default to
 `--format plain`; login's plain success output prints the host id, credential
 path, and service status. Explicit `--format json` prints key id and host
 metadata, not the token.