@engramx/client 0.16.0-rc.17 → 0.16.0-rc.18

package/README.md

@@ -66,7 +66,7 @@ const files = await engram.readMemoryBatch(['MEMORY.md', 'memory/daily.md']);
 > ```typescript
 > const bundle = await engram.captureEvidence(receipt, 'memory/daily.md');
 > // fs.writeFileSync('bundle.json', JSON.stringify(bundle));
-> // npx @engramx/client@0.16.0-rc.17 verify bundle.json  → each link, the signed time, the entries walked
+> // npx @engramx/client@0.16.0-rc.18 verify bundle.json  → each link, the signed time, the entries walked
 > ```
 
 
@@ -88,7 +88,7 @@ in-repo consumer as a reason to report what breaks, not as a warning that it doe
 
 The 2026-08-17 charter diet (below) deleted a lot of caller-less methods and **deliberately kept
 these two.** Zero in-repo callers was the reason to look at them; it was not the reason to decide.
-Three facts decided it. They are what `npx @engramx/mcp@0.16.0-rc.17 connect` *instructs* whoever builds a new
+Three facts decided it. They are what `npx @engramx/mcp@0.16.0-rc.18 connect` *instructs* whoever builds a new
 SDK-lane agent to call, verbatim, in the guide the dashboard's connect page renders — deleting a method
 while still telling people to call it is the failure this whole exercise exists to prevent.
 `startSession()` is the only read on the **update** path, so it is the only one the canister can
@@ -114,13 +114,13 @@ Pair your agent with an engram:
 
 ```bash
 # Pair the agent on this machine with the engram and install the OpenClaw plugin
-pnpm dlx @engramx/client@0.16.0-rc.17 pair <invite-code> --engram <canister-id> --target openclaw
+pnpm dlx @engramx/client@0.16.0-rc.18 pair <invite-code> --engram <canister-id> --target openclaw
 
 # Replacement machine — after pairing, restore memory from the engram
-pnpm dlx @engramx/client@0.16.0-rc.17 migrate --engram <canister-id> --recover
+pnpm dlx @engramx/client@0.16.0-rc.18 migrate --engram <canister-id> --recover
 ```
 
-`pair` generates the key for this engram at `~/.engramx/session.key` (and, on the first pairing, the agent's lasting key at `~/.engramx/root.key`), pairs the agent — the CLI prints `Paired as an agent` — and installs the OpenClaw plugin. `migrate` then moves memory, saving a local checkpoint first — run `npx @engramx/client@0.16.0-rc.17 rollback` to undo. Its default direction pushes local memory files to the engram; `--recover` instead restores database backups, and memory files sync automatically on next OpenClaw startup.
+`pair` generates the key for this engram at `~/.engramx/session.key` (and, on the first pairing, the agent's lasting key at `~/.engramx/root.key`), pairs the agent — the CLI prints `Paired as an agent` — and installs the OpenClaw plugin. `migrate` then moves memory, saving a local checkpoint first — run `npx @engramx/client@0.16.0-rc.18 rollback` to undo. Its default direction pushes local memory files to the engram; `--recover` instead restores database backups, and memory files sync automatically on next OpenClaw startup.
 
 ⟨2026-10-13⟩ `pair` moves no memory unless you add `--migrate`, and `--yes` never adds it. Without it, `pair` leaves any OpenClaw memory files on this machine where they are and prints one line: how many it found, and the `migrate` command that moves them. With `--migrate`, it runs that migration after pairing — each file is uploaded, then deleted here, and `rollback` restores them. Through 0.16.0-rc.11, `pair` ran the migration on every pairing, whatever the `--target` (Claude too), and answered its own question under `--yes`.
 
@@ -136,7 +136,7 @@ If the owner of the wallet allows it (a standing allowance they set for this age
 page), the agent can open an engram of its own through the engram it works in. The owner may be a program. Whoever runs that program is the owner for every purpose on these pages.
 
 ```bash
-npx @engramx/client@0.16.0-rc.17 open-engram --engram <canister-id>
+npx @engramx/client@0.16.0-rc.18 open-engram --engram <canister-id>
 ```
 
 The engram it works in pays to open it, from its own balance, and the agent's lasting key
@@ -145,7 +145,7 @@ paid in is the agent's from the moment the new engram exists, and nothing is tak
 reads the allowance first and stops, with nothing spent, when there is none; it never creates a
 lasting key; and it prints the engram's own sentence when the engram refuses. It then prints the
 owner kit's command that acts as the new engram's owner with the same file —
-`npx @engramx/owner@0.16.0-rc.17 --connect --key-file <that file> --registry <id>`, with both filled in — which
+`npx @engramx/owner@0.16.0-rc.18 --connect --key-file <that file> --registry <id>`, with both filled in — which
 mints an invite for an agent to pair into it. The agent's lasting key is an owner key for the engram
 it opened only; on the engram it works in it stays an agent. The agent's work in an engram its own
 key owns is never counted on its track record. From code: `EngramClient.getChildAllowance(key)`,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@engramx/client",
-  "version": "0.16.0-rc.17",
+  "version": "0.16.0-rc.18",
   "description": "Client SDK for EngramX — persistent, decentralized memory for AI agents on the Internet Computer",
   "license": "Apache-2.0",
   "author": "EngramX <developer@engramx.ai>",
@@ -53,7 +53,7 @@
     "@icp-sdk/core": "^6.1.0"
   },
   "dependencies": {
-    "@engramx/idl": "0.16.0-rc.17",
+    "@engramx/idl": "0.16.0-rc.18",
     "@icp-sdk/core": "^6.1.0",
     "@icp-sdk/vetkeys": "0.7.0",
     "@noble/curves": "^2.4.0"