zk-agent-cli 0.1.0-beta.1 → 0.1.0-beta.3

package/README.md

@@ -34,7 +34,9 @@ zksync-agent --help
 
 ## Prerequisites
 
-- Node.js `>=24` if you install globally.
+- Node.js `>=24` for either `npx zk-agent-cli ...` or global install.
+  Older Node versions may still start the CLI, but the current package is not
+  supported there and npm will emit `EBADENGINE` warnings.
 - The default local approval path expects the connector UI to be reachable at
   `http://localhost:4444`. Override it with
   `zk-agent setup --connector-url <url>` when needed.
@@ -91,6 +93,7 @@ zk-agent workflow fund --wallet main --amount <amount> --execute
 Shortest relay-backed path in one command:
 
 ```bash
+zk-agent relay inspect --relay-url <relay-url>
 zk-agent wallet create --relay-url <relay-url> --wait-relay --prompt-code
 zk-agent wallet reapprove --name main --relay-url <relay-url> --wait-relay --prompt-code
 ```
@@ -98,13 +101,18 @@ zk-agent wallet reapprove --name main --relay-url <relay-url> --wait-relay --pro
 Local relay prototype path:
 
 ```bash
-zk-agent relay serve
+zk-agent relay serve --public-origin https://relay.example.com
 zk-agent wallet create --relay-url <relay-url>
 zk-agent wallet request approve --request-id <id> --relay-url <relay-url> --code <code> --wait
 ```
 
 The built-in relay is a local file-backed prototype. It is useful for operator
-testing, not a production hosted relay service.
+testing, not a production hosted relay service. When it sits behind a tunnel or
+reverse proxy, pass `--public-origin` so the emitted share/status URLs point at
+the externally reachable hosted URL instead of the local bind address. The
+published package now also ships the bundled connector UI build used by
+`relay serve`, so hosted share-link approval no longer depends on a separate
+source checkout just to serve the UI.
 
 ## Local Storage
 
@@ -124,18 +132,25 @@ Common files created by the default path:
 
 ## Smart-Account Profiles
 
-The published package can inspect built-in profiles:
+The published package ships built-in profile artifacts for the first-party
+smart-account presets:
 
 ```bash
 zk-agent wallet smart-account profiles --json
 ```
 
+That means the packaged CLI can use:
+
+- `zk-agent wallet smart-account predict --profile sed-lite`
+- `zk-agent wallet smart-account deploy --profile sed-lite`
+- the same built-in path for `daily-spend-limit`
+
 Current boundary:
 
-- profile inspection works from the packaged CLI
-- built-in profile deploys still require
-  `ZK_AGENT_ACCOUNT_PROFILES_ROOT=<checked-out account-profiles package dir>`
-  because the npm tarball does not ship the EraVM profile artifacts
+- built-in profiles work from the packaged CLI
+- custom profile artifacts still use `--artifact <json|@file>`
+- `ZK_AGENT_ACCOUNT_PROFILES_ROOT` is now only a source-checkout override for
+  development or custom runtime layouts
 
 ## Common Failures