Modernize site architecture and static publishing

[130U]

Summary

• migrate the site from Vinext/Vite/Cloudflare scaffolding to the official Next.js static export
• centralize site, experience, and post metadata in validated registries with scalable dynamic static routes
• preserve every original public word, link, accessible name, deep-link ID, date, and source asset through frozen artifact baselines
• add append-only snapshots so future published pages receive the same copy-preservation guarantee
• add responsive image derivatives, canonical/OG metadata, robots, sitemap, JSON-LD, and a custom 404
• refine accessibility and responsive behavior without changing the approved visual or editorial direction
• simplify GitHub Pages CI so PRs validate and only main can deploy

Why

The previous implementation rendered correctly but mixed framework, export, worker, and route-specific infrastructure. That made routine content additions easy to duplicate and harder to validate. The new architecture uses framework-standard static publishing, explicit content contracts, and final-artifact tests so future maintenance is smaller and safer.

Impact

The public design and original writing are preserved. The main user-facing differences are accessibility improvements, responsive image loading, stronger metadata/discovery, and a custom 404. Maintainers get a documented single-repository workflow with compile-time and CI guardrails.

Validation

• clean npm ci --ignore-scripts
• npm.cmd run check — lint, typecheck, official Next export, 11/11 artifact tests
• npm.cmd audit --omit=dev — 0 vulnerabilities
• preservation-fixture additions-only gate
• git diff --check
• browser review at desktop, 720px, 390px, and 320px
• independent architecture, security/CI, and Apple-design acceptance reviews