The UI had almost no motion: two transition declarations in total, no
@keyframes, no animation and no prefers-reduced-motion support. Interactive
states snapped instantly and the landing page was completely static.
Add a self-contained motion layer instead of scattering rules through the
existing stylesheets:
- frontend/src/motion.css holds the tokens, interaction feedback, keyframes
and the reduced-motion opt-out. It only appends rules; no existing layout
rule is rewritten, so dropping the import restores the static UI.
- frontend/src/motion.ts implements scroll reveal with IntersectionObserver
and a MutationObserver for asynchronously rendered content.
Design constraints:
- Animate transform and opacity only, so motion stays on the compositor and
never forces layout of siblings.
- Never animate the transform of the tilted hero artwork, which would
override its 3D perspective; it fades in instead.
- Decorative loops are slow and low amplitude, and only where they convey
"alive" (status dots, hero glow, floating prompt).
- Anchor navigation now uses smooth scrolling with scroll-padding so
section headings clear the sticky header.
Accessibility and progressive enhancement:
- The hidden state is gated on html.motion-ready, which JS adds only after
an IntersectionObserver exists. Without JS, in a browser without the
observer, or with reduced motion requested, content is never hidden.
- prefers-reduced-motion: reduce disables every animation, transition and
smooth scrolling, and forces revealed content visible.
- The reduced-motion preference is also watched at runtime, so toggling it
mid-session reveals anything still hidden.
Verified: 27 pages render without console errors, reveal works on every
landing section, hover feedback is measurable, dark mode and mobile layouts
are unaffected, and both reduced-motion and missing-IntersectionObserver
fallbacks keep all content visible.
Bug 1 (high): login rate limiting used request.getRemoteAddr(), which is
always the nginx container address. Every client shared one bucket, so any
anonymous caller could lock the whole platform out of login for 60 seconds.
- Add ClientIp to resolve the real address, honouring X-Real-IP /
X-Forwarded-For only when the direct peer is a proxy we operate
(loopback, private or container range). Public peers cannot spoof.
- Prefer X-Real-IP, fall back to the right-most X-Forwarded-For entry so
client-supplied prefixes are ignored. Guard with an IP literal check so
a malformed header can never trigger a DNS lookup.
- nginx now overwrites the forwarded headers with $remote_addr instead of
clearing them, so spoofed values never reach the backend.
- Add a global login ceiling (600/60s) well above the per-address limit.
Bug 2: the landing page had no login entry point on mobile. The collapsed
menu button was permanently display:none and the login link was hidden
below 550px, leaving no way to reach an account.
- Show the menu button below 850px, render nav as a dropdown panel.
- Add a login item inside the collapsed menu.
Bug 3: upload size limits disagreed across three layers. nginx capped
requests at 1m while the backend and UI advertise 25MiB, so any file over
1 MiB failed with nginx's HTML error page.
- Raise client_max_body_size to 26m to match the backend.
- Return 413 as JSON matching the API error shape.
Tests: 153 backend tests pass, including 10 new ClientIpTest cases
covering spoofed headers, right-most entry selection, IPv4-mapped IPv6,
and malformed values.