Repository navigation
docs: a verification that checked the adjacent thing (#2492) - #2505
Merged
Merged
Conversation
Contributor
PR DashboardGenerated at: 2026-08-23 06:13:46 UTC
Summary
Seal Status
|
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
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.
A gate written yesterday for a question nobody was asking went red on real data today. What it found was eleven blog posts absent from a live site for two days.
A deploy had replaced the site's application bundle with one built from a different repository. Eleven posts existed only in the old bundle — never migrated into the shared source — so the swap removed them. They had no static pages either, so nothing served them at all.
That deploy was verified before pushing. Its commit message says so:
Every word of that is true, and it is the wrong question. It checked the static trees; the loss was entirely inside the bundle. A verification aimed one step to the left of the thing being changed is harder to notice than no verification at all, because the commit reads as checked.
The rule: name what your change REPLACES, and verify that.
And a gate is not tested until it is red on data you did not plant. Four planted control cases all passed before the gate had ever seen a real deploy. Replaying it over 160 commits of history found three drops — two healed by the next deploy, one not. That replay is now a mode of the tool rather than a script run once, and it has its own three planted cases: an unhealed drop reds, a healed drop stays green and says why, a clean history does not invent one.
All eleven posts are restored and live in both languages, verified by content on production rather than by exit code.
Refs #2492