@haven_ai/connect 0.7.0-alpha.0 → 0.8.1-alpha.0

package/README.md

@@ -392,7 +392,8 @@ also yields one rather than failing a completed setup.
 
 **The dashboard offers the revoke, never the connector (#2561).** The same ids
 now ride the install-status report, so the Haven dashboard can put a
-one-click revoke next to the setup that displaced them. The connector does not
+revoke next to the setup that displaced them; it also ends the agent's budget
+with one owner signature (#3542). The connector does not
 and must not do it: `POST /agents/:id/revoke` is owner-authenticated, and an
 agent credential retiring a sibling agent is the "agent editing its own
 authority" the re-key routes refuse. Nothing is revoked automatically — the
@@ -516,9 +517,9 @@ already-configured machine behaves as follows (characterized in
     refuses with `wiring_collision` — nothing written, token still unused —
     naming the superseded agent ids and the two flags that resolve it. The
     refusal is written as a **relay instruction**: an agent running the
-    dashboard's command may append only `--json` (and `--runtime` after a
-    runtime refusal), so it must hand the choice to its user rather than add
-    a flag itself, and re-run only with the flag the user picks.
+    dashboard's command must hand the choice to its user rather than add a
+    flag itself. The setup prompt then permits one re-run with the flag the
+    user picks (#3689), on top of `--json` and a `--runtime` retry.
   - **`--replace`** is the unattended answer "yes, replace". `--name <slug>`
     installs alongside. Passing both is a usage error — they contradict.
 - **Replacing re-points the bare pair, then retires the previous directory

package/dist/cli.cjs

@@ -620,9 +620,9 @@ var init_runtime_manifest = __esm({
       mcpPackage: "@haven_ai/mcp",
       mcpVersion: mcp.MCP_VERSION,
       sdkPackage: "@haven_ai/sdk",
-      sdkVersion: "0.7.0-alpha.0",
+      sdkVersion: "0.8.1-alpha.0",
       signerPackage: "@haven_ai/signer",
-      signerVersion: "0.7.0-alpha.0",
+      signerVersion: "0.8.1-alpha.0",
       // 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
@@ -4451,7 +4451,7 @@ var init_runtime = __esm({
     init_tombstone();
     init_local_mcp_runtime();
     init_runtime_manifest();
-    CONNECTOR_VERSION = "0.7.0-alpha.0";
+    CONNECTOR_VERSION = "0.8.1-alpha.0";
     CONNECTOR_CLIENT_IDENTITY = `@haven_ai/connect/${CONNECTOR_VERSION}`;
     CONNECT_OUTCOME_SCHEMA_VERSION = 1;
     failureOutcomesByError = /* @__PURE__ */ new WeakMap();
@@ -4976,19 +4976,18 @@ async function discoverCredentialDirectory(homeDir, explicit) {
   const parkedOnly = [];
   for (const entry of entries) {
     const directory = path.join(root, entry);
+    if (await pathExists3(path.join(directory, TOMBSTONE_FILENAME))) {
+      tombstonedOnly.push(directory);
+      continue;
+    }
     try {
       const s = await promises.stat(path.join(directory, "identity.json"));
       candidates.push({ directory, mtimeMs: s.mtimeMs });
     } catch {
       try {
-        await promises.stat(path.join(directory, TOMBSTONE_FILENAME));
-        tombstonedOnly.push(directory);
+        await promises.stat(path.join(directory, REKEY_PENDING_FILENAME));
+        parkedOnly.push(directory);
       } catch {
-        try {
-          await promises.stat(path.join(directory, REKEY_PENDING_FILENAME));
-          parkedOnly.push(directory);
-        } catch {
-        }
       }
     }
   }