@sys9/chord-cli 0.1.332-linux-arm64 → 0.1.352-darwin-x64

package/README.md

@@ -1,32 +1,14 @@
 # @sys9/chord-cli
 
-`@sys9/chord-cli` packages the native `chord-daemon` and `chord-bridge` binaries for npm. The package exposes
-only the daemon launcher to users:
+`@sys9/chord-cli` is the npm release boundary for Chord's native Host processes. The root package contains
+platform dependency metadata only; it does not expose a command or run a persistent Node process.
 
-```sh
-npx -y @sys9/chord-cli@latest run --server 'https://chord-api.sys9.ai'
-```
+The matching platform package is installed as an optional dependency and contains three native executables under
+its target vendor directory:
 
-Copy the complete command from Add Host. On first use, open the Pair link printed by the CLI. The CLI
-creates the durable Host credential locally after approval.
+- `runner`, the stable Host process supervisor;
+- `chord-daemon`, the replaceable Host coordination process; and
+- `chord-bridge`, the Agent-facing command process.
 
-Direct installation also works when needed:
-
-```sh
-npm install -g @sys9/chord-cli
-chord-daemon version
-```
-
-Release builds publish this root package plus platform-specific optional dependencies. The root package contains
-the `chord-daemon` Node launcher; the matching platform package contains the daemon and its same-version
-`chord-bridge`. The daemon pins that pair before starting and exposes the bridge only inside Agent Runtimes.
-
-If the API reports a newer daemon protocol, the packaged launcher restarts the daemon once with the exact compatible `@sys9/chord-cli` version through `npx` or `bunx`. It does not change the global installation or select an unverified `latest` version.
-
-The same launcher owns Host detail's managed `Update now` flow. After the old daemon closes, it
-snapshots daemon SQLite and starts the exact release selected by the API. The update commits only
-after that release reconnects the same Host and confirms the API has registered and settled its
-command stream. If the candidate exits or times out before readiness, the launcher restores SQLite
-and starts the packaged prior binary once. Runtime-owned Sessions, active turns, and native files
-continue through both replacement paths. A standalone native binary cannot advertise or perform
-this managed update.
+The transient `@sys9/chord-ctl` bootstrap resolves the platform package and installs the runner with the daemon and
+bridge release that share its exact version. The package manager cache is not a long-lived process authority.

package/package.json

@@ -1,13 +1,13 @@
 {
   "name": "@sys9/chord-cli",
-  "version": "0.1.332-linux-arm64",
-  "description": "Chord daemon and Agent bridge binaries",
+  "version": "0.1.352-darwin-x64",
+  "description": "Chord native runner, daemon, and Agent bridge binaries",
   "license": "UNLICENSED",
   "os": [
-    "linux"
+    "darwin"
   ],
   "cpu": [
-    "arm64"
+    "x64"
   ],
   "files": [
     "vendor"