@zackbart/connecta-eve 0.38.0 → 0.40.0

package/README.md

@@ -4,15 +4,16 @@ Connect an Eve agent to a Connecta agent pool and load its endpoint instructions
 once per turn. The helper runs in the Eve app; the Connecta server
 runs separately. No `@zackbart/connecta` dependency is installed by this package.
 
-Requires **Node 24+** and **Eve >=0.86.0 <0.87.0**. Development and consumer
-checks use real Eve 0.86.0. The range covers its patch line; newer minor releases
-need a compatibility check. Helper releases share Connecta's version and tag;
-choose the helper version matching your server release.
+Requires **Node 24+** and **Eve 1.0.0-rc.1**. Development and consumer
+checks use that exact release candidate. The peer stays pinned during the RC
+period; later candidates and stable 1.0 need a compatibility check. Helper
+releases share Connecta's version and tag; choose the helper version matching
+your server release.
 
 ## Install and add two files
 
 ```sh
-npm install @zackbart/connecta-eve eve@0.86.0
+npm install @zackbart/connecta-eve eve@1.0.0-rc.1
 ```
 
 The server must declare your agent, admit it to the named pool and issue its
@@ -89,22 +90,48 @@ Each selected name must match `[a-z0-9_-]+`. A throwing selector or an invalid
 name fails the turn, even when guidance is cached. Handle lookup failures in
 your selector if it should fall back to a least-privileged pool.
 
-## Eve 0.86.0 dependency override
-
-Eve 0.86.0 pins undici 8.10.2. Connecta's development/test override does not ship
-with this helper, so the Eve app must apply its own override to 8.12.3 before
-installing. For an npm app, add this to its `package.json`, then reinstall and
-commit the lockfile:
-
-```json
-{ "overrides": { "eve": { "undici": "8.12.3" } } }
-```
-
-For a pnpm app, add `overrides: { "eve@0.86.0>undici": "8.12.3" }` to its
-`pnpm-workspace.yaml`. Check the resolved dependency graph and audit the app.
-Remove this override after upgrading to an Eve release that pins a fixed version
-and validating compatibility. The server's optional undici 6.29.1 peer is a
-separate dependency and keeps its exact pin.
+## Upgrading to Eve 1.0 RC
+
+Update the app to `eve@1.0.0-rc.1` and reinstall to refresh its lockfile.
+The helper's connection, dynamic pool, instructions and approval APIs use Eve's
+stable entry points and require no authoring changes for this RC. Eve's
+[1.0 stability policy](https://eve.dev/docs/reference/typescript-api#stability-policy)
+does not cover `experimental` fields or internal modules.
+
+From 0.90, review the intervening
+[release notes](https://github.com/vercel/eve/blob/eve%401.0.0-rc.1/packages/eve/CHANGELOG.md):
+`session.clear()` now cancels running turns and tasks, and object-form connection
+approvals are now preserved at runtime. RC.1 also requires `@vercel/connect`
+`^2.7.0` when that optional integration is installed; older Connect releases
+reject the prerelease Eve peer.
+
+For older apps, follow Eve's [Upgrade to 1.0](https://eve.dev/docs/guides/upgrade)
+guide for event consumers, saved history, extensions and client APIs.
+Build and test the app before deploying it. The helper does not migrate those
+app-owned surfaces.
+
+## Upgrading from Eve 0.86
+
+Eve 0.88.1 and later pin undici 8.12.3, so the app no longer needs its own undici
+override. Remove `"eve": { "undici": "8.12.3" }` from an npm app's `overrides`, or
+`"eve@0.86.0>undici": "8.12.3"` from a pnpm app's `pnpm-workspace.yaml`, then
+reinstall, commit the lockfile and audit the app. The server's optional undici
+6.29.1 peer is a separate dependency and keeps its exact pin.
+
+Eve 0.87 through 0.90 also changed app code the helper does not own. Review every
+intervening release in the
+[Eve 0.90.0 changelog](https://raw.githubusercontent.com/vercel/eve/refs/tags/eve%400.90.0/packages/eve/CHANGELOG.md);
+an app on Eve 0.84 or 0.85 must also review those releases. Notable changes:
+
+- Builds reject connection definitions not made by Eve's own factories, and
+  `defineDynamic()` values are opaque (0.87). `connectaConnection()` and
+  `connectaInstructions()` already return values made by Eve's factories.
+- Several client, workflow and channel APIs moved (0.87).
+- Grant-bearing `vercelOidc` auth becomes `eveVercelOidc`, auth callbacks that
+  returned `allowToolStubs` become `EveAuthFn`, and `/info` access is restricted
+  (0.90). Identity-only `vercelOidc()` calls need no rename.
+
+Build and test the app on the new Eve before deploying it.
 
 ## Approval and writes
 
@@ -176,9 +203,9 @@ custom audience, even when Vercel signed them.
 
 In a source checkout with dependencies installed and both packages built, run
 `pnpm --filter @zackbart/connecta-eve run probe:catalog --output /absolute/path/outside/checkout`
-on Node 24. This boots real Eve 0.86.0 with a packed, installed helper against
+on Node 24. This boots real Eve 1.0.0-rc.1 with a packed, installed helper against
 seeded local catalogs of 40, 100, 250, 500, and 1,000 downstream tools on the
-meta, native, and native-plus-code surfaces. Native listings include two
+meta, native, and native-plus-code surfaces. Native listings include three
 Connecta tools beyond the downstream count. A 1,001-tool native catalog must
 refuse listing. `--counts 40,1000` selects a smaller matrix.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zackbart/connecta-eve",
-  "version": "0.38.0",
+  "version": "0.40.0",
   "type": "module",
   "sideEffects": false,
   "description": "Eve connection and instructions helpers for Connecta agent endpoints.",
@@ -28,11 +28,11 @@
     }
   },
   "peerDependencies": {
-    "eve": ">=0.86.0 <0.87.0"
+    "eve": "1.0.0-rc.1"
   },
   "devDependencies": {
     "@types/node": "^24.19.2",
-    "eve": "0.86.0",
+    "eve": "1.0.0-rc.1",
     "typescript": "^6.0.3",
     "vite": "^8.3.4",
     "vitest": "^5.0.4"