verify-sitelisted
Install: claude install-skill reloru/new-relo
# Verify the live site
Confirm the deployed site is healthy. Use the base URL in `$ARGUMENTS` if one was
given, otherwise `https://crosbynews.com`. Run the checks below with `curl`, then
report a compact PASS/FAIL table. For anything that FAILs, quote the actual
status/header so it's actionable.
**Deploys land in ~10–40s but take 1–2 minutes to reach every edge.** A single
curl can be served by a colo still running the PREVIOUS Worker version, and a
`?cb=` cache-buster does NOT help — this is version propagation, not caching.
When checking that a specific change went live, sample ~8 times and require
agreement before reporting either way:
```bash
for i in $(seq 1 8); do curl -s "$BASE$PATH?cb=$RANDOM-$i" | grep -c "$MARKER"; done
```
Measured 2026-08-05: 7/8 new, 1/8 old, persisting ~2 minutes past a green deploy
job. Report a mixed sample as "still propagating", never as a failure.
## 1. Routes return 200 — **both languages, every page**
**Sweep all 21 content pages in BOTH languages. Not a spot-check.** Roughly half
the site's render branches never execute under `lang="en"`, so an English-only
pass proves nothing about `/es`. This is not hypothetical: `/es/hourly` served a
502 in production across two deploys because `features/hourly.js` referenced
`ES_NWS_NOTE`, which only the Spanish branch reaches, and the checklist here said
"`/es` (Spanish spot-check)" — so `/es` was green while `/es/hourly` was down.
English pages: `/`, `/weather`, `/hourly`, `/radar`, `/alerts