feat: ignite the home page with rising embers and shimmer

[punyamsingh]

Cinematic glow-up for the landing page, in keeping with the Catching Fire theme. 🔥

What changed

• Rising embers (EmberField.tsx) — 32 glowing sparks drift up through the dark like the girl on fire, each with its own size, speed, sideways drift, and brightness. Positions are derived deterministically from a sine hash, so it's hydration-safe (no SSR mismatch), fully decorative (aria-hidden, no pointer events), and silenced by prefers-reduced-motion.
• Living atmosphere — the static glow blobs now slowly drift and pulse, plus a third ember pool low-left for depth.
• Shimmering headline — molten gold sweeps across the "ever in your favor" accent (and "library" on the populated shelf), with a soft ember drop-shadow.
• Breathing Mockingjay — the hero pin gently scales and brightens instead of sitting flat.
• Drop-target halo — a warm ember glow pools behind the upload zone to pull the eye to the main action.
• Richer feature cards — glowing icon rings, a faded 01 / 02 / 03 index, an ember filament that ignites along the top edge on hover, lift + glow shadow, and a staggered fade-in.

All new motion respects prefers-reduced-motion via the existing global rule.

Verification

• pnpm lint — 0 errors (6 pre-existing warnings in untouched ui/ files)
• pnpm format:check — clean
• pnpm build — passes

The release-managed CHANGELOG.md was left untouched; the commit is Conventional (feat: → minor bump).

https://claude.ai/code/session_013mbrh7Lhq2F7NR5pBZneh4

---

Generated by Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
wereadpdf	Ready	Preview, Comment	Jun 10, 2026 9:10am

[coderabbitai]

Warning

Review limit reached

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

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

Your organization has run out of usage credits. Purchase more in the billing tab.

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

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: bbf858c5-4c5c-4ffa-bc9e-a997906ddd47

📥 Commits

Reviewing files that changed from the base of the PR and between e1da1cc and e268fbd.

📒 Files selected for processing (3)

• src/components/EmberField.tsx
• src/components/Library.tsx
• src/styles.css

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/nice-johnson-b0donc

---

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