Fix Vercel Next.js output directory

[lupppig]

Summary

• override the stale Vercel project output directory with .next
• align the deployment configuration with the repository's Next.js standalone build

Root cause

The post-merge Vercel workflow compiled the Next.js application successfully, then failed because the linked Vercel project still expected the previous dist directory. This repository builds Next.js output in .next.

Validation

• npm run lint
• npm run typecheck
• npm run build
• Next.js generated all 17 static pages and prepared standalone output successfully

Summary by CodeRabbit

• Chores
  • Updated deployment configuration to use the correct Next.js build output directory.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 3458b244-d630-4991-a232-1853d57264fe

📥 Commits

Reviewing files that changed from the base of the PR and between 911f8bd and a326bc5.

📒 Files selected for processing (1)

• web/vercel.json

---

📝 Walkthrough

Walkthrough

The Vercel configuration now explicitly sets .next as the build output directory while retaining the existing Next.js framework declaration.

Changes

Vercel configuration

Layer / File(s)	Summary
Build output configuration web/vercel.json	Adds "outputDirectory": ".next" alongside the existing "framework": "nextjs" setting.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: updating Vercel’s Next.js output directory configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/vercel-output-directory

---

_{Comment @coderabbitai help to get the list of available commands.}