Repository navigation
docs: sweeping for the shape, and what a guard cannot ask (#2492) - #2506
Merged
Merged
Conversation
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#2505 named a shape rather than an incident — a verification aimed one step to the left of what the change replaces. So every deploy path in reach got the same two questions: what does it REPLACE, and what does it verify?
Four paths, one hit.
The hit was the worst one available
publish-website.ymlruns on a 15-minute cron, unattended, and replaces the site'sassets/with a build from another repository. It called the blog regenerator and the drift checker and nothing that asks whether the incoming build still carries the posts the site is serving — the exact gap that cost eleven posts two days of downtime, sitting in the one path that fires ninety-six times a day without a human present.And the drift checker structurally cannot ask it
verify-site.shcompares the shipped bundle against the static tree and fails on disagreement. That is the right check. It is also blind to a slug leaving both sides at once, which is what happened: the posts lived only in the bundle, the bundle was replaced, and nothing disagreed with anything.A checker of agreement between two artefacts says nothing about preservation across time. Different questions; one instrument cannot hold both.
The clean paths were clean for a copyable reason
The CNAME guard reads the CNAME file. The Pages guard reads the Pages API and curls production. Each verifies the artefact it names, and the second crosses an independent channel to do it.
Then the sweep turned on the instrument
The new gate counted slugs by PRESENCE on disk.
rsyncis additive, so yesterday's chunk sits beside today's: a slug dropped from the reachable chunk is still on disk in the unreachable one, so a disk-wide read calls it live while the site 404s it — and the orphan prune that follows a deploy then deletes it for good.That is the 2026-08-21 mechanism exactly, and the instrument built to catch it shared its blind spot. Today the apex carries 16 chunks, one reachable, and it happens to hold all 48 slugs: the old reading was right by luck.
Reachability from
index.htmlnow. Eighth control case, verified RED under the old presence-based reading. The planted trees carry a realindex.htmland entry chunk so the cases run the walk rather than the no-index fallback — planting only the chunk would test the fallback and call it the gate.Verified where it matters
In CI, not only locally: the cron fired on the commit that added the gate and printed
no post is lost — live serves 48, this build carries 48, 0 new. And on real data the other way: the pre-restoration build exits 1 and names all eleven posts.Refs #2492