chore(oxfmt): Add comment for setBlocking(true)

[leaysgur]

Follow up #20289 , just adding comments.

[leaysgur]

• chore(oxfmt): Add comment for setBlocking(true) #20323 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent changes, fast-track this PR to the front of the merge queue

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Copilot]

Pull request overview

This PR improves the inline documentation around why the oxfmt JS CLI forces stdin/stdout into blocking mode when running under non‑TTY (piped) I/O, clarifying separate failure modes for output vs input and linking to relevant upstream issues.

Changes:

• Refines the existing explanation of Node.js non‑TTY stdio being non‑blocking and how that surfaces as Rust WouldBlock/EAGAIN errors.
• Splits the rationale into distinct stdout and stdin sections with concrete repro contexts (--stdin-filepath and --lsp) and issue links.

---

You can also share your feedback on Copilot code review. Take the survey.

[leaysgur]

Merge activity

• Mar 13, 4:29 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Mar 13, 4:38 AM UTC: leaysgur added this pull request to the Graphite merge queue.
• Mar 13, 4:56 AM UTC: Merged by the Graphite merge queue.