fix: correct Windows 32-bit compiler and error handling in npm build

[Copilot]

Code review identified critical build configuration errors that would prevent Windows 32-bit binaries from building and cause incorrect exit codes when binaries are missing.

Changes

• Windows 32-bit build: Use i686-w64-mingw32-gcc instead of x86_64-w64-mingw32-gcc for 386 architecture
• Error handling: Replace || with ?? operator in wrapper script to handle null status correctly
• CI dependencies: Add gcc-mingw-w64-i686 package to both release and test workflows
• Darwin builds: Disable CGO for cross-compilation (codebase doesn't use C dependencies)

Before

process.exit(error.status || 1);  // exits with 0 if status is null

CC=x86_64-w64-mingw32-gcc  # wrong compiler for 32-bit

After

process.exit(error.status ?? 1);  // correctly exits with 1 if status is null

CC=i686-w64-mingw32-gcc  # correct 32-bit compiler

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• esm.ubuntu.com
  • Triggering command: /usr/lib/apt/methods/https /usr/lib/apt/methods/https (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[leggetter]

@copilot does 7002310 address your feedback?

[Copilot]

@copilot does 7002310 address your feedback?

Yes, commit 7002310 addresses my feedback and takes an even better approach. Instead of fixing the Windows 32-bit compiler (which I suggested), it disables CGO entirely for all platforms since the codebase has no C dependencies. This is cleaner - it eliminates the need for mingw cross-compilers completely and simplifies the build process.

The commit addresses all my review points:

• ✅ Error handling fix (error.status ?? 1)
• ✅ Darwin CGO disabled for cross-compilation
• ✅ Windows builds simplified (no compiler dependencies needed)
• ✅ Enhanced test coverage for all 6 platforms

The pure Go approach (CGO_ENABLED=0) is the right solution here.