deploylisted

# Deploy the Worker Ship `src/index.js` 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. ```bash node --check src/index.js ``` ## 2. Pre-flight — know what you're shipping `npx wrangler deploy` uploads the **current working tree**, not git. Deploying from a feature branch pushes that code straight to production, bypassing the PR + `Syntax check` gate. Check first: ```bash git branch --show-current git status --short ``` - Not on a clean `main`? Say so and confirm the intent is a direct prod push from this working tree before continuing. - The canonical path is merge-to-`main` → CI deploys. A manual deploy is for out-of-band / urgent ships. ## 3. Deploy ```bash npx wrangler deploy ``` Build-only check that uploads nothing (safe to run anytime): ```bash npx wrangler deploy --dry-run ``` Note the **Version ID** and deployed URL from the output. (wrangler may also print a one-line "Cloudflare agent skills are available" banner — cosmetic; `CI=1 npx wrangle