Can this launch?
Cloudflare deploy surface check
Verifies a live Cloudflare Pages deploy for the six traps invisible to every check that only reads HTML: a Content-Security-Policy header silently dropped because its _headers line ran over Cloudflare's length limit; a served asset over 25 MiB, which hard-rejects the whole deploy; the deployed HTML rewritten by Auto-Minify so a byte-parity comparison drifts against a transform nobody made; a stale edge-cached alias serving the previous bundle for up to 24h after a redeploy; declared _headers/_redirects rules that were written but never confirmed live; and an Access-gated preview reachable on its unprotected deployment alias even though the project alias is gated.
What this capability does
Verifies a live Cloudflare Pages deploy for the six traps invisible to every check that only reads HTML: a Content-Security-Policy header silently dropped because its _headers line ran over Cloudflare's length limit; a served asset over 25 MiB, which hard-rejects the whole deploy; the deployed HTML rewritten by Auto-Minify so a byte-parity comparison drifts against a transform nobody made; a stale edge-cached alias serving the previous bundle for up to 24h after a redeploy; declared _headers/_redirects rules that were written but never confirmed live; and an Access-gated preview reachable on its unprotected deployment alias even though the project alias is gated.
How employees use it
Ask for the outcome in normal job language. The coding agent selects the approved implementation, records evidence, and returns a review-ready result.
“check the Cloudflare deploy — https://sherberandrad.com”
Where the technical instructions live
The detailed implementation guide stays inside the private Toolkit repository. Employee-facing pages intentionally use friendly capability names only.