fix(seo): restore crawler metadata rendering

[Producdevity]

Description

Googlebot requests served from Vercel's cached shell lose page metadata after a React metadata-boundary resume mismatch. Update Next.js and its four companion packages from 16.2.6 to 16.3.6, which contains the upstream metadata-resume fixes (vercel/next.js#96364 and vercel/next.js#96367). Application code and API contracts are unchanged.

Type of change

• Bug fix

How Has This Been Tested?

• Full application production build with Node 22 and isolated placeholder services.
• Lint (0 errors, 79 warnings), typecheck, and complete unit suite through the normal push hooks.
• Database-free cached-shell reproduction: 16.2.6 fails both Googlebot resume assertions; 16.3.6 passes all 12 supported browser/crawler paths, including title, description, canonical, Open Graph and Twitter metadata.

The Vercel preview passes all six repeated browser/Googlebot/Twitterbot report requests, including Googlebot cache HIT with complete metadata and no resume-error digest. Real Clerk development sign-in passes. Both mobile auth and mobile getSession return 401 anonymously and 200 with the existing test session; getSession reports isAuthenticated=true. Liveness and database readiness return 200. All CI gates pass, including 2104 unit tests (4 skipped) and 292 browser tests (2 skipped). The isolated local build used a static sitemap fallback; deployed preview checks use the existing staging database.

Checklist

• Performed a self-review of the dependency update and exact-version package-age exception.
• The 24-hour release-age rule remains enabled; an explicitly approved exception covers only the 14 exact Next.js 16.3.6 package versions.
• No schema, migration, application behavior or API contract changes.

Notes for reviewers

Merge deploys through the existing Vercel production pipeline after CI and preview validation. VPS cutover, DNS changes and database migration are outside this release.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
emuready	Ready	Preview	Sep 23, 2026 9:01am UTC

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 1c8d14e7-b519-413f-8816-c98180a47633

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-23T08:56:12.820655Z	fcd0f4a	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.

Re-trigger cubic</sub>