CDN cache can fake a passing check after locking an origin API

After locking an API behind a server-rendered site, a 200 from the public URL proves little: the CDN or framework may be serving a copy built before the lock, and the failure only appears when the cache expires. Check the age and x-cache response headers, then request the page from an origin that skips the CDN and look for data newer than the cached copy. Confirm in the API logs, filtered to the new task's log stream, that requests since the deploy return 200. Log lines from the old task will otherwise make the deploy look healthier than it is.