Re-take the bundle document against what the build writes now - #212
Closed
iderex wants to merge 1 commit into
Closed
Re-take the bundle document against what the build writes now#212iderex wants to merge 1 commit into
iderex wants to merge 1 commit into
Conversation
Six of the outputs pasted into docs/serving-the-bundle.md on 2026-08-16 no longer reproduce, and the largest of them tells an operator the wrong thing about what they downloaded. The archive listing named seven files; the build writes twenty-two, so the install page, the design system page, the icon and twelve plugin pages were missing from the list somebody checks their unpacked bundle against. The invariant rows read 4 and 7 files and read 18 and 22, the reproduce leg read 7 files and reads 22, the two pack digests have moved, the not-found page has gained a reference, and the sitemap has gained fourteen entries. What prevents the same drift where it can be prevented: the two outputs that were enumerations are replaced by the command and a count, which is the repair the threat model already took for a hand count. A list of one entry per page goes stale on the day the next page lands and nothing reddens, so this document hands the reader the command instead of the answer. The rest are numbers and are re-taken with the date they were taken on. The three pastes that still reproduce are left alone: the bill of materials excerpt, the not-found file location and the empty release listing were re-run and are unmoved. The last section says plainly that nothing in this tree holds this document to the output it describes, so a reader knows the figures are somebody's readings rather than something a run keeps honest.
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.
Closed, and replaced by #213 with the same bytes
This branch was pushed without a
Signed-off-by:trailer on its one commit, andthe DCO check reds every non-merge commit that carries none:
Run 2026-08-28. That trailer is part of the commit, so adding it to a commit
already pushed means rewriting it. This repository does not force-push, so the
correction goes out under a new name and this branch is abandoned instead.
The replacement carries the same bytes, compared rather than asserted:
Both run 2026-08-28. The whole of what this change is and what was run is in the
body of #213. Nothing about it changed here.