sush command output piped to head will panic

If I try to send output to the head command, it causes sush to dump core:

alan@castle:~$ /staff/alex/sush job history | head
✅ Job ID:       book-dial-lawn-shock-insect-loop-picnic-filter
   913-0000023:2F8JEXDK  Started at 2026-09-03 15:58:14.523153172 UTC
✅ Job ID:       casual-couch-abuse-ready-wreck-demand-discover-large
   913-0000023:2F8JEXDK  Stopped, exit 0 (20s 759ms 11us 205ns), 14.2 kB out, 0 B err
✅ Job ID:       apple-custom-lab-hybrid-argue-talent-pen-keen
   913-0000019:BRM23230010  Stopped, exit 0 (9ms 141us 829ns), 334 B out, 0 B err
   913-0000019:BRM23230018  Stopped, exit 0 (8ms 432us 369ns), 334 B out, 0 B err
   913-0000019:BRM27230037  Stopped, exit 0 (6ms 616us 227ns), 334 B out, 0 B err
   913-0000023:2F8JEXDK     Stopped, exit 0 (6ms 37us 734ns), 334 B out, 0 B err
✅ Job ID:       tissue-power-ivory-hero-squeeze-trip-swim-maximum

thread 'main' (1) panicked at /rustc/8bab26f4f68e0e26f0bb7960be334d5b520ea452/library/std/src/io/stdio.rs:1166:9:
failed printing to stdout: Broken pipe (os error 32)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Reproduce the failure with sush job history | head, then trace the command's output path and Rust stdout handling from the command entry point. Confirm the behavior when the downstream pipe closes early. Done means piping output to head exits without a panic or core dump while preserving normal output.