Implementation Specs

In this section

• Implementation m001 — CI pipeline and release process

  Status: In Progress (documents the shipped pipeline; §5 records the gaps) Owner: yqr maintainers Last updated: 2026-07-29 Related: yqr-m004 (crates.io release posture), yqr-m003 (the shared corpus the test job runs), yqr-f010 (the website workflow)

• Implementation m002 — Fidelity-Engine Adapter (the a001 §4.3 seam)

  Status: In Progress (read floor shipped on the single noyalib backend via yqr-f002; backend A retired in yqr-m005; write tier unstarted — yqr-b004 is its driver) Owner: yqr maintainers Last updated: 2026-07-03 Implements: yqr-a001 §4.3 (the source/span implementation seam) Related: yqr-b001 (t...

• Implementation m003 — Shared real-world corpus for validation and benchmarks

  Status: Done Owner: yqr maintainers Last updated: 2026-07-08 Related: yqr.f001 (the filter language under test), yqr-f002/yqr-f003/yqr-f004 (the fidelity engines), yqr-m002 (the engine seam)

• Implementation m004 — crates.io release posture (git-dep fidelity backends)

  Status: Done — yqr is published to crates.io (0.2.1, 2026-07-10). The dependency blockers were resolved (noyalib re-pinned to crates.io 0.0.14; rust-yaml-rt removed via the single-engine consolidation, yqr-m005), leaving zero git deps, and the maintainer's cargo publish has landed — cargo ins...

• Implementation m005 — Single YAML engine: consolidation on noyalib

  Status: In Progress — implemented and green (clippy -D warnings, 118 tests, benches compile); pending review/merge. yqr owns its Value (src/value.rs), so the engine is a swappable detail (§3). Owner: yqr maintainers Last updated: 2026-07-10 Related: yqr-r002 (noyalib evaluation), yqr-m002 (eng...