Simplify homepage claw artwork with subtle parallax

[naimkatiman]

What changed

• removes the fixed three-sculpture backdrop from the root layout and all supporting public routes
• restores one restrained market sculpture inside the root homepage hero only
• adds subtle CSS scroll-linked parallax with static reduced-motion and mobile-safe states
• removes the unused Remotion player, route allowlist, and two Remotion runtime dependencies
• keeps the additional generated WebPs as source assets without referencing them at runtime
• records the verified Railway production release and rollback receipt

Why

Owner feedback was that the repeated background imagery overwhelmed the page. This refinement returns to the quieter single-art composition: one homepage section, one decorative image, and no wallpaper effect while scrolling or browsing docs and product pages.

Validation

• focused Jest: 2 suites / 5 tests passed
• web lint: zero errors (23 existing warnings)
• web typecheck: passed
• root production build: 324/324 static pages generated
• local Playwright: desktop parallax, 360px mobile, reduced motion, and docs boundary passed with zero console errors
• Railway deployment 8e67d017-a7cb-4d1d-b152-561c68cc2641: SUCCESS
• production homepage, docs, and health endpoint: HTTP 200; one homepage image, no global backdrop or Remotion player

[gemini-code-assist]

Code Review

This pull request replaces the homepage-specific 'HeroBrandArt' with a site-wide 'GlobalClawBackdrop' component that uses Remotion to render slow, deterministic ambient motion on desktop devices, falling back to a static composition on mobile and for users with reduced motion. The backdrop is restricted to public marketing routes via an explicit allowlist. Feedback focuses on preventing Next.js hydration mismatches by gating client-side checks with a 'mounted' state, ensuring React 19 compatibility by adding explicit 'px' units to CSS properties, and pausing the Remotion player on mount if the page is loaded in a background tab to save resources.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[naimkatiman]

The reviewer comment suggestions target older file paths/commit state that is no longer in the current PR branch. The referenced code has since been superseded; no direct patch is applicable at this time.