Skip to content

QR 0.3.13: selected mesh recovery

Choose a tag to compare

@TheCryptoDonkey TheCryptoDonkey released this 17 Nov 08:20
b1d9507

QR 0.3.13 improves recovery of curved QR codes using an already sampled alignment mesh.

Some curved QR images produce a usable direct alignment mesh, while the final refined grid still fails validation. Retain the existing mesh from the same invocation that selected the rediscovered header, then try it once under that strict hypothesis only after every earlier path fails. Preserve version, Reed–Solomon and segment checks and earlier successful results.

The packaged TypeScript/WASM reads 653/1,120 evaluated curves, up from 648/1,120 in 0.3.12, compared with ZXing-WASM 3.1.7 at 569/1,120. Five new reads include one in a separate 128-image set frozen before evaluation. Previous full successful results, inputs and search counts remain unchanged across the qualification. Rust and Kotlin implement the same policy; SPEC step 20 and two generated conformance frames describe it. No image sampling or second looks are added. The retained-grid bound is 281,961 module bytes, excluding active buffers and metadata; packaged WASM grows by 404 bytes to 252,923.

Validation: 511 TypeScript tests with required photographs; 123 Kotlin tests; 49 Rust tests plus a doctest under default/all-feature configurations; 84 standalone WASM frames/672 counters, 1,745 option comparisons, 148 encoder vectors, grid/render parity and a stable 1,000-round capacity check. Final packaged parity covers 1,120 curves, 888 regressions including 64 negative controls, 2,944 photo views and 18 sheets. Browser, worker, character-set and session/reset checks pass.

Across two paired M4 runs, the five new reads change WASM median latency by 0.19–0.89% relative to the earlier misses. The two selected-mesh cases that still fail to decode change by -0.24–0.40%; earlier successful curved cases change by -0.45–0.84%. These measurements do not establish a general speed improvement or a worst-case bound.

The paired pure-TypeScript clean-frame median rises from 3.785–3.824 ms to
3.968–4.017 ms (3.77–6.15% per fork); blank-frame medians rise from
2.937–2.953 ms to 3.077–3.080 ms (4.32–4.78%). These measured regressions
are part of the accuracy trade-off. Their cause is not established by these
timings; no general TypeScript speed improvement is claimed.

Prepublication passed: documentation freshness, eight pages’ metadata and landing-page layout at 390/1280 px; isolated npm and Maven consumers; packaged crate library/doctest checks and Rust API documentation with warnings denied; JSR strict dry run, source consumer and actual publisher archive captured on loopback. Public registry consumers remain a post-publication verification step.

Available on npm and JSR as @forgesworn/qr@0.3.13, crates.io as forgesworn-qr 0.3.13, and Maven Central as io.github.forgesworn:qr:0.3.13. Published npm/JSR/Maven consumers, crate source/checksum and docs.rs, thirteen documentation files and six CDN files have been verified.

Complete release verification links the seven successful CI/release workflows and six public verification reports. All seven attached reports were downloaded again and matched against the local evidence.