blog: restore the eleven posts a bundle swap dropped - #873
Merged
Conversation
On 2026-08-21 a deploy replaced the apex SPA bundle with one taken from this repo's gh-pages tree. Those eleven posts existed only in the apex bundle -- they had never been migrated into posts.ts -- so the swap removed them. They have been absent from t27.ai for two days: not in the bundle, and never having had static pages either. The deploy verified "blog/ (29) and ru/ (11) untouched" before pushing. That was true and it was the wrong question: it checked the static trees, not the bundle's slug set, and the loss was entirely inside the bundle. Found by replaying ghashtag.github.io/check-deploy-loses-nothing.py over 160 commits of apex history. Three transitions dropped slugs; two recovered on the next deploy, this one did not. Full en+ru text recovered from the 2026-08-12 rescue snapshot. Every block kind used (p, h, ul, quote, code, table) is already in the Block union, so nothing is converted or approximated. Verified: build carries 48 slugs against the live 37, +11, none lost.
github-actions Bot
added a commit
that referenced
this pull request
Aug 23, 2026
blog: restore the eleven posts a bundle swap dropped (#873) On 2026-08-21 a deploy replaced the apex SPA bundle with one taken from this repo's gh-pages tree. Those eleven posts existed only in the apex bundle -- they had never been migrated into posts.ts -- so the swap removed them. They have been absent from t27.ai for two days: not in the bundle, and never having had static pages either. The deploy verified "blog/ (29) and ru/ (11) untouched" before pushing. That was true and it was the wrong question: it checked the static trees, not the bundle's slug set, and the loss was entirely inside the bundle. Found by replaying ghashtag.github.io/check-deploy-loses-nothing.py over 160 commits of apex history. Three transitions dropped slugs; two recovered on the next deploy, this one did not. Full en+ru text recovered from the 2026-08-12 rescue snapshot. Every block kind used (p, h, ul, quote, code, table) is already in the Block union, so nothing is converted or approximated. Verified: build carries 48 slugs against the live 37, +11, none lost.
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
1 participant
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.
Eleven posts have been absent from t27.ai for two days. Not in the SPA bundle, and never having had static pages either — entirely gone.
What happened
On 2026-08-21 a deploy replaced the apex SPA bundle with one taken from this repo's
gh-pagestree. Those eleven posts existed only in the apex bundle — they had never been migrated intoposts.ts— so the swap removed them.The deploy's own verification says:
That was true, and it was the wrong question. It checked the static trees; the loss was entirely inside the bundle.
How it was found
By replaying
ghashtag.github.io/check-deploy-loses-nothing.pyover 160 commits of apex history — a gate written yesterday for exactly this question, and never yet red on real data.Three transitions dropped slugs. Two (2026-08-12, three slugs each) recovered on the next deploy. This one did not.
The restoration
Full en+ru text recovered from the 2026-08-12 rescue snapshot, which holds all eleven. Every block kind used —
p,h,ul,quote,code,table— is already in theBlockunion, so nothing is converted or approximated: the bodies go in as they were written.Restored slugs:
Verified
check-deploy-loses-nothing.pyagainst this build: live serves 37, this build carries 48, 11 new, none lost.