This release adds 3 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+9 more
Affected surfaces
Summary
AI summaryFixed type‑unsafe ledger reads that could silently disable blocking and briefing.
Full changelog
## v0.8.1 — the review release
Before launch week, an independent adversarial review went over everything shipped in v0.6-v0.8. It found 7 major bugs — every one verified by execution before being fixed. This release fixes all of them, plus the minor findings, with 9 new regression tests (84 total).
Highlights
- Thrash escalation actually fires now — one old large wall no longer silences every new wall forever.
rl importis hardened — strict validation, field truncation, ledger cap enforcement. A hostile export can no longer kill the guardrail, grow a 44 MB ledger, or inject unbounded text into your agent's context.- Type-unsafe ledger reads fixed — a single malformed entry could previously disable blocking AND briefing for a file, silently (fail-open hid it).
- Classifier regressions fixed —
error:prose in passing runs,mvn dependency:tree, "200 OK", "0 passed" all misclassified; explicit toolchain pass evidence now outranks generic fail substrings. rspec/phpunit restored,node --testadded. - Structural channel: 15-token floor (no more guard-clause noise), 3000-token cap (no more multi-second Writes).
Honest accounting: 5 of the 7 majors were introduced by features shipped earlier today. Shipping fast creates bugs; reviewing adversarially catches them. Both halves matter — this project tracks failed fixes for a living, so the changelog keeps its own ledger honest.
84 tests - benchmark 120/120 caught, 0/190 false blocks - zero dependencies.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About Regressionledger
All releases →Related context
Related tools
Beta — feedback welcome: [email protected]