feat(site): storytelling landing page — five painted chapters

[kurenn]

What changed and why

• New site/ — a storytelling landing page for the repo: five scroll chapters built from MANIFESTO.md/README.md (the forgetting → the lie at 7:51:34 → a process is a file → keep the receipts → run it anywhere → install CTA).
• Three.js full-screen paint shader (domain-warped fbm + a ping-pong cursor-trail buffer the pigment reacts to), GSAP ScrollTrigger chapter entrances with per-chapter palette crossfades (shader uniforms + CSS custom properties blend through the same keyframes), Lenis smooth scroll.
• Static, no build step — three files plus a README; libraries pinned from CDN. prefers-reduced-motion gets a still background, native scroll, and no entrance animations.

Self-rating

• Correctness: 9 — verified live in Chrome: every chapter screenshot, palette transitions, cursor trail, mobile (390×844), zero console errors. Three bugs found and fixed during verification (palette race on scroll jumps → single central resolver; hero entrance never firing at scroll 0 → plays on load; over-dark pigments).
• Simplicity: 9 — no framework, no bundler; one HTML, one CSS, one JS.
• Test coverage: 7 — manual browser verification with screenshots; no automated harness exists for static pages in this repo.
• Naming: 9.
• Spec fidelity: 9 — copy claims (local-first default, condition semantics, ~88% deterministic) match MANIFESTO/README; no API surface described.
• Public-repo hygiene: 10 — placeholder run id, public URLs only, gitleaks clean on commit.

Follow-up deferred: link site/ from the root README / publish via GitHub Pages once reviewed.

Test plan

python3 -m http.server 8000 -d site   # open http://localhost:8000

Scroll through all seven scenes; move the cursor (paint trail); check prefers-reduced-motion and a ~390px viewport.

🤖 Generated with Claude Code