fix(eve-extension): make agentkit()'s config argument optional

packages/eve-extension/AGENTS.md

@@ -15,6 +15,11 @@ unavailable, use https://eve.dev/docs/extensions as a fallback.
 - Declare the extension in `extension/extension.ts` with `defineExtension` from
   `eve/extension`. Config is optional; read bound values via the handle's
   `.config` in tools and hooks.
+  Note: even when every config *field* is optional, eve types the mount handle's
+  call signature as `(values: InferInput<S>)` — a **required** parameter — so
+  `agentkit()` fails `tsc` with TS2554 and docs must show `agentkit({})`. That
+  signature lives in the `eve` peer dep, not here; `.optional()` on the schema
+  does not fix it (it only makes `extension.config` possibly-undefined).
 - Add contributions under `extension/` the same way as in an agent:
   `tools/`, `channels/`, `connections/`, `skills/`, `schedules/`, `subagents/`,
   `hooks/`, and optional instruction fragments (eve ≥0.41 supports the full set;

packages/eve-extension/README.md

@@ -26,13 +26,13 @@ Set `UPSTASH_REDIS_REST_URL` / `UPSTASH_REDIS_REST_TOKEN` in your env (the exten
 
 ## Mount it
 
-Every field is optional. The smallest mount gives the agent memory tools:
+Every field is optional, so the smallest mount is an empty config — it gives the agent memory tools:
 
 ```ts
 // agent/extensions/agentkit.ts
 import agentkit from "@upstash/agentkit-eve-extension";
 
-export default agentkit();
+export default agentkit({});
 ```
 
 Add `search` to turn on the search tools over one index. The schema is built with `s` from