feat(site): animate the landing page mascot

[elkaix]

Related Issue

No linked issue. This change follows a direct maintainer request for the landing page.

Problem

The landing page used a static mascot. The supplied animation was 6.98 MB, included audio, contained dark fade frames, and showed an opaque rectangular background against the page.

What changed

• Replaced the static hero mascot with an 811 KB H.264 animation with fast-start metadata and no audio.
• Trimmed the faded frames, built a forward-and-reverse loop, masked the video edges into the page background, and removed the eyebrow artwork from every frame.
• Kept the mascot itself as an accessible play/pause target, without a visible control overlay, and added live reduced-motion preference handling.

Verification

• pnpm --filter @pythoughts/site build
• Browser checks for autoplay, mascot play/pause behavior, live reduced-motion changes, responsive layout, and edge blending
• FFmpeg contact-sheet inspection across the installed loop
• Pixel-mask verification across all 239 frames: zero residual eyebrow pixels in both tracked regions
• pnpm lint (passes with existing warnings)
• Pre-push gate passed: attribution scan, sherif, lint, Nix hash freshness, changed-package typecheck, and changed tests
• Full pnpm test: 650 passed, 11 skipped, and 1 unrelated environment-sensitive failure in test/cli/export.test.ts because the non-interactive harness reported no shell

Checklist

• I have read the CONTRIBUTING document.
• I have linked a related issue, or explained the problem above.
• I have added tests that prove my feature works. (No automated site UI test harness; browser and media checks cover this change.)
• Ran gen-changesets skill, or this PR needs no changeset. (Private marketing site only; no released package changes.)
• Ran gen-docs skill, or this PR needs no doc update. (The landing page is the changed user-facing surface.)

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 3 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: a18fa57e-8718-4a3a-bdcb-8eef9e25671a

📥 Commits

Reviewing files that changed from the base of the PR and between 97afb85 and c4deef2.

⛔ Files ignored due to path filters (1)

• apps/site/public/pythinker-hero-clean-v2.mp4 is excluded by !**/*.mp4

📒 Files selected for processing (1)

• apps/site/src/App.vue

---

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

[pkg-pr-new]

pnpm dlx https://pkg.pr.new/@pythoughts/pythinker-code@c4deef2

npx https://pkg.pr.new/@pythoughts/pythinker-code@c4deef2

commit: c4deef2