Fix login form light-mode contrast, add theme toggle to auth pages

[soorya-u]

Summary

• Fixes LoginForm and its social provider buttons, which hardcoded dark-only colors (bg-black, border-white/10, bg-white/8) while surrounding text used theme-aware tokens — causing illegible/invisible inputs and buttons in light mode.
• Fixes hover:bg-white on the bg-foreground/text-background "Sign In" buttons (login form + magic link + home page hero CTA), which made the label disappear on hover in light mode. Changed to hover:bg-foreground/90.
• Makes the login form's right-side agent showcase panel theme-adaptive (background + FlickeringGrid dot color) instead of permanently black, so the existing per-icon invert logic works correctly in both themes.
• Extracts the home page's theme toggle button into a shared ThemeToggle component and adds it to the /auth layout, since there was previously no way to switch themes from the sign-in flow.

Test plan

• tsc --noEmit passes
• biome check passes on all touched files
• Verified visually in a local dev server (Playwright) in both light and dark mode: login form, hover states on Sign In buttons, and the new auth-page theme toggle
• Existing unit test suite passes (turbo test-unit via pre-push hook)

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
cyrus	Ready	Preview	Aug 7, 2026 6:05am

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 12 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e39b4910-fb43-4c54-ae2a-f35e967c810f

📥 Commits

Reviewing files that changed from the base of the PR and between 10a8e22 and 5f0681e.

📒 Files selected for processing (6)

• apps/web/src/components/auth/login-form.tsx
• apps/web/src/components/auth/provider-button.tsx
• apps/web/src/components/home/hero.tsx
• apps/web/src/components/home/home-nav.tsx
• apps/web/src/components/theme-toggle.tsx
• apps/web/src/routes/auth/route.tsx

---

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