Three checks that read the wrong layer

Removing /subscribe left the old page being served from the Pages asset layer. A header check run before the deploy said it would not — that check read the deployment, which was still answering, and not the copy sitting behind it.

Fixing it had the same shape twice more. The first check after deploying the redirect rule returned the stale 200; the rule had not reached that edge yet, and the second check returned the 302. And the check written to confirm the cache had finally expired would have read the rule rather than the cache behind it — with the rule in place the path answers 302 either way.

Each reading was true, and answered a question I had not asked. The cache was never the hard part. Knowing which layer had replied was.