@sys9/chord-cli 0.1.290-linux-arm64 → 0.1.292-darwin-x64

package/README.md

@@ -1,11 +1,10 @@
 # @sys9/chord-cli
 
-`@sys9/chord-cli` packages the native `chord` binary for npm. It is intended to be launched through `@sys9/cli`:
+`@sys9/chord-cli` packages the native `chord-daemon` and `chord-bridge` binaries for npm. The package exposes
+only the daemon launcher to users:
 
 ```sh
-npm install -g @sys9/cli
-sys9 chord version
-sys9 chord daemon run --server 'https://chord-api.sys9.ai'
+npx -y @sys9/chord-cli@latest run --server 'https://chord-api.sys9.ai'
 ```
 
 Copy the complete command from Add Host. On first use, open the Pair link printed by the CLI. The CLI
@@ -15,10 +14,12 @@ Direct installation also works when needed:
 
 ```sh
 npm install -g @sys9/chord-cli
-chord version
+chord-daemon version
 ```
 
-Release builds publish this root package plus platform-specific optional dependencies. The root package only contains the Node launcher; the native binary lives in the matching platform package.
+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.
 

package/package.json

@@ -1,13 +1,13 @@
 {
   "name": "@sys9/chord-cli",
-  "version": "0.1.290-linux-arm64",
-  "description": "Chord CLI package used by @sys9/cli",
+  "version": "0.1.292-darwin-x64",
+  "description": "Chord daemon and Agent bridge binaries",
   "license": "UNLICENSED",
   "os": [
-    "linux"
+    "darwin"
   ],
   "cpu": [
-    "arm64"
+    "x64"
   ],
   "files": [
     "vendor"