@iicp/client 0.7.106 → 0.7.108

package/README.md

@@ -35,7 +35,7 @@ npm install @iicp/client@latest
 ## One-line test
 
 ```bash
-npm install -g @iicp/client@latest
+npm install -g @iicp/client@0.7.107 --registry=https://registry.npmjs.org
 iicp-node query "Hello, mesh."
 ```
 
@@ -44,7 +44,7 @@ What good looks like:
 ```bash
 iicp-node --help       # shows query, serve, proxy, mcp-gateway, credits, ...
 which iicp-node        # points to your Node/npm environment
-iicp-node --version    # prints iicp-node 0.7.106 or newer
+iicp-node --version    # prints iicp-node 0.7.108 or newer
 ```
 
 The query command contacts the public directory, discovers a matching live node,
@@ -88,6 +88,18 @@ them. The context is rebuilt on fallback, never includes endpoints, tokens,
 node identities, candidate sets or scores, and is not a prompt-injection
 security boundary.
 
+## Restricted trust-domain verification foundation
+
+The package exports strict, fixture-backed verifiers for the pre-normative
+restricted trust-domain membership and authenticated-gossip envelopes. They
+validate bounded Ed25519/JCS assertions and fail closed on malformed,
+expired, revoked-generation, wrong-domain or replayed evidence.
+
+This is a verification foundation, not a claim that the TypeScript runtime
+already provides complete private/CUG operation. Peer admission, credential
+lifecycle, private discovery, no-public-fallback behavior and supervised
+restart evidence remain separate integration work.
+
 Raw `submit()` calls and non-chat intents are unchanged. Disable or require the
 chat context explicitly:
 
@@ -146,6 +158,17 @@ not silently fall back to anonymous dispatch if consumer-token acquisition
 fails. The default remains `"optional"`; `"disabled"` skips token
 acquisition.
 
+### Restricted trust-domain directories
+
+Restricted operation is opt-in and fail closed. Supply a
+`restricted_directory` context with membership material resolved from an
+environment variable or a caller-owned provider function. The SDK does not
+persist that material in browser storage. It sends the credential only to the
+configured directory, refuses redirects and legacy discovery fallback, and
+accepts candidates or tokens only after a matching, current operation decision.
+Public behavior is unchanged when the context is absent. Peer-gossip and CIP
+worker participation are not part of this SDK surface.
+
 ### Experimental local candidate rankers
 
 Library users may attach a `CandidateRanker` to test a learned or
@@ -178,7 +201,7 @@ const reply = await new IicpClient().chat([
 Existing OpenAI-compatible tools:
 
 ```bash
-npm install -g @iicp/client@latest
+npm install -g @iicp/client@0.7.107 --registry=https://registry.npmjs.org
 iicp-node proxy
 export OPENAI_BASE_URL=http://127.0.0.1:9483/v1
 ```
@@ -188,7 +211,7 @@ base URL. Full guide: <https://iicp.network/docs/proxy>
 
 ## Keep provider nodes current
 
-The current public release line is **0.7.106**. Upgrade through your package
+The current public release line is **0.7.108**. Upgrade through your package
 manager before troubleshooting an older installation. Routing profiles can
 refuse remote dispatch before a prompt leaves the client; use `sensitive` for
 local-only work, `eu-restricted` for EU/EEA routing, or `strict-policy` when a
@@ -196,8 +219,12 @@ no-retention policy manifest is required.
 
 Provider nodes run an hourly official-registry check by default
 (`IICP_AUTO_UPDATE=1`, `IICP_AUTO_UPDATE_INTERVAL_S=3600`; minimum 300s).
+Failed candidates use persisted, bounded retry backoff (up to 24 hours) instead
+of being reinstalled every check. The non-sensitive retry status is stored under
+`$IICP_HOME/state/update-status.json`; `IICP_UPDATE_STATE_FILE` overrides that
+path for managed or test environments.
 When npm publishes a newer stable release, `serve` runs
-`npm install -g @iicp/client@latest` and re-execs the node so identity and cached
+`npm install -g @iicp/client@X.Y.Z --registry=https://registry.npmjs.org` and re-execs the node so identity and cached
 node tokens are preserved.
 
 If an older supervised node does not update itself, perform one manual upgrade
@@ -659,6 +686,7 @@ npm run build      # emit to dist/
 - [Agent bootstrap guide](https://github.com/RobLe3/IICP/blob/main/docs/agent-bootstrap.md) — connect a consumer or provider agent
 - [Implementation registry](https://github.com/RobLe3/IICP/blob/main/IMPLEMENTATIONS.md) — supported and preview components
 - [Node setup guide](https://iicp.network/docs/node-setup) — run your own node
+- [CLI examples](https://iicp.network/docs/cli-examples) — copyable `iicp-node` tasks and operator recipes
 - [Error reference](https://iicp.network/docs/error-reference) — all error codes
 - [iicp-client-python](https://github.com/RobLe3/iicp-client-python) — Python SDK
 - [iicp-client-rust](https://github.com/RobLe3/iicp-client-rust) — Rust SDK

package/dist/cli.js

@@ -80,7 +80,7 @@ function startProviderAutoUpdate(options = {}) {
         const tick = () => {
             void (async () => {
                 try {
-                    await u.autoUpdateTick(current, await u.latestNpmVersion(), true, () => u.performSelfUpdate(), () => u.reexecCli(), logFn);
+                    await u.autoUpdateTick(current, await u.latestNpmVersion(), true, (version) => u.performSelfUpdate(version), () => u.reexecCli(), logFn);
                 }
                 catch (err) {
                     u.recordUpdateCheck(null, err instanceof Error ? err.name : "Error");