The post merged and did not publish: dated tomorrow - #595
Merged
Conversation
Paul asked whether the post was delivered. It was not, and I would not have noticed - I had reported it shipped. `how-to-audit-content-you-didnt-write` carried `date: 2026-08-23`. Today is the 22nd. Production does not build future-dated content, so the post merged to master, passed every gate, and was absent from the live site. Date corrected to 2026-08-22. **Both pieces of evidence I cited were vacuous, and that is the part worth keeping.** `bin/hugo-build` passed - it writes to `_dest/public-dev`, which DOES build the future, so my post was there and I read that as proof. Production writes elsewhere. The build never claimed what I took it to claim. `bin/rake test:links` reported zero errors across 1,768 pages - because the post was not among them. A crawl that skips the thing you wrote reports a clean green for exactly that reason. It scanned everything except the artifact under test. This is the same shape as the dtest incident (#578, green because it compared nothing) and the reason the fault-injection work exists: a gate that cannot see the artifact reports success indistinguishable from real success. The falsifiable check, now in blog-pipeline.md STEP 7 and the blog-write skill: build production, find the slug in it, and QUOTE THE PAGE-COUNT DELTA. This run went 1,768 -> 1,775 pages when the post entered the set. That delta is the evidence; "the build passed" is not. bin/rake test:links find _dest/public-linkcheck -type d -name "<slug>" "Merged" and "delivered" are different claims. Only the second needs this check, and I made the first while reporting the second. Verified after the fix: post present in _dest/public-linkcheck, 1,775 pages, 31,908 unique links, zero errors. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016PUkwFTsiv7EB2DYKogbpg
Contributor
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
The post merged and did not publish: dated tomorrow
Paul asked whether the post was delivered. It was not, and I would not have
noticed - I had reported it shipped.
how-to-audit-content-you-didnt-writecarrieddate: 2026-08-23. Today is the22nd. Production does not build future-dated content, so the post merged to
master, passed every gate, and was absent from the live site. Date corrected to
2026-08-22.
Both pieces of evidence I cited were vacuous, and that is the part worth
keeping.
bin/hugo-buildpassed - it writes to_dest/public-dev, which DOES build thefuture, so my post was there and I read that as proof. Production writes
elsewhere. The build never claimed what I took it to claim.
bin/rake test:linksreported zero errors across 1,768 pages - because the postwas not among them. A crawl that skips the thing you wrote reports a clean green
for exactly that reason. It scanned everything except the artifact under test.
This is the same shape as the dtest incident (#578, green because it compared
nothing) and the reason the fault-injection work exists: a gate that cannot see
the artifact reports success indistinguishable from real success.
The falsifiable check, now in blog-pipeline.md STEP 7 and the blog-write skill:
build production, find the slug in it, and QUOTE THE PAGE-COUNT DELTA. This run
went 1,768 -> 1,775 pages when the post entered the set. That delta is the
evidence; "the build passed" is not.
bin/rake test:links
find _dest/public-linkcheck -type d -name ""
"Merged" and "delivered" are different claims. Only the second needs this check,
and I made the first while reporting the second.
Verified after the fix: post present in _dest/public-linkcheck, 1,775 pages,
31,908 unique links, zero errors.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_016PUkwFTsiv7EB2DYKogbpg