kylon-cli 0.2.2-next.260 → 0.2.2-next.263

package/README.md

@@ -34,6 +34,21 @@ The dist-tag tracks the environment: production uses `@latest`, dev uses
 Requirements: Node.js 22.15.0+ (npm ships with Node). Linux / macOS only
 (Windows operators should use WSL).
 
+### Upgrading a gateway host
+
+```bash
+npx --yes kylon-cli@latest gateway service upgrade
+```
+
+(`@next` on dev.) The daemon and the pinned agent `kylon` both run the
+installed bundle under `~/.kylon/bin`, which only this command (or a
+re-connect) refreshes: the freshly-resolved CLI installs its own bundle and
+drain-restarts the running daemon onto it, moving both in lockstep.
+`npm install -g` alone updates the operator's terminal binary and leaves the
+gateway on the old build. The update notice the CLI prints on gateway hosts
+uses exactly this command; `kylon gateway service repair` is the same
+reconciliation under its recovery-oriented name.
+
 ### Local development (contributors)
 
 ```bash
@@ -524,6 +539,7 @@ npm dist-tag add kylon-cli@<last-good> latest   # move the channel back
 npm deprecate kylon-cli@<bad> "Broken release — use <last-good>."
 ```
 
-Operators on `@latest` pick up the re-pointed version the next time they
-`npm install -g kylon-cli@latest`; in-flight daemons keep their current CLI
-until they restart. Do not `npm unpublish`.
+Operators on `@latest` pick up the re-pointed version the next time they run
+`npx --yes kylon-cli@latest gateway service upgrade` (the command the update
+notice prints on gateway hosts); in-flight daemons keep their current pinned
+bundle until that drain-restart. Do not `npm unpublish`.