chore(web): upgrade Next app to 16

[code-yeongyu]

Summary

• Upgrade packages/web to Next.js 16.2.9, React 19.2.7, pnpm 11.7.0, TypeScript 6.0.3, and current secure web tooling dependencies.
• Add security overrides for vulnerable transitive packages and align web CI/deploy pnpm with the package manager version.
• Add Next DevTools MCP setup/docs for the web package and keep tests aligned with current docs command syntax.
• Preserve the existing UI exactly: no UI component files are changed.

Verification

• pnpm run build
• pnpm run lint
• pnpm run type-check
• pnpm audit --json → 0 vulnerabilities
• pnpm audit signatures → 583 verified signatures
• CI=true pnpm exec playwright test --grep-invert @lighthouse → 47 passed
• CI=true pnpm run test:lighthouse → mobile and desktop perf=100 a11y=100 bp=100 seo=100 via Playwright/Node API, not Lighthouse CLI
• Visual QA: 6 baseline-vs-final mocked screenshot pairs all diffPixels=0, alphaChannelIntact=true
• Manual browser QA: home links/stars/copy/overflow; docs navigation/search/anchor/mobile menu/no-JS SSR; Next /_next/mcp dev endpoint

Notes

• Dynamic GitHub stars were mocked for visual comparison to avoid live API variance.
• The earlier docs desktop visual mismatch was a screenshot viewport-height mismatch; recapturing at the baseline-matched height produced 0 differing pixels.

---

Summary by cubic

Upgrade packages/web to Next.js 16 with React 19 and TypeScript 6, add next-devtools-mcp for local diagnostics, and align CI/deploy to pnpm@11.7.0. Locks down vulnerable transitive deps and keeps the UI unchanged with stable tests and 0 audit issues.

• Dependencies

  • Bump: next@16.2.9, react@19.2.7, react-dom@19.2.7, typescript@6.0.3, @playwright/test@1.61.0, lighthouse@13.4.0, tailwindcss@4.3.1, @biomejs/biome@2.5.0, geist@^1.7.2.
  • CI/deploy use pnpm@11.7.0; browserslist targets raised.
  • Workspace overrides: @opentelemetry/core@2.8.0, esbuild@0.28.1, postcss@8.5.15, ws@8.21.0.
  • Add .mcp.json to enable next-devtools-mcp; add AGENTS.md guidance.
  • tsconfig: jsx: "react-jsx" and include Next 16 dev type paths.

• Migration

  • Require pnpm@11.7.0 and Node >=22, then pnpm install.
  • No UI or app code changes expected; regular build/lint/type-check flow unchanged.
  • Next DevTools MCP available at /_next/mcp when dev server runs.
  • If running e2e locally, use @playwright/test@1.61.0.

^{Written for commit 7f50812. Summary will update on new commits.}

[github-actions]

Thanks for the PR! Changes to LazyCodex land through oh-my-openagent — could you open this against omo-codex over there instead? PRs in this repository can't be merged.

If you're working with a coding agent, prompt it like this:

I opened #58 ("chore(web): upgrade Next app to 16") against code-yeongyu/lazycodex, but changes there land through code-yeongyu/oh-my-openagent, where the Codex implementation lives under packages/omo-codex. Read my original PR, then open an equivalent PR against code-yeongyu/oh-my-openagent. In the new PR body, link the original PR (#58), explain that it was first opened against lazycodex, and describe in detail what that PR changed and why.