chore(release): v1.8.23 — the downstream-report residue, finished - #421
Merged
Conversation
Packages the four units this wave shipped, and the interesting part is that each one unblocked the next rather than being four independent chores: - #175 (PR #417) validate.ps1 stopped mojibaking its own output on a non-UTF-8 console. Its bootstrap reproduced #178 live. - #178 (PR #418) AGENTS.md stopped forbidding the backlog advance bootstrap.md requires. That legalised the step #88's bootstrap needed. - #88 (PR #419) Windows CI shards balance by time, not test count. Its committed durations file turned #171 from latent into a hard block. - #171 (PR #420) the secret scanner stopped failing on ordinary identifiers, which had to land before anything else could merge. Every headline number is measured, and two were revised DOWNWARD on measurement rather than published as predicted: - #88's rebalance was predicted at 2.2x from workstation-generated weights; it measured 13m7s then 11m24s against a 21m57s baseline = 1.67x-1.93x, recorded as a RANGE because two runs of the same tree differed ~13%. - #175's backlog row claimed the bug does not reproduce on pwsh 7; measured, 5.1 and 7 emit identical bytes, and the row was corrected in place. - #88's own row recorded 7:14 for an imbalance that had grown to 21m57s. Three greens were mutation-verified before being trusted: the directive-count ratchet, the new detector-scope test, and the source-only call-site guard -- whose mutation run REFUTED a review panel's headline objection. Version banners bumped on seven surfaces, enumerated by grepping the previous version on disk rather than trusting the last release's record. Each replacement asserted its own anchor; residual grep over all seven returns 0. Files #182: nothing pins version consistency across those seven surfaces. This release's own banners were bumped by hand -- same failure class as the tag step in repo-gotchas 12, which has been forgotten twice. Tests: - full CI-equivalent suite, no -m filter: 897 passed, 1 skipped, exit 0 (1:06:46) - validate.ps1 exit 0 - pass=118 warn=4 fail=0 skip=2 (unqualified pass) - validate.sh exit 0 - pass=118 warn=4 fail=0 skip=2 (unqualified pass, twins identical) - check_audit_chain.py: audit chain intact NOT done by this merge (repo-gotchas 12): git tag v1.8.23 && git push origin v1.8.23 gh release create v1.8.23 --latest Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
chore(release): v1.8.23 — the downstream-report residue, finished
Packages the four units this wave shipped, and the interesting part is that
each one unblocked the next rather than being four independent chores:
console. Its bootstrap reproduced docs(readme): de-slop EN/zh-TW README tone; release v1.2.1 #178 live.
requires. That legalised the step fix: route validate.sh inline python checks through PYTHON_BIN (#30) #88's bootstrap needed.
committed durations file turned [Bug] Validator mis-flags ship-history archive as a Work Log missing Phase Summary #171 from latent into a hard block.
which had to land before anything else could merge.
Every headline number is measured, and two were revised DOWNWARD on
measurement rather than published as predicted:
measured 13m7s then 11m24s against a 21m57s baseline = 1.67x-1.93x, recorded
as a RANGE because two runs of the same tree differed ~13%.
and 7 emit identical bytes, and the row was corrected in place.
Three greens were mutation-verified before being trusted: the directive-count
ratchet, the new detector-scope test, and the source-only call-site guard --
whose mutation run REFUTED a review panel's headline objection.
Version banners bumped on seven surfaces, enumerated by grepping the previous
version on disk rather than trusting the last release's record. Each replacement
asserted its own anchor; residual grep over all seven returns 0.
Files #182: nothing pins version consistency across those seven surfaces. This
release's own banners were bumped by hand -- same failure class as the tag step
in repo-gotchas 12, which has been forgotten twice.
Tests:
identical)
NOT done by this merge (repo-gotchas 12):
git tag v1.8.23 && git push origin v1.8.23
gh release create v1.8.23 --latest
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
🤖 Generated with Claude Code