deploylisted
Install: claude install-skill reloru/new-relo
# Deploy the Worker
Ship the Worker source under `src/` to the `crosbynews` Worker and confirm the
live site is healthy. Auth comes from `CLOUDFLARE_ZONE_API_TOKEN` (preferred — see
CLAUDE.md's Deploy section) or `CLOUDFLARE_API_TOKEN`, paired with
`CLOUDFLARE_ACCOUNT_ID` either way (never a zone id — wrangler has no such
concept) — **never run `wrangler login`** (it clobbers the token auth).
If `$ARGUMENTS` contains `--dry-run`, run step 1, then the dry-run in step 3, and
stop — nothing is uploaded and nothing goes live.
## 1. Pre-flight — syntax gate
Mirror CI's gate before shipping. If this fails, STOP — do not deploy. It covers
every file under `src/`, not just the entry point: `node --check` validates one
file at a time and doesn't follow imports, so checking only `src/index.js` would
pass while an imported module was unparseable.
```bash
find src -name '*.js' -print0 | xargs -0 -n1 node --check
```
Then the cross-module reference check and the renderer sweep (both pure node,
no install):
```bash
node scripts/check-module-refs.mjs
node scripts/check-renders.mjs
node scripts/test-health.mjs
```
`node --check` catches syntax errors but NOT a missing or renamed export — the
dry-run in step 3 catches that, so treat it as a merge gate, not an optional
extra. And NEITHER catches a module using another module's export without
importing it, because esbuild treats an unresolved identifier as a global. That
is what `check-module-refs.mjs` is for; run all three.
## 2. Pre-fligh