What broke
The repository and public website disagreed.
A green source check proved that a file changed, but visitors could still receive an older deployed page.
DentSignal repair · Deployment truth
The code changed. The live page did not.
The repair extended verification from the repository to the exact deployment and the custom domain a visitor actually opens.
What changed
The check followed the release to its destination.
Verification linked source revision, exact project deployment, deployment URL, and a cache-busted custom-domain response.
What it fixed
“Done” now means the intended version reached the public surface.
The check requires new content and rejects known stale copy at the URL visitors use.
Before / after
Check the page visitors actually open.
Broken
assert source_has(new_marker)
mark_release_done()Fixed
assert deployment_matches(revision)
page = fetch(custom_domain, cache_bust=True)
assert new_marker in page
assert old_marker not in pageEvidence
The historical release check covered all three surfaces.
The cited revision history reports source-contract checks, exact-project deployment verification, deployment-URL checks, and cache-busted custom-domain checks with stale-copy rejection. They were not rerun for this page.
Stack and capabilities
Release verification from commit to visitor response.
- Vercel
- GitHub Actions
- HTTP checks
- Revision matching
- Cache-busted verification
- Stale-copy detection
Next