fix(rg): preserve default binary-match reporting for explicit inputs

[chaliy]

Motivation

• A NUL-byte check introduced a blanket skip for binary inputs because stdin, explicit paths, and recursively discovered files were collapsed into (filename, content) tuples, losing provenance and causing false negatives for explicit files and stdin.
• Goal: match ripgrep semantics where default binary skipping applies to recursively discovered files but explicit file arguments and stdin should report binary file matches ... by default.

Description

• Introduce RgSearchInput with fields filename, content, and skip_binary_by_default and replace Vec<(String,String)> with Vec<RgSearchInput> for RgCollectedInputs to preserve input provenance (crates/bashkit/src/builtins/rg/mod.rs).
• Mark stdin and explicit path reads with RgSearchInput::explicit(...) (no default skip) and mark recursively discovered/indexed files with RgSearchInput::recursive(...) (default-skip enabled).
• Change the main search loop to consult input.skip_binary_by_default when deciding whether a NUL-containing input should be silently skipped, so explicit inputs and stdin produce ripgrep-style binary summaries by default.
• Add regression assertions to test_rg_binary_text_modes to cover explicit binary file argument and binary stdin behavior under default mode.

Testing

• Ran cargo test -p bashkit test_rg_binary_text_modes, which passed (1 passed; 0 failed).
• The modified test_rg_binary_text_modes now includes assertions for explicit binary path and binary stdin and these assertions succeeded.

---

Codex Task

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	bashkit	a210074	Commit Preview URL	May 25 2026, 04:34 PM