vercel-deploy-triage

name	vercel-deploy-triage
description	Triage and fix repo-tracked Vercel deployment issues for the live app. Use when: Vercel build/runtime checks fail, direct SPA routes 404 in production, or a Vite upgrade may need a new Node engine pin.

Vercel Deploy Triage

When to Use

• Vercel failed on main or a production deploy looks broken
• Direct app routes like /about, district, constituency, or candidate URLs 404 on Vercel
• Vite or deployment dependency upgrades may need a runtime pin refresh

Canonical Files

• vercel.json
• package.json
• README.md
• AGENTS.md
• handoff.md

Procedure

1. Confirm the target SHA and check the latest Vercel status before changing repo files
2. Reproduce the production build locally with npm run build
3. Check the installed Vite engine requirement and keep package.json.engines.node aligned with it
4. Preserve the SPA fallback in vercel.json so direct routes rewrite to /index.html
5. After deploy, verify /, /about, one nested district route, and one static asset or public/data/* JSON URL
6. If the fix adds a durable repo rule, sync AGENTS.md, README.md, and handoff.md before close-out

Guardrails

• Prefer the minimum repo-tracked fix; do not mutate candidate or swarm data for a deploy-only incident
• Keep static assets and public/data/* reachable; do not replace them with the SPA fallback
• Treat pushing main as production-affecting
• Use the repo-local GitHub App identity for any commit or push

Validation

• npm run build passes
• Vercel check on the pushed SHA is green
• Direct SPA routes return 200
• Static files such as favicon.svg and public/data/*.json still return their real content types