relayflows 2.0.1 → 2.0.3

package/README.md

@@ -17,4 +17,15 @@ carry the same version number, and this package pins its dependency to that
 exact version rather than a range, so `npm install -g relayflows` always
 resolves the SDK build it shipped with.
 
+It also declares the per-platform runtime packages
+(`@relayflows/runtime-linux-x64`, `@relayflows/runtime-darwin-arm64`) as
+`optionalDependencies`, pinned the same way. Each declares `os`/`cpu`, so npm
+installs only the one matching the current machine and silently skips the
+rest — this is what lets `flows run` spawn `relayflowd` with no manual build
+step (`kernel/DAEMON-LIFECYCLE.md` §3.1's `relayflowd-path.ts` resolution
+finds it as an optional dependency of this package). A platform with no
+runtime package yet (Intel Mac, Windows) installs `relayflows` fine; `flows`
+then falls through to a source checkout or `PATH`, and refuses with
+`relayflowd_not_found` if neither has a binary.
+
 See `@relayflows/sdk` and `docs/SURFACE.md` for what the CLI actually does.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "relayflows",
-  "version": "2.0.1",
+  "version": "2.0.3",
   "description": "Relayflow v2 CLI. Installs the `flows` command — a thin wrapper around @relayflows/sdk, published under the unscoped name for `npm install -g relayflows`.",
   "type": "module",
   "license": "Apache-2.0",
@@ -16,7 +16,11 @@
     "flows": "./bin/flows.js"
   },
   "dependencies": {
-    "@relayflows/sdk": "2.0.1"
+    "@relayflows/sdk": "2.0.3"
+  },
+  "optionalDependencies": {
+    "@relayflows/runtime-linux-x64": "2.0.3",
+    "@relayflows/runtime-darwin-arm64": "2.0.3"
   },
   "engines": {
     "node": ">=20"