release: v1.6.0 — the audit is closed in full, and the bytes are the caller's

[ojassug]

Ships DECISIONS §54, §55, §56 and §57. max_audit.md had been declared closed twice while findings were open; this release carries the work that actually closed it, plus one defect found afterwards by pointing an MCP client at this repository's own source.

Important

The one change that can break a startup. An unrecognized TOKENDAMPER_* enum value is now a hard error instead of being silently ignored. Nothing that worked stops working — the setting never took effect — but a stale or typo'd TOKENDAMPER_LOG_LEVEL=verbose that used to fall back to the default now fails at startup.

What ships

§54 (M7) — the Gateway forwards the caller's bytes. When an elision fired, the proxy rebuilt the request with JSON.stringify and rewrote fields it never touched:

client sent	provider received
"temperature": 1.0	"temperature":1
"seed": 12345678901234567890	"seed":12345678901234567000

The third is a different number. Elided content is now spliced into the original bytes; savings are measured on what's forwarded (48.5% claimed against 47.1% actual → 46.3% against 46.5%), and a forwarded body can no longer be larger than the one that arrived.

§55 — the LOW table was never scheduled. Nine findings that entered no wave table, which is §54's own failure mode one severity band down. L1, L7, L8 fixed; L4, L5, L9 recorded at their sites as acceptable rather than correct. L7 was rated too low — a Python function with a blank line after def was unoptimizable end-to-end: 436 → 436 bytes, against 434 → 96 for the same function without the blank line.

§56 — the measured precondition for widening elision. Not shipped behaviour. It corrects a sequencing warning that was wrong in the dangerous direction and would have produced silent unmeasured elision.

§57 — a file documenting the placeholder format is not a corrupted placeholder. regions.ts reduced 29.60% on the CLI and fell back to 0% on MCP, because the corruption scan matched the prose describing the legacy format. 22 files in this repo carry such a string — ARCHITECTURE.md and CHANGELOG.md among them — and every one was unoptimizable over MCP.

Numbering

Per §53: the roadmap reserves no numbers; a number is a fact about what shipped, assigned at ship time.

• Minor rather than patch — the same command over the same input emits different bytes.
• Minor rather than major — nothing that worked stopped working.

Verification

677 tests, typecheck, lint and build green. All three version surfaces read from dist/ and agree:

dist constant   -> 1.6.0
package.json    -> 1.6.0
MCP serverInfo  -> 1.6.0

There is no --version flag — it prints usage — so those three are the check.

🤖 Generated with Claude Code