Tianyi Cui 7097e4fb50 docs(bash-local): clarify the stdin error handler swallows ANY write error, not just EPIPE ... Review noted the handler's comment said "EPIPE" while the code swallowed every stdin 'error'. Swallowing any stdin-write error IS correct here — the write is best-effort and the command's authoritative outcome is its exit code + captured output (reported by the `close` handler regardless of whether the write landed). A rare non-EPIPE pipe fault means the command ran with incomplete stdin, which it surfaces itself via its own exit/output; rejecting `done` would instead discard that real output and turn it into an opaque infrastructure error. Widen the comment to state this rather than implying only EPIPE is caught. No behavior change.		2026-07-01 15:23:09 +08:00
..
index.ts	feat(bash): add stdin + extra env to the executor seam as a trusted-plugin surface	2026-06-30 13:52:25 +08:00
run.ts	docs(bash-local): clarify the stdin error handler swallows ANY write error, not just EPIPE	2026-07-01 15:23:09 +08:00