[WIP] Migrate project to Next.js 16 and update AI SDK dependencies

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Original prompt

Project Migration Request: Next.js 16 + AI SDK Update

Objective:
Migrate the current project to Next.js 16 and update all AI SDK dependencies to their latest versions, ensuring zero breakage with minimal code changes.

Requirements:

1. Package Manager: Using pnpm throughout
2. Target Versions:

• Next.js 16 (latest stable)
• AI SDK (latest stable from Vercel)

1. Success Criteria:

• Successful production build (pnpm build)
• All existing functionality preserved
• No runtime errors
• No breaking changes unhandled

Migration Process:

Phase 1: Research & Planning

• Search and review official migration guides:
  • Next.js 16 migration documentation (https://nextjs.org/docs)
  • AI SDK migration/upgrade guides (https://ai-sdk.dev/docs/introduction)
• Identify all breaking changes between current and target versions
• Document deprecated features and their replacements
• Create a comprehensive migration checklist

Phase 2: Dependency Analysis

• Audit current package.json for all Next.js and AI SDK related packages
• Identify version-specific dependencies and peer dependencies
• Check for conflicting packages that may need updates

Phase 3: Incremental Migration

• Update dependencies in stages (not all at once)
• Handle breaking changes systematically:
  • Configuration changes (next.config.js/ts)
  • API route updates
  • App Router changes (if applicable)
  • AI SDK provider/model configurations
  • Type definitions and imports
• Preserve existing functionality at each step

Phase 4: Code Refactoring

• Apply minimal necessary code changes
• Update deprecated API calls to new equivalents
• Ensure type safety throughout
• Maintain code structure where possible

Phase 5: Validation

• Run pnpm build to verify production build
• Check for TypeScript errors
• Validate all configurations
• Document any warnings that need addressing

Constraints:

• Make the minimum number of changes necessary
• Do NOT refactor code unnecessarily
• Do NOT change project structure unless required by migration
• Preserve all existing features and behaviors
• Use web search extensively for official documentation and migration patterns

Deliverable:

• Complete migration with passing build
• Summary of all changes made
• List of breaking changes handled
• Green light confirmation when ready for local testing

Instructions:

1. Start with thorough web searches for migration documentation
2. Use sequential thinking - plan before executing
3. Handle each breaking change explicitly
4. Test build after each major change
5. Do not stop until migration is 100% complete and build succeeds
6. Trust your process but verify each step

Please confirm you understand the requirements and begin the migration process.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.