Harden Vercel config for first-pass Next.js deployment

[Copilot]

The repository’s vercel.json was carrying framework-specific overrides that are unnecessary for a standard Next.js deployment and can drift from Vercel’s expected config shape. This change reduces the config to the minimum explicit settings needed for this app while preserving the install behavior required by the dependency graph.

• Config shape

  • Add the official Vercel schema reference for editor/schema validation.
  • Add version: 2 so the config is explicitly interpreted as a Vercel project config.

• Next.js deployment defaults

  • Remove buildCommand and outputDirectory overrides and defer to Vercel’s native Next.js detection/build pipeline.
  • Keep framework: "nextjs" explicit for clarity.

• Dependency install behavior

  • Preserve the custom install command using npm install --legacy-peer-deps, which this repo still needs because a plain npm install does not resolve successfully with the current peer dependency set.

{
  "$schema": "https://openapi.vercel.sh/vercel.json",
  "version": 2,
  "framework": "nextjs",
  "installCommand": "npm install --legacy-peer-deps"
}

[Copilot]

Pull request overview

This PR simplifies and hardens the repository’s vercel.json to better align with Vercel’s default Next.js deployment behavior while keeping the required custom install command for dependency resolution.

Changes:

• Adds the official Vercel JSON schema reference for editor validation.
• Explicitly sets version: 2 for Vercel project config interpretation.
• Removes explicit buildCommand / outputDirectory overrides to rely on Vercel’s native Next.js pipeline, while keeping framework: "nextjs" and the legacy peer deps install command.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.