@haven_ai/connect 0.0.0-dev.202610240100.6d87ddf → 0.0.0-dev.202610240456.b79b112

package/README.md

@@ -655,7 +655,8 @@ refused, because their derived names would collide with another pair's.
 > browser ([#1878](https://github.com/d-hinders/Haven-AI/issues/1878)). It is a
 > label, not authority — nothing keys off it.
 >
-> Agents connected before that shipped read **"MCP name not recorded"**: Haven
+> Agents connected before that shipped show **not recorded** in the *MCP server
+> name* row of their Settings tab: Haven
 > genuinely does not know, and guessing would name the wrong pair for anyone who
 > used `--name`. They keep working exactly as they are; `--doctor` on the machine
 > still maps them, and reconnecting records the name.

package/dist/cli.cjs

@@ -276,9 +276,9 @@ var init_runtime_manifest = __esm({
       mcpPackage: "@haven_ai/mcp",
       mcpVersion: mcp.MCP_VERSION,
       sdkPackage: "@haven_ai/sdk",
-      sdkVersion: "0.0.0-dev.202610240100.6d87ddf",
+      sdkVersion: "0.0.0-dev.202610240456.b79b112",
       signerPackage: "@haven_ai/signer",
-      signerVersion: "0.0.0-dev.202610240100.6d87ddf",
+      signerVersion: "0.0.0-dev.202610240456.b79b112",
       // Sourced from the SDK, never a literal (#1161). This field read '20.0.0'
       // while every package's `engines` said `>=24` and the docs said `>=24.0.0`,
       // so the guard that was supposed to enforce the floor waved Node v23 through
@@ -4703,7 +4703,7 @@ var init_runtime = __esm({
     init_tombstone();
     init_local_mcp_runtime();
     init_runtime_manifest();
-    CONNECTOR_VERSION = "0.0.0-dev.202610240100.6d87ddf";
+    CONNECTOR_VERSION = "0.0.0-dev.202610240456.b79b112";
     PRODUCTION_CHAIN_ID = 8453;
     UUID_SHAPE = /^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$/i;
     CONNECTOR_CLIENT_IDENTITY = `@haven_ai/connect/${CONNECTOR_VERSION}`;