High-severity CVEs via pnpm audit

Describe the bug
Migration https://github.com/modelcontextprotocol/typescript-sdk/pull/1074 introduced vite as a mandatory peer dep of vitest. The currently locked vite@7.3.0 has two high-severity CVEs (https://github.com/advisories/GHSA-v2wj-q39q-566r, https://github.com/advisories/GHSA-p9ff-h696-f583), patched in ≥7.3.2. pnpm.overrides does not force the resolution for peer deps, so pnpm audit --audit-level=high fails on a clean checkout with no workaround short of adding vite as an explicit devDependency. Jest didn't have this problem — no bundler in the dep tree.

Technical details: https://github.com/modelcontextprotocol/typescript-sdk/issues/2042

To Reproduce
Steps to reproduce the behavior:

1. Run pnpm audit --audit-level=high
2. Outcome:

pnpm audit --audit-level=high
┌─────────────────────┬────────────────────────────────────────────────────────┐
│ high                │ Vite: `server.fs.deny` bypassed with queries           │
├─────────────────────┼────────────────────────────────────────────────────────┤
│ Package             │ vite                                                   │
├─────────────────────┼────────────────────────────────────────────────────────┤
│ Vulnerable versions │ >=7.1.0 <=7.3.1                                        │
├─────────────────────┼────────────────────────────────────────────────────────┤
│ Patched versions    │ >=7.3.2                                                │
├─────────────────────┼────────────────────────────────────────────────────────┤
│ Paths               │ .>vitest>vite                                          │
│                     │                                                        │
│                     │ common__vitest-config>vite-tsconfig-paths>vite         │
├─────────────────────┼────────────────────────────────────────────────────────┤
│ More info           │ https://github.com/advisories/GHSA-v2wj-q39q-566r      │
└─────────────────────┴────────────────────────────────────────────────────────┘
┌─────────────────────┬────────────────────────────────────────────────────────┐
│ high                │ Vite Vulnerable to Arbitrary File Read via Vite Dev    │
│                     │ Server WebSocket                                       │
├─────────────────────┼────────────────────────────────────────────────────────┤
│ Package             │ vite                                                   │
├─────────────────────┼────────────────────────────────────────────────────────┤
│ Vulnerable versions │ >=7.0.0 <=7.3.1                                        │
├─────────────────────┼────────────────────────────────────────────────────────┤
│ Patched versions    │ >=7.3.2                                                │
├─────────────────────┼────────────────────────────────────────────────────────┤
│ Paths               │ .>vitest>vite                                          │
│                     │                                                        │
│                     │ common__vitest-config>vite-tsconfig-paths>vite         │
├─────────────────────┼────────────────────────────────────────────────────────┤
│ More info           │ https://github.com/advisories/GHSA-p9ff-h696-f583      │
└─────────────────────┴────────────────────────────────────────────────────────┘

Expected behavior
Fails = 0

Logs
Described in To Reproduce section above

Additional context
We expect to revert Jest, remove better-auth dependency from examples (reason is the same)

Start by running pnpm audit --audit-level=high and inspect the dependency declarations, pnpm.overrides, and lockfile paths that resolve vitest to vite. Review the linked issue and the expected Jest reversion and example dependency removal. Done means a clean checkout reports zero high-severity audit findings without a manual workaround.