Upgrade Next.js and add page smoke tests

[willwashburn]

Summary

• upgrade Next.js to stable 16.2.10, React/React DOM to 19.2.7, and the OpenNext Cloudflare adapter to 1.20.1
• remove the deprecated PostHog middleware convention that produced the Next.js warning and could not migrate to Node-only Proxy on OpenNext Cloudflare
• add a self-discovering Playwright production smoke suite covering every registered static page, agent, blog post, current/legacy docs page, product docs page, redirect alias, and invite-page shape

Why

Next.js 16 deprecates middleware.ts in favor of Node.js proxy.ts, while the current OpenNext Cloudflare adapter rejects Node.js Proxy. The existing PostHog client already sends analytics through its configured ingest host, so removing the unused middleware path resolves the warning without breaking the deploy target.

The page suite provides upgrade protection by asserting successful HTTP responses, visible meaningful content, document titles, absence of application-error output, and clean browser hydration across the generated route inventory.

Validation

• npm test — 82 tests passed
• npm run build — passed on Next.js 16.2.10
• npm --workspace web run cf:build — OpenNext Cloudflare bundle completed
• npm --workspace web run test:e2e — 271 Chromium page checks passed

---

Summary by cubic

Upgraded next to 16.2.10 and react/react-dom to 19.2.7, added a Playwright page smoke suite, and removed the deprecated PostHog middleware.ts to resolve Next 16 warnings and Cloudflare incompatibility.

• New Features

  • Added self-discovering Playwright smoke tests for static pages, agents, blog posts, current/legacy/product docs (including versioned paths), redirect aliases, and invite pages.
  • Each page is checked for a successful response, visible meaningful content, a non-empty title, no “Application error”, and now explicitly waits for load and initial hydration before assertions to catch uncaught errors.
  • Config builds and starts the app on port 3100, runs Chromium tests, and in CI enables retries and the GitHub reporter. Run with: npm --workspace web run test:e2e.
  • Updated next-env.d.ts to the new Next 16 route types path to remove the dev-only reference.

• Dependencies

  • Upgraded next to 16.2.10.
  • Upgraded react and react-dom to 19.2.7.
  • Upgraded @opennextjs/cloudflare to 1.20.1 and added @playwright/test (dev).

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

[coderabbitai]

Warning

Review limit reached

@willwashburn, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 29 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 70de7981-3c90-4b2c-bd41-849ec913d080

📥 Commits

Reviewing files that changed from the base of the PR and between 0816b8e and daff0a3.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (6)

• .gitignore
• web/e2e/pages.spec.ts
• web/middleware.ts
• web/next-env.d.ts
• web/package.json
• web/playwright.config.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch agent/upgrade-next-page-smoke-tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[gemini-code-assist]

Code Review

This pull request introduces Playwright end-to-end smoke tests to verify page rendering, removes the PostHog middleware, and updates several project dependencies (including Next.js and React). Feedback on the new test suite highlights opportunities to improve path resolution robustness by replacing process.cwd() with __dirname, making the agent slug regular expression less fragile to quote style changes, and enabling reuseExistingServer locally to optimize the developer experience.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[github-actions]

Preview deployed!

Environment	URL
Web	https://43b04bd2-agentrelay-web.agent-workforce.workers.dev

This is a Cloudflare Workers preview version of this PR's build.

[cubic-dev-ai]

All reported issues were addressed

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>