Bug Specs

Bug reports and resolutions (yqr-bNNN-*). yqr-b000-bug-status.md tracks every bug and its current state.

In this section

Bug Status Tracker

Single source of truth for the state of every yqr-bNNN bug. Update this file in the same change that opens, advances, or resolves a bug (mirrors the feature status tracker convention).

Bug b001 — Round-trip through `rust-yaml` discards whitespace, comments, and formatting

Status: Resolved for the default read (yqr-f009, 2026-07-11). Byte fidelity is now the default: yqr '.' f is byte-for-byte identical to f (the §2/§12 north-star), served by the fidelity engine (yqr-f002) with no flag. The lossy semantic round trip described below still exists but is now opt-in ...

Bug b002 — noyalib CST deficiencies: span boundaries, duplicate-key policy, and the string-only key model

Status: Resolved — all seven fixes are now in the upstream noyalib 0.0.14 release (2.1 shipped in 0.0.13; 2.2–2.7 folded into the v0.0.14 release, noyalib#160, whose CHANGELOG records the five CST span_at fixes, the scanner lone-CR fix, and loader KeyCollision parity). yqr now consumes them f...

Bug b003 — rust-yaml fork `RoundTripDocument::parse_all` errors on a trailing `...` after a block collection

Status: Resolved — moot (2026-07-10). The rust-yaml fork RoundTripDocument backend was removed when yqr consolidated on noyalib (yqr-m005), so this fork bug no longer affects yqr. (The upstream fork issue itself is unchanged.) Severity: Medium — breaks the a001 byte-for-byte identity of --eng...

Bug b004 — noyalib CST mutation-API gaps: comment editing, key rename, sequence reorder, nested/multi-line delete

Status: Resolved (2026-08-02) — every gap below ships in noyalib 0.0.18 (crates.io 2026-07-31, GitHub release v0.0.18 the same day), and yqr is pinned to it as of yqr-f013. Verified against the published .crate, not just the branch: src/cst/emit.rs is present, cst/mod.rs re-exports pub use emit...