Create the incident note at vault/04-Operations/Incidents/2026-03-13 Stale Build Manifest.md
Use the same Obsidian format as the existing incident files in that folder (YAML frontmatter with created, tags, related fields, and wikilinks). Here's what happened:
Incident: RateRight landing page UI degraded — CSS/JS failing to load intermittently.
Root cause: The Next.js server process (rateright-app.service) had been running since Mar 6. Someone ran npm run build on Mar 13 which regenerated the .next directory, but the running process still had old build manifests cached in memory. When browsers requested CSS/JS chunks, some hashes matched and worked, others didn't — causing intermittent 500s and unstyled pages.
Fix: systemctl restart rateright-app.service — fresh process loaded current build manifests.
Verification: Service active, CSS 5/5 returning 200 (98KB, text/css), page 200 fully styled, zero console errors.
Prevention: Added a warning callout and chained npm run build && systemctl restart in vault/04-Operations/SOPs/Deployment SOP.md. Added checklist items for SSR restart and asset verification. Next.js in production reads build manifests once at startup — always restart after rebuilding.
Link back to: [[04-Operations/SOPs/Deployment SOP]]