Fix production build font loading

[CheFu-code]

Motivation

• Production builds were failing because next/font/google attempted to fetch Google Fonts during compilation and network requests could fail.
• The app already referenced Geist CSS variables for fonts, so switching to local fallbacks avoids the external dependency at build time.

Description

• Removed next/font/google usage and the generated font variables from src/app/layout.tsx so the layout no longer triggers Google Fonts fetches during next build.
• Replaced the Geist font variables with local system font fallbacks by adding --font-geist-sans and --font-geist-mono to :root in src/app/styles/base.css and updated the HTML className to a static value.
• Changed files: src/app/layout.tsx and src/app/styles/base.css.

Testing

• Ran npm run typecheck, which completed successfully.
• Ran npm run lint, which passed with one existing warning in src/hooks/useAsync.ts (no-unused-vars).
• Ran npm run build, which now completes successfully and generates the static routes without attempting to fetch Google Fonts.

---

Codex Task

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
flow	Ready	Preview, Comment	Jun 20, 2026 8:48am

[coderabbitai]

Warning

Review limit reached

@CheFu-code, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 7 minutes and 46 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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

🚦 How do rate limits work?

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

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: aa6b5e0a-350f-4187-b2f7-3715ba054695

📥 Commits

Reviewing files that changed from the base of the PR and between 1b31cc4 and 358fe15.

📒 Files selected for processing (2)

• src/app/layout.tsx
• src/app/styles/base.css

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/fix-signing-in-implementation

---

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 and usage tips.}