@haven_ai/connect 0.0.0-dev.202609050705.51c3d92 → 0.0.0-dev.202609050932.747d815

package/README.md

@@ -7,6 +7,17 @@ signing key and API key locally, stores them locally, and sends Haven only the
 public signing address, proof signature, and API-key hash. Haven never receives
 the private key or plaintext API key.
 
+## Are you an AI agent whose user has no Haven account yet?
+
+Read **`/for-agents.md`** on the Haven host your user gave you — or
+[the copy in this repository](https://github.com/d-hinders/Haven-AI/blob/dev/packages/frontend/public/for-agents.md)
+if you do not have that host yet.
+
+Your user creates the account and the passkey: those are theirs, they need a
+human, and you should never ask for their password. You can do everything else
+— including running the connector command from the setup prompt they paste you,
+and managing the account from the shell with `@haven_ai/cli`.
+
 ```sh
 npx -y @haven_ai/connect@<channel> --setup hv_setup_... --api https://api.haven.example --ack-local-tools --runtime claude-code
 ```
@@ -296,7 +307,7 @@ already-configured machine behaves as follows (characterized in
 `storage.test.ts`, `config-writers.test.ts`, `runtime.test.ts`, and
 `runtime-install.test.ts`, #1544/#1569):
 
-- **Re-running an already-consumed setup command** fails cleanly before any
+- **Re-running an already-consumed connector command** fails cleanly before any
   credential file or runtime configuration is touched — Haven refuses the
   consumed setup when Connect resolves it (or, in a rare concurrent-run race,
   at registration). The key pair minted for the attempt exists only in memory
@@ -523,7 +534,7 @@ HAVEN_SIGNER_SPEC=file:$PWD/packages/signer npx @haven_ai/connect@<channel> --se
 Environment variables rather than a flag, deliberately: the install runs from
 three entry points (`--setup`, `--doctor --repair`, `--rekey-finish`) and all
 three honour the same variables, so a re-key cannot silently reinstall the
-registry build; and the setup command is minted by the dashboard and pasted
+registry build; and the connector command is minted by the dashboard and pasted
 verbatim, often by an agent, so the override sits beside it instead of being
 spliced into a line the developer did not write.
 

package/dist/cli.cjs

@@ -536,9 +536,9 @@ var init_runtime_manifest = __esm({
       mcpPackage: "@haven_ai/mcp",
       mcpVersion: mcp.MCP_VERSION,
       sdkPackage: "@haven_ai/sdk",
-      sdkVersion: "0.0.0-dev.202609050705.51c3d92",
+      sdkVersion: "0.0.0-dev.202609050932.747d815",
       signerPackage: "@haven_ai/signer",
-      signerVersion: "0.0.0-dev.202609050705.51c3d92",
+      signerVersion: "0.0.0-dev.202609050932.747d815",
       // 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
@@ -4389,7 +4389,7 @@ async function pathExists2(path) {
 init_unwire();
 init_local_mcp_runtime();
 init_runtime_manifest();
-var CONNECTOR_VERSION = "0.0.0-dev.202609050705.51c3d92";
+var CONNECTOR_VERSION = "0.0.0-dev.202609050932.747d815";
 var CONNECT_OUTCOME_SCHEMA_VERSION = 1;
 var failureOutcomesByError = /* @__PURE__ */ new WeakMap();
 function failureOutcomeFor(runtimeHint, error) {