fix: don't show EPIPE error

[alexsch01]

• Closes Error: write EPIPE after CTRL+C in terminal #30659

Additional details

Steps to test

How has the user experience changed?

PR Tasks

• Have tests been added/updated?
• Has a PR for user-facing changes been opened in cypress-documentation?
• Have API changes been updated in the type definitions?

---

Note

Suppress EPIPE errors from the config child process (e.g., after CTRL+C) and document it in the changelog.

• IPC/Config Loading:
  • Update packages/data-context/src/data/ProjectConfigIpc.ts to ignore EPIPE in child process error handlers for loadConfig() and registerSetupIpcHandlers(), preventing noisy terminal errors after CTRL+C; add explicit NodeJS.ErrnoException typing.
• Changelog:
  • Add bugfix entry noting suppression of EPIPE error after CTRL+C in cli/CHANGELOG.md.

^{Written by Cursor Bugbot for commit 068b85c. This will update automatically on new commits. Configure here.}

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

[jennifer-shehane]

@alexsch01 Any thoughts on how to test this?

[alexsch01]

@jennifer-shehane @AtofStryker
for manually testing this.....

cypress/packages/data-context/src/data/ProjectConfigIpc.ts

Line 109 in e0b4158

send (event: string, ...args: any[]) {

   send (event: string, ...args: any[]) {
+    console.log(event)
+    Atomics.wait(new Int32Array(new SharedArrayBuffer(4)), 0, 0, 4000)

• above adds an synchronous wait of 4000 ms to every event

---

run yarn cypress:run --project PROJECT_DIR

• after you see an event such as loadConfig, do a CTRL-C with vs without this PR