Dependency major-version upgrades pending — looking for prioritization before opening PRs

[fabicarvano]

"Running bun outdated on the project turned up ~15 packages with a major version available that would need real code changes (not a simple lockfile bump). Before opening any PR, I wanted to check priority with you, since each one has a different scope and risk.\n\nHighest attention \u2014 interacts with PR #63 (the /responses endpoint fix):\n- @ai-sdk/openai 3.x \u2192 4.x \u2014 PR #63 fixes a routing bug specific to the v3 API shape (.chat() vs the bare callable). A v4 upgrade could change that behavior again, so if you want to move to v4 it probably makes sense to do that after deciding on #63, not in parallel.\n- ai (Vercel AI SDK core) 6.x \u2192 7.x\n\nInfra/tooling \u2014 real risk of breaking the build/CI:\n- nx + @nx/* 21.x \u2192 23.x\n- typescript 5.9 \u2192 7.0\n- next 15.x \u2192 16.x\n- prisma / @prisma/client 6.x \u2192 7/8 (8 is still a release candidate, wouldn't recommend that one yet)\n\nSmaller runtime/libs, still breaking:\n- pino 9 \u2192 10, nodemailer 9 \u2192 10, imapflow 1 \u2192 2, jsdom 26 \u2192 30, pdf-parse 1 \u2192 2, eslint 9 \u2192 10, vitest/@vitest/coverage-v8 3 \u2192 5\n\nHappy to validate and open a PR for any of these you'd like to prioritize \u2014 one at a time, so each diff stays reviewable. Is any of these already on your radar, or would you like me to suggest an order?\n"