chore: bump to eve 0.49.0, raise eve-extension peer floor to >=0.48.0

[upstash-tag]

eve's tool contribution contract moved twice since the repo's current 0.47.6 pin (22→23 in 0.47.7, 23→24 in 0.48.0). Rebuilding @upstash/agentkit-eve-extension against eve 0.49.0 re-stamps its manifest to tool 24, which makes the currently-declared eve peer floor (>=0.47.5) stale: eve 0.47.5, 0.47.6 and 0.47.7 all install cleanly and then fail eve build with "Selected module binding … has no compile or runtime usage." This raises the floor to >=0.48.0, the oldest eve verified end-to-end (packed dist into a real consumer app) to actually build the rebuilt manifest.

@upstash/agentkit-eve's peer floor (>=0.32.0) needed no change — its sandbox-backend type surface is byte-identical between 0.47.6 and 0.49.0, so SandboxBackendHandle gained no new required member.

Every eve pin in the repo (both packages' devDependency, both eve example apps) moves to ^0.49.0; install/build/typecheck/lint/tests/example-builds/mocked-model-eval all pass. The prior unreleased eve-extension-0476-rebuild changeset (from PR #31/#32, never actually published) is folded into a single changeset describing the final state relative to the last version that was published (0.8.0, built with eve 0.47.3, floor >=0.47.0), rather than left as a second, now-inaccurate pending entry. CLAUDE.md, the extension's README and AGENTS.md are updated to match, plus a note on the pnpm@11.5.3 manage-package-manager-versions setup gotcha hit while verifying this.

---

Built by upstash-tag · mission 6b4bdfb9-68c3-44cd-b235-bac3600b02a0 · chore/eve-0.49.0-upgrade → main · $9.24