Quantization, spectral, and report-schema hardening

Release: InvarLock 0.3.11 - AWQ discovery, RTN clipping, and schema edge cases

Highlights

• Adds targeted regression coverage for quantization clipping, spectral guard branches, and report-schema edge cases.
• AWQ support detection now uses the lightweight awq module 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. The new regression coverage targets quantization clipping, spectral guard branches, and report-schema edge cases because those are the kinds of changes that can look small while changing review outcomes.

AWQ handling becomes safer in two places. Support detection now checks the lightweight awq module path, and plugin listing avoids importing AWQ during discovery, so ordinary introspection is less likely to trip optional dependency behavior. Spectral guard handling also recognizes gate_proj as an FFN projection in gating paths.

On the reporting and quantization side, nullable dataset window seeds and structured system_overhead payloads are accepted, while RTN outlier clipping is hardened for fp16-safe behavior. If your stack includes AWQ integrations, strict report ingestion, or quantized checkpoint paths, this patch should reduce surprise behavior without widening the public workflow surface.

Sources

Website documentation explains the maintained workflow. The changes described here belong to InvarLock v0.3.11; the tagged release record preserves that historical scope.

• Documentation
• Tagged v0.3.11 changelog