Cloudflare's Rate Limiting binding checks a locally cached count per edge machine and syncs it in the background. On production one keep-alive connection hits the limits almost exactly (120 pages, then 429s), but 300 requests on fresh parallel connections in 13 s all passed. Say so in DEPLOYMENT.md and the rate-limit.ts header instead of "overshoot slightly", and document a one-connection curl test for production. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>