[jaredLunde]

Fixes D5. After the matches of a file it stopped searching at a NUL byte, rg prints PATH: WARNING: stopped searching binary file after match (found "\0" byte around offset N) on stdout. It has no NUL, so the parser read it as the start of the next record's path.

Measured flags: --no-messages does not suppress it; --binary rewords it (PATH: binary file matches (...), still on stdout); --text removes it but searches binary files whole, which changes the results. So the fix is in the parser, all clients (Rust, TS, Python sync/async; sandbox-mcp uses the Rust crate): a line is the warning when it is exactly the previous record's path followed by the warning text, and parsing resumes on the next line. A file merely named like the warning stays a path. Spec: Parsing section. GNU grep -I prints nothing for such a file; busybox prints Binary file PATH matches, which has no LINE field and is already dropped. The scenario now runs on every engine (its control step no longer uses a glob, which busybox applies to the full path).

Removes the D5 xfails and the last differential tolerance (known.rs now has none). test:differential: 6/6 with rust, ts, python, python-async and mcp; search scenarios pass on local/alpine/debian-runas/readonly/tinydisk.

Stacked on #598 (D3); retarget once it lands.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HJRTKuPpNNqCLEdyUwZj64