Stop reporting user/environment errors as unexpected bugs in Bugsnag

Add 'write EPIPE' and 'Unsupported platform' to
errorMessageImpliesEnvironmentIssue so they are no longer flagged
as unhandled CLI bugs in error-analytics.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: lucyxiang

packages/cli-kit/src/public/node/error.test.ts

@@ -74,4 +74,12 @@ describe('shouldReportErrorAsUnexpected helper', () => {
   test('returns false for user-aborted requests', () => {
     expect(shouldReportErrorAsUnexpected(new Error('The user aborted a request.'))).toBe(false)
   })
+
+  test('returns false for EPIPE errors', () => {
+    expect(shouldReportErrorAsUnexpected(new Error('write EPIPE'))).toBe(false)
+  })
+
+  test('returns false for unsupported platform errors', () => {
+    expect(shouldReportErrorAsUnexpected(new Error('Unsupported platform: win32 arm64 LE'))).toBe(false)
+  })
 })

packages/cli-kit/src/public/node/error.ts

@@ -234,6 +234,8 @@ function errorMessageImpliesEnvironmentIssue(message: string): boolean {
     'spawn EPERM',
     'socket hang up',
     'The user aborted a request.',
+    'write EPIPE',
+    'Unsupported platform',
   ]
   const anyMatches = environmentIssueMessages.some((issueMessage) => message.includes(issueMessage))
   return anyMatches