[Bug] Print mode crashes with segfault on Windows; interactive mode fails on non-C: drives

Bug Description
[Windows] Claude Code 2.1.31 - Two distinct Bun 1.3.5 crash issues:

Issue 1: Print mode (-p) completely broken - NO WORKAROUND

• claude -p "any prompt" crashes with segfault on ALL drives (C:, D:, etc.)
• claude --version works fine
• This breaks all non-interactive/scripting use cases

Issue 2: Interactive mode crashes from non-C: drives - HAS WORKAROUND

• claude (interactive) crashes when CWD is D: drive
• Works fine when CWD is C: drive
• Workaround: Start from C: and use --add-dir D:\path

Environment:

• Windows 11 Enterprise
• Claude Code 2.1.31
• Both C: and D: are local NTFS fixed drives

Crash signature (identical for both):
panic(main thread): Segmentation fault at address 0xFFFFFFFFFFFFFFFF
https://bun.report/1.3.5/e_11e86cebGugogCg1zlIkzi3d43+1uB4pmyuB65jyuBy2i5Io37nG2nowmBy0rwFmtb4hMop/oyDCYKERNEL32.DLLut0LCSntdll.dll4gij
BA2DD

Related issues: #19453, #20147, #20148 (same Bun crash signature but don't mention print mode or drive-specific conditions)

Diagnostic evidence: Tested with minimal config (no plugins/hooks) - same crash, confirming it's a core Bun/Claude Code issue, not
configuration.

This clearly distinguishes:

• Issue 1: No workaround available (print mode broken everywhere)
• Issue 2: Workaround exists (use --add-dir from C:)

Environment Info

• Platform: win32
• Terminal: windows-terminal
• Version: 2.1.31
• Feedback ID: 19304a2c-301c-4916-9394-3cd38aa7fc78