Release
Targeted regression hardening for quantization and reporting paths
A focused hardening release: safer AWQ plugin discovery, stronger quantization clipping behavior, and broader report-schema acceptance for edge payloads.
Release: InvarLock 0.3.11 - Focused regression and schema hardening
Highlights
- Adds targeted regression coverage for quantization clipping, spectral guard branches, and report-schema edge cases.
- AWQ support detection now uses the lightweight
awqmodule path, and plugin listing avoids importing AWQ during discovery. - Reporting now accepts nullable dataset window seeds and structured
system_overhead, while RTN outlier clipping is hardened for fp16-safe behavior.
0.3.11 is intentionally focused: reinforce sensitive pathways that can cause subtle failures in production-grade evaluation pipelines. It improves predictability in plugin discovery, report parsing, and quantization safety without changing the workflow surface.
If your stack includes AWQ integrations or strict report ingestion, this release should reduce surprise behavior and improve confidence in edge-case handling.
For more details, see CHANGELOG.md.
More from the blog
Continue through recent releases and implementation notes.
Release
Stable public contracts with stricter fail-closed verification
InvarLock 0.4.0 stabilizes contracts around policies, proof packs, and evaluation provenance while tightening verification, CI, and coverage enforcement.
Release
Coverage hardening across CLI, reporting, and observability paths
Coverage thresholds now enforce split-module branch floors for critical CLI/reporting paths.
Release
Bigger proof-pack coverage with stronger CI reproducibility
Proof packs add new showcase and evidence artifacts, while CI and release flows become more deterministic and easier to validate repeatedly.