chore: bump eve to 0.77.0 (extension rebuilt, peer floor >=0.77.0); supersedes #64

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

@@ -0,0 +1,10 @@
+---
+"@upstash/agentkit-eve-extension": minor
+---
+
+fix!: rebuild the extension against `eve` 0.77.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.77.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.77.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.76.3 and earlier refuse them; an intermediate dist built with 0.76.3 stamped 85/79/44 with floor 0.76.2 and was never released; 0.76.0 and 0.75.x refuse those too with the same obtuse "has no compile or runtime usage" error; an intermediate dist built with 0.75.1 stamped 80/75/41 with floor 0.75.0 and was never released; 0.74.0 and earlier refuse these too, e.g. 0.74.0 fails `eve build` with the obtuse "has no compile or runtime usage" error; the previous dist, built with 0.74.0, stamped 78/73/39 with floor 0.74.0 — 0.72.0–0.73.0 refuse those too: 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.77.0` (extension peer `>=0.77.0`, since 2026-10-12; 0.76.3 / `>=0.76.2` was never released; 0.76.0 / `>=0.76.0` was never released; 0.75.1 / `>=0.75.0` was never released; 0.74.0 / `>=0.74.0` was the previous floor; 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,14 @@ 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`.**
+- **Update 2026-10-12: eve 0.77.0 re-stamps to tool 86 / dynamicTool 81 / hook 45, which 0.76.3 refuses; the extension dist is rebuilt on 0.77.0 with floor `>=0.77.0` (published 0.16.0 still builds clean on 0.77.0, verified in a fresh consumer; `packages/eve` + `examples/eve-demo` remain on 0.65.0, see below).**
+- **The 0.74.0 → 0.76.0 bump (2026-10-10; first built against 0.75.1 on 2026-10-09) is EXTENSION-ONLY again. Update 2026-10-11: eve 0.76.2/0.76.3 re-stamp again to tool 85 / dynamicTool 79 / hook 44, which eve 0.76.0 refuses; the dist is rebuilt on 0.76.3 and the floor is now `>=0.76.2` (published 0.16.0 still builds clean on 0.76.3).** The 0.76.0 rebuild re-stamps **tool 80→84, dynamicTool 75→77, hook 41→43**; a consumer on 0.75.0 or 0.75.1 fails `eve build` with the packed dist ("has no compile or runtime usage"), 0.76.0 mounts clean, so the floor is **`>=0.76.0`** (published 0.16.0 78/73/39 still builds clean on 0.76.0; `packages/eve` on 0.76.0 still fails `TS2305`/`TS7006` in `src/sandbox.ts:63,334`). The 0.75.1 notes follow. `packages/eve` + `examples/eve-demo` stay on 0.65.0: besides the long-known
+  `MutableNetworkSandboxSession` removal (`TS2305`), eve 0.75.0 renamed the sandbox provider handle hooks `onSessionStop`/`onSessionDelete` →
+  `onSandboxStop`/`onSandboxDelete` (and added `onSessionEnd`); on 0.75.1 `src/sandbox.ts` fails with `TS2353` at `createHandle`, plus implicit-any
+  cascades. Needs a source change. The extension rebuild re-stamps **tool 78→80, dynamicTool 73→75, hook 39→41**; a consumer on 0.74.0 fails
+  `eve build` with the packed dist, 0.75.0 and 0.75.1 mount clean, so the floor moved `>=0.74.0` → **`>=0.75.0`**. Published 0.16.0 (78/73/39) still
+  builds clean on 0.75.1. Also bumped: `ai` 7.0.136, `@tanstack/ai` 0.66.0, `-memory` 0.2.11, `-client` 0.39.0, `-openai` 0.28.0, `-react` 0.30.1,
+  `@upstash/box` ^0.7.9; `@tanstack/ai-persistence` still held at 0.7.2 (0.8.1 and 0.8.3: the conformance kit still requires an `activities` store — `AIPersistence conformance: store 'activities' is missing`). 2026-10-10 re-bump: `ai` 7.0.137, `@tanstack/ai` 0.68.0, `-memory` 0.2.13, `-client` 0.39.2, `-openai` 0.29.1, `-react` 0.30.3, `@ai-sdk/openai` ^4.0.91, `@ai-sdk/provider` ^4.0.26.
 - **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

@@ -8,12 +8,12 @@
     "start": "next start"
   },
   "dependencies": {
-    "@ai-sdk/openai": "^4.0.71",
+    "@ai-sdk/openai": "^4.0.91",
     "@ai-sdk/react": "^4.0.110",
     "@upstash/agentkit-ai-sdk": "workspace:*",
     "@upstash/agentkit-sdk": "workspace:*",
     "@upstash/redis": "^1.38.4",
-    "ai": "7.0.133",
+    "ai": "7.0.137",
     "dotenv": "^16.4.5",
     "next": "16.2.9",
     "react": "19.2.6",

examples/eve-demo/package.json

@@ -14,7 +14,7 @@
     "typecheck": "tsgo --noEmit -p tsconfig.json"
   },
   "dependencies": {
-    "@ai-sdk/openai": "^4.0.71",
+    "@ai-sdk/openai": "^4.0.91",
     "@radix-ui/react-use-controllable-state": "1.2.2",
     "@shikijs/core": "4.1.0",
     "@shikijs/engine-javascript": "4.1.0",
@@ -25,10 +25,10 @@
     "@streamdown/mermaid": "1.0.2",
     "@tailwindcss/postcss": "4.3.0",
     "@upstash/agentkit-eve": "workspace:*",
-    "@upstash/box": "^0.7.5",
+    "@upstash/box": "^0.7.9",
     "@upstash/redis": "^1.38.4",
     "@vercel/connect": "0.2.2",
-    "ai": "7.0.133",
+    "ai": "7.0.137",
     "class-variance-authority": "0.7.1",
     "clsx": "2.1.1",
     "cmdk": "1.1.1",

examples/eve-extension-demo/package.json

@@ -14,12 +14,12 @@
     "typecheck": "tsc"
   },
   "dependencies": {
-    "@ai-sdk/openai": "^4.0.71",
+    "@ai-sdk/openai": "^4.0.91",
     "@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.137",
+    "eve": "^0.77.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

@@ -50,10 +50,10 @@
     "zod": "^3.23.8 || ^4"
   },
   "devDependencies": {
-    "@ai-sdk/openai": "^4.0.71",
-    "@ai-sdk/provider": "^4.0.17",
+    "@ai-sdk/openai": "^4.0.91",
+    "@ai-sdk/provider": "^4.0.26",
     "@upstash/redis": "^1.38.4",
-    "ai": "7.0.133",
+    "ai": "7.0.137",
     "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.77.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.77.0",
     "typescript": "7.0.2"
   },
   "peerDependencies": {
-    "eve": ">=0.74.0"
+    "eve": ">=0.77.0"
   }
 }

packages/eve/package.json

@@ -58,9 +58,9 @@
     "zod": "^3.23.8 || ^4"
   },
   "devDependencies": {
-    "@upstash/box": "^0.7.5",
+    "@upstash/box": "^0.7.9",
     "@upstash/redis": "^1.38.4",
-    "ai": "7.0.133",
+    "ai": "7.0.137",
     "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"