edge-cache-doctor
description (verbatim frontmatter)
Post-deploy diagnosis of the REAL stale-edge-cache-after-deploy pattern this fleet keeps hitting (subagentpython.com 2026-07-01: stale sibling content + error 1104 right after zone activation, self-resolved in seconds; subagentsystemdesigns.com 2026-07-09: first verify saw the old 725-byte parked placeholder, the retry got the 13237-byte worker body). Probes a domain N times with cache-busting queries + no-cache headers, records status/size/cf-cache-status/marker per attempt, and classifies: HEALTHY / STALE-EDGE (some attempt shows the new content — wait and re-probe before diagnosing anything) / ROUTE-MISS (consistent old content, no worker evidence — check wrangler routes, waiting won't help) / DOWN, each with its next action. Use when a just-deployed site "still shows the old page", a verify step failed right after wrangler deploy, curl returns a 725/1008- byte placeholder, or before filing any "deploy didn't take" diagnosis. Do NOT use as the pass/fail deploy gate — that is ../fleet-expansion/scripts/verify-site.sh's job (this is the diagnosis half, that is the gate half) — and do NOT use it to fix routes (route work is a deploy mutation, governed by this plugin's existing gates).
summary
Post-deploy diagnosis of the REAL stale-edge-cache-after-deploy pattern this fleet keeps hitting (subagentpython.com 2026-07-01: stale sibling content + error 1104 right after zone activation, self-resolved in seconds; subagentsystemdesigns.com 2026-07-09: first verify saw the old 725-byte parked...
source
plugins/cwc-deploy/skills/edge-cache-doctor/SKILL.md
provenance
created 2026-07-10 18:13:13 · JSON