fix(eve-extension)!: rebuild against eve 0.78.0, peer floor >=0.77.0; bump ai 7.0.138, @tanstack/ai 0.68.0

.changeset/eve-extension-eve-0-78.md

@@ -0,0 +1,10 @@
+---
+"@upstash/agentkit-eve-extension": minor
+---
+
+fix!: rebuild the extension against `eve` 0.78.0 and raise the `eve` peer floor to `>=0.77.0`
+
+`@upstash/agentkit-eve-extension@0.16.0` was built with eve 0.74.0 and stamps tool contract 78 / dynamicTool 73 /
+hook 39. This release is rebuilt on eve 0.78.0, whose manifest requires tool 86 / dynamicTool 81 / hook 45; eve
+0.76.3 and earlier do not support them (`Selected module binding "extensions/agentkit.ts" has no compile or runtime usage.`),
+so the `eve` peer floor moves from `>=0.74.0` to `>=0.77.0`.

CLAUDE.md

@@ -126,9 +126,9 @@ implements TanStack AI's own backend contracts (see its section below) — keep
   npm/yarn hoisted layouts — was fixed upstream in eve 0.25.3; no workaround needed on ≥0.25.3.)
   **Consumer eve version:** `eve extension build` stamps the manifest's `requires` with the building
   eve's *current* contribution-format versions, and a consumer rejects any version not in its own
-  supported list — the current dist, built with **eve 0.74.0**, stamps formatVersion 2; extension 1 /
-  **tool 78** / **dynamicTool 73** / **hook 39** / instructions 2 / config 1, which needs consumers on
-  **eve ≥0.74.0** — 0.74.0 is the first release accepting all three (0.72.0–0.73.0 refuse them: a pack of this dist built
+  supported list — the current dist, built with **eve 0.78.0**, stamps formatVersion 2; extension 1 /
+  **tool 86** / **dynamicTool 81** / **hook 45** / instructions 2 / config 1, which needs consumers on
+  **eve ≥0.77.0** — 0.77.0 is the first release accepting all three (0.74.0–0.76.3 refuse them; the previous dist, built with 0.74.0, stamped 78/73/39 with floor 0.74.0 and still builds on 0.78.0; 0.72.0–0.73.0 refuse 78/73/39: a pack of this dist built
   against 0.72.0/0.72.1/0.73.0 fails `eve build` with the obtuse "has no compile or runtime usage" error; the intermediate
   0.72.1 build stamped 76/72/38 with floor 0.72.0 and was never released; 0.72.0 **dropped tool 71–75**; the published dist, built with 0.69.0, stamped
   71/68/35 with floor 0.69.0 and fails on eve ≥0.72.0). Earlier: 0.69.0 was the first release accepting any of 71/68/35 (0.65.0–0.68.0 accept none
@@ -164,7 +164,7 @@ implements TanStack AI's own backend contracts (see its section below) — keep
   release's worth of headroom. Since ~0.50 eve also **drops** contracts out of the middle of its
   supported range, so a *newer* eve is not automatically compatible either: the floor has repeatedly
   landed on the pinned version itself, with **no back-compat window at all**.
-  The `eve` peer is **`">=0.74.0"`, not `"*"`** — issue #22 proved the wildcard is a trap: eve
+  The `eve` peer is **`">=0.77.0"`, not `"*"`** — issue #22 proved the wildcard is a trap: eve
   0.33 dropped hook contracts ≤9 *nine hours* after 0.32 shipped, so a wildcard install succeeds and
   then fails at `eve build` with a manifest error. The manifest is still the real compatibility tie;
   the peer floor is the install-time guard. **On every eve devDep bump: rebuild, read the new
@@ -888,7 +888,7 @@ implements TanStack AI's own backend contracts (see its section below) — keep
 
 ## Eve framework facts
 - **The repo is split (since 2026-09-30): `packages/eve-extension` + `examples/eve-extension-demo` are
-  on `eve@0.74.0` (extension peer `>=0.74.0`, since 2026-10-08; 0.70.0 / `>=0.70.0` and 0.72.1 / `>=0.72.0` were never released);
+  on `eve@0.78.0` (extension peer `>=0.77.0`, since 2026-10-13; 0.74.0 / `>=0.74.0` was the previous release; 0.70.0 / `>=0.70.0` and 0.72.1 / `>=0.72.0` were never released);
   `packages/eve` + `examples/eve-demo` stay on `eve@0.65.0` (peer `>=0.65.0`)** — see the 0.68.0 → 0.69.0
   and 0.65.0 → 0.68.0 bump notes below. Before that (2026-09-23)
   it was one `eve@0.65.0` everywhere, with both packages declaring `eve: ">=0.65.0"`. (For one
@@ -1075,6 +1075,13 @@ implements TanStack AI's own backend contracts (see its section below) — keep
   implementation needed **no** new member for 0.55.0 — `pnpm typecheck` is clean across all four packages.
   Even the extension's compiled output is unchanged: **`_manifest.json` is the only file in
   `packages/eve-extension/dist` that differs from published `0.10.0`.**
+- **The 0.74.0 → 0.78.0 bump (2026-10-13) is EXTENSION-ONLY again.** `packages/eve` + `examples/eve-demo` stay on 0.65.0: eve 0.75.0 renamed the
+  sandbox handle hooks `onSessionStop`/`onSessionDelete` → `onSandboxStop`/`onSandboxDelete` and dropped `MutableNetworkSandboxSession`
+  (`TS2305` + `TS2353` in `src/sandbox.ts`, `sandbox.test.ts`; needs a source change). The rebuild re-stamps **tool 78→86, dynamicTool 73→81,
+  hook 39→45**; read off by building the packed dist against a consumer on each of 0.74.0/0.75.0/0.75.1/0.76.0/0.76.2/0.76.3/0.77.0/0.78.0, only
+  0.77.0+ mounts it, so the floor moved `>=0.74.0` → **`>=0.77.0`**. Published 0.16.0 (78/73/39) still builds clean on 0.78.0.
+  Also bumped: `ai` 7.0.138, `@tanstack/ai` 0.68.0, `-client` 0.39.2, `-memory` 0.2.13, `-openai` 0.29.1, `-react` 0.30.3; `@tanstack/ai-persistence`
+  still held at 0.7.2 (its 0.8.x conformance suite requires an `activities` store or `skip: ['activities']`).
 - **The 0.72.1 → 0.74.0 bump (2026-10-08) is EXTENSION-ONLY again** (same reason: `packages/eve` still imports the removed
   `MutableNetworkSandboxSession`, `TS2305` in `src/sandbox.ts`/`sandbox.test.ts` on 0.74.0; `packages/eve` + `examples/eve-demo` stay on 0.65.0). The rebuild re-stamps
   **tool 76→78, dynamicTool 72→73, hook 38→39**; only 0.74.0 accepts them (verified by building the packed dist against a consumer on each of

examples/ai-sdk-demo/package.json

@@ -13,7 +13,7 @@
     "@upstash/agentkit-ai-sdk": "workspace:*",
     "@upstash/agentkit-sdk": "workspace:*",
     "@upstash/redis": "^1.38.4",
-    "ai": "7.0.133",
+    "ai": "7.0.138",
     "dotenv": "^16.4.5",
     "next": "16.2.9",
     "react": "19.2.6",

examples/eve-demo/package.json

@@ -28,7 +28,7 @@
     "@upstash/box": "^0.7.5",
     "@upstash/redis": "^1.38.4",
     "@vercel/connect": "0.2.2",
-    "ai": "7.0.133",
+    "ai": "7.0.138",
     "class-variance-authority": "0.7.1",
     "clsx": "2.1.1",
     "cmdk": "1.1.1",

examples/eve-extension-demo/package.json

@@ -18,8 +18,8 @@
     "@upstash/agentkit-eve-extension": "workspace:*",
     "@upstash/redis": "^1.38.4",
     "@vercel/connect": "0.2.2",
-    "ai": "7.0.133",
-    "eve": "^0.74.0",
+    "ai": "7.0.138",
+    "eve": "^0.78.0",
     "zod": "4.4.3"
   },
   "devDependencies": {

examples/tanstack-ai-demo/package.json

@@ -10,12 +10,12 @@
     "e2e": "vitest run --config e2e/vitest.config.ts"
   },
   "dependencies": {
-    "@tanstack/ai": "0.65.1",
-    "@tanstack/ai-client": "0.38.0",
-    "@tanstack/ai-memory": "0.2.10",
-    "@tanstack/ai-openai": "0.27.0",
+    "@tanstack/ai": "0.68.0",
+    "@tanstack/ai-client": "0.39.2",
+    "@tanstack/ai-memory": "0.2.13",
+    "@tanstack/ai-openai": "0.29.1",
     "@tanstack/ai-persistence": "0.7.2",
-    "@tanstack/ai-react": "0.30.0",
+    "@tanstack/ai-react": "0.30.3",
     "@upstash/agentkit-tanstack-ai": "workspace:*",
     "@upstash/redis": "^1.38.4",
     "next": "16.2.9",

packages/ai-sdk/package.json

@@ -53,7 +53,7 @@
     "@ai-sdk/openai": "^4.0.71",
     "@ai-sdk/provider": "^4.0.17",
     "@upstash/redis": "^1.38.4",
-    "ai": "7.0.133",
+    "ai": "7.0.138",
     "dotenv": "^16.4.5"
   },
   "peerDependencies": {

packages/eve-extension/AGENTS.md

@@ -37,7 +37,7 @@ unavailable, use https://eve.dev/docs/extensions as a fallback.
 agent-shaped source tree into `dist/extension/`, emits type declarations and a
 compatibility manifest, and fills the package `exports` map. Ship `dist/` only.
 `eve` is a required peer so the consumer's eve is the one that runs, but NOT a
-wildcard: keep the floor (`>=0.74.0`) in sync with what the built manifest's
+wildcard: keep the floor (`>=0.77.0`) in sync with what the built manifest's
 contracts require, so an incompatible eve fails at install instead of at
 `eve build` (see issue #22). eve validates the real compatibility from the
 generated manifest.

packages/eve-extension/README.md

@@ -15,7 +15,7 @@ no repeated schemas; upgrades come through the package manager.
 
 `<ns>` is the mount file's basename — the examples below use `agentkit`.
 
-Start from an eve project (eve ≥ 0.74.0 — the prebuilt extension is built with eve 0.74.0 and its compatibility manifest requires tool contract v78 (dynamicTool v73, hook v39), which eve 0.74.0 is the first release to support; the package declares this as its `eve` peer range), then:
+Start from an eve project (eve ≥ 0.77.0 — the prebuilt extension is built with eve 0.78.0 and its compatibility manifest requires tool contract v86 (dynamicTool v81, hook v45), which eve 0.77.0 is the first release to support; the package declares this as its `eve` peer range), then:
 
 ```bash
 pnpm add @upstash/agentkit-eve-extension

packages/eve-extension/package.json

@@ -56,10 +56,10 @@
   },
   "devDependencies": {
     "@types/node": "24.x",
-    "eve": "^0.74.0",
+    "eve": "^0.78.0",
     "typescript": "7.0.2"
   },
   "peerDependencies": {
-    "eve": ">=0.74.0"
+    "eve": ">=0.77.0"
   }
 }

packages/eve/package.json

@@ -60,7 +60,7 @@
   "devDependencies": {
     "@upstash/box": "^0.7.5",
     "@upstash/redis": "^1.38.4",
-    "ai": "7.0.133",
+    "ai": "7.0.138",
     "dotenv": "^16.4.5",
     "eve": "^0.65.0"
   },

packages/tanstack-ai/package.json

@@ -58,8 +58,8 @@
     "zod": "^3.23.8 || ^4"
   },
   "devDependencies": {
-    "@tanstack/ai": "0.65.1",
-    "@tanstack/ai-memory": "0.2.10",
+    "@tanstack/ai": "0.68.0",
+    "@tanstack/ai-memory": "0.2.13",
     "@tanstack/ai-persistence": "0.7.2",
     "dotenv": "^16.4.5",
     "@upstash/blob": "0.0.7"