[YOMXXX]

Summary

• handle BrokenPipe while writing rtk read output instead of panicking
• skip gain tracking when downstream consumers stop reading before the full read output is delivered
• add a regression test for rtk read <file> | head -c ... with an isolated tracking DB

Issue

Addresses #2468 for the rtk read broken-pipe/partial-output path.

Verification

• cargo +1.93.0 test --all -- --skip small_grep_not_worse_than_plain before changes: passed
• cargo +1.93.0 test --test read_broken_pipe_test -- --nocapture before fix: failed with failed printing to stdout: Broken pipe
• cargo +1.93.0 test --test read_broken_pipe_test -- --nocapture: passed
• cargo +1.93.0 test read::tests -- --nocapture: passed
• cargo +1.93.0 fmt --check: passed
• git diff --check: passed
• cargo +1.93.0 clippy --all-targets: passed
• cargo +1.93.0 test --all -- --skip small_grep_not_worse_than_plain: passed

[rtk-release-bot]

This pull request has been automatically marked as stale due to 90 days of inactivity. If this pull request is still relevant, please leave any comment (for example, "bump"), and we'll keep it open. Your contribution is very much appreciated — we're sorry we haven't been able to review it yet.

[KuSh]

#1048 (merged 2026-05-29) resets SIGPIPE to its default in main, so on Linux and macOS rtk read <file> | head -c 10 already exits cleanly without recording a gain row. What develop still lacks from this branch is the BrokenPipe-tolerant write around the two print! calls in src/cmds/system/read.rs, which still matters on platforms without SIGPIPE such as Windows, together with tests/read_broken_pipe_test.rs. Could you rebase onto current develop and narrow the PR to that part? read.rs has since been restructured around head and tail windows, so expect conflicts, but the two print sites you wrap are still there. The window paths in the same file still turn a closed pipe into a "Failed to write line window" error on Windows; your helper could cover them here, or they can go to a separate narrow PR. Thanks for the fix.