release: v1.6.1 - #44
Merged
Merged
Conversation
Closes oxaudit.md Lane A in full and Lane B but for M8 and M9, which are held open as decisions rather than work. Headline, in the order the notes lead with them: - §62 withdraws --trace-output / TOKENDAMPER_TRACE_OUTPUT and the `explain` value of --mode / TOKENDAMPER_APP_MODE. Nominally breaking: neither was ever read by anything, so nothing that took effect stops taking effect, but a wrapper passing --trace-output stderr now exits non-zero. A config file still carrying traceOutput keeps loading. - §61 makes Go the fourth language that elides -- 27.46% on application Go, 19.42% on the stdlib at target 0.3, with the 287-file main corpus 574/574 byte-identical because every Go path is gated on the language. - §64 turns debtScore from a constant pinned at its 35.00 clamp on 317/317 rows into a measurement tracking the byte cut at correlation 1.0000. - §65-§68 fix four Gateway defects that reached provider traffic: one `content: null` turn zeroing a whole request's saving, streaming responses truncated at 30s, within-payload dedup dead on turn 1, and region pricing registering blocks it discarded. - §58 --keep-docstrings and the pruned-file warning, both from dogfooding rather than the audit. Numbered a patch by explicit decision at ship time. Recorded in CHANGELOG, CLAUDE.md and the status doc that output did move -- Go elision and §64 both change what the same command emits -- so the patch digit is not evidence of byte stability. §53's rule is unchanged. Also corrects a changelog defect found while cutting this: nine post-v1.6.0 entries had been written into the already-released `## [v1.6.0]` section rather than [Unreleased] -- §62's Removed block and the OX-H1/H3/M2/M3/M10/M11/M12/M14 fixes. Verified by diffing that section against the v1.6.0 tag; it is now byte-identical to what v1.6.0 actually shipped, and the entries appear under the release that contains them. Verified: typecheck, lint and build clean; 91 files / 826 tests passing. The built artifact reports 1.6.1 three ways -- dist/src/version.js, package.json, and MCP serverInfo.version. 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
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.
Cuts v1.6.1 from the 24 commits on
mainsince thev1.6.0tag.The number
Numbered a patch by explicit decision at ship time. Recorded plainly in the changelog lede,
CLAUDE.mdand the status doc that output did move — Go elision (§61) and thedebtScorefix(§64) both change what the same command emits for the same input, which is normally this project's
threshold for a minor (DECISIONS §53). The patch digit is not evidence of byte stability, and the
notes say so where a reader deciding whether to upgrade will see it. §53's rule is unchanged for
the next release.
What ships
--trace-output/TOKENDAMPER_TRACE_OUTPUTwithdrawn, andexplainrejected from--mode/TOKENDAMPER_APP_MODE/ the config file. Nominally breaking: neither was ever read, so nothing that took effect stops taking effect — but a wrapper passing--trace-output stderrnow exits non-zero. A config file still carryingtraceOutputkeeps loading.debtScorewas a constant pinned at the 35.00 clamp on 317/317 rows carrying debt. Now tracks the byte cut at correlation 1.0000, with all 578 rows byte-identical.content: nullmessage no longer zeroes a whole request's Gateway saving (8,685 sent / 8,685 forwarded before).--keep-docstrings, opt-in, plus a CLI warning when the knapsack drops whole files.A changelog defect fixed in passing
Nine post-v1.6.0 entries had been written into the already-released
## [v1.6.0]section insteadof
[Unreleased]— §62's whole### Removedblock plus the OX-H1/H3/M2/M3/M10/M11/M12/M14 fixes.Found by diffing that section against the
v1.6.0tag. Left alone, this release's notes would havesilently omitted the breaking change and eight user-visible fixes, while v1.6.0's notes kept
claiming it removed
--trace-output— which the published 1.6.0 tarball still accepts.The
[v1.6.0]section is now byte-identical to what the tag shipped, verified by the samediff, and the entries sit under the release that contains them.
Verification
npm run typecheck,npm run lint,npm run build— cleannpm test— 91 files, 826 tests passing1.6.1all three ways thereleaseskill requires:dist/src/version.js,package.json, and MCPserverInfo.versionsrc/version.tswas flattened bysed -iand repaired; the diff is one line)npm publishis deliberately not run here — it needs the maintainer's 2FA.🤖 Generated with Claude Code