@haven_ai/connect 0.0.0-dev.202609031654.2309084 → 0.0.0-dev.202609031827.893d74f

package/README.md

@@ -478,3 +478,11 @@ To return to the pinned manifest: unset the variables and run
 `--doctor --repair --runtime <runtime>` (or re-run setup). The override
 directories live under `~/.haven` like every other runtime directory, so the
 same reset that removes `~/.haven` removes them.
+
+That is the loop for a build that has **not** merged. For one that has — a
+`@dev` snapshot of all five packages, published from every package-touching
+push to `dev` — and for the owner steps that make the dev dashboard hand out
+`npx -y @haven_ai/connect@dev …` in the first place, see the repository runbook
+[`docs/operations/package-dev-channel.md`](https://github.com/d-hinders/Haven-AI/blob/dev/docs/operations/package-dev-channel.md).
+The two compose: `@dev` picks the connector, these variables pick what it
+installs.

package/dist/cli.cjs

@@ -535,9 +535,9 @@ var init_runtime_manifest = __esm({
       mcpPackage: "@haven_ai/mcp",
       mcpVersion: mcp.MCP_VERSION,
       sdkPackage: "@haven_ai/sdk",
-      sdkVersion: "0.0.0-dev.202609031654.2309084",
+      sdkVersion: "0.0.0-dev.202609031827.893d74f",
       signerPackage: "@haven_ai/signer",
-      signerVersion: "0.0.0-dev.202609031654.2309084",
+      signerVersion: "0.0.0-dev.202609031827.893d74f",
       // 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
@@ -4270,7 +4270,7 @@ function defaultPromptIo() {
 // src/runtime.ts
 init_local_mcp_runtime();
 init_runtime_manifest();
-var CONNECTOR_VERSION = "0.0.0-dev.202609031654.2309084";
+var CONNECTOR_VERSION = "0.0.0-dev.202609031827.893d74f";
 var CONNECT_OUTCOME_SCHEMA_VERSION = 1;
 var failureOutcomesByError = /* @__PURE__ */ new WeakMap();
 function failureOutcomeFor(runtimeHint, error) {