Published September 9, 2026.
A green deployment proves the build process finished. It does not by itself prove that every public request is receiving the new page through application, CDN, and browser caches.
Identify the expected version
Save the full commit SHA and a harmless page fingerprint, such as the exact title and publication date. Avoid relying only on a deployment timestamp.
Request the public route
Load the canonical URL without a session and inspect the returned HTML. Confirm the fingerprint, canonical, structured publication date, and linked hero image. Check the family index and sitemap separately because they may follow different cache paths.
Treat inconsistency as evidence
If responses disagree, record headers, location, time, and result. Wait for the platform’s normal propagation window or use the approved targeted purge process. Do not repeatedly redeploy the same commit unless the deployment itself failed.
This separation makes release evidence clearer: build completion is one fact, and public delivery of the intended version is another.