Scenario 12: cdn-edge-pop-us-east — No False Credit

A CDN cache purge triggered a stampede of re-fetch requests against the origin, spiking latency for about 25 minutes. The cache naturally re-warmed and latency recovered on its own — about 6 minutes before a manual cache-flush fix actually ran.

Steps to test

1. Open INC0000012.
2. Steps 4–7: http_request_duration_p99_ms spikes after the purge, then recovers on its own.
3. Steps 13–14: the manual cache-flush is executed live, but timestamped after recovery had already happened.
4. Verification outcome VERIFICATION_INCONCLUSIVE, with a reason noting latency was already back to baseline before the fix ran.