1.3.0Locally verified · unreleased17 October 2026
Engine & native runtime
- Strand mode 34: sparse-residual context mixing closes the sparse-image virtualization gap. A reversible zero-run fold feeds strong context mixing, with byte-exact cross-decoding between the TypeScript encoder and native decoder.
- Context-mixing model progressed v2 → v6: bit-history state maps, richer text contexts, long-order and indirect-model contexts behind frame version bits, with strict profile selection.
- Native fast tier: stream I/O overlaps compute and match-chain walks prefetch candidates. Output stays byte-identical, with higher throughput on the same machine.
- Reversible domain modes recorded and verified byte-exact: PNG (27), signal (28), ZIP (29), WAV (30), raster (32) and PDF (33); SQLite and archive samples measured.
- Robustness: bounded-memory hardening rejects pathological PPM inputs instead of exhausting memory.
- A native Linux x64 runtime is built and tested beside the macOS reference (codec, native and app suites green).
- Hosted large-file delivery: resumable verified part streams with checkpoint continuation, admitting files up to 5 TiB.
- Published evaluation suites re-measured on 18 October 2026 with the current revision under a uniform whole-command CLI method; the prior fast chart mixed in-process Saar timings with CLI competitor timings and has been replaced.
- All 31 workload classes now carry a dated measurement (30 wins, 1 loss shown in place); real public samples replaced generated fixtures for six previously unsampled classes.
- Point-cloud mode 35: LAS point records are transposed into delta-coded numeric columns before PPM coding; both real LiDAR samples now beat xz -9 (49,566 vs 53,228 and 68,640 vs 89,124), byte-exact across TypeScript and native decoders.
- Structured-text mode 36: hex runs are packed two characters per byte and a fixed JSON/OCI/HTTP vocabulary is substituted before coding; the cloud manifest now beats brotli -q11 (584 vs 588), byte-exact across TypeScript and native decoders.
Excluded from this entry
- The earlier lossy JSON prototype figures (−20% to −33% on World Bank JSON) are retracted: they were not byte-reversible. The exact record-engine payoff measured is ~6% on tabular CSV.
- No performance, security or compliance claim beyond the dated records in evidence/ is made.
