[Windows] CTRL_C_EVENT not handled by bun (umbrella issue)

[kommander]

This is to collect issues that are reporting ANSI escape sequences after CTRL+C in some windows terminals and shell, where it sends a CTRL_C_EVENT which is not handled by bun.

• Pressing Ctrl+C in input field outputs ANSI escape sequences/garbled text #7062
• Ctrl+C does not disable mouse tracking, causing raw escape sequences to flood terminal (Windows) #6912

[github-actions]

This umbrella issue appropriately collects ANSI escape sequence issues related to CTRL_C handling. Additional related issues found:

• In the Windows system, pressing Ctrl+C will automatically exit the terminal #6189: In the Windows system, pressing Ctrl+C will automatically exit the terminal
• Bug: Ctrl+C interruption in opencode causes terminal corruption with ANSI escape sequences #5990: Ctrl+C interruption causes terminal corruption with ANSI escape sequences
• Provide a way to stop all running scripts when OpenCode is interrupted #3057: Ctrl+C should terminate child processes
• Provide means to disable Ctrl-C #2999: Provide means to disable Ctrl-C (Windows quits app instead of copy)
• bug: ctrl+c exiting app even when prompt input isn't empty #5071: Ctrl+C exiting app even when prompt input isn't empty

All of these appear to stem from improper CTRL_C_EVENT and signal handling on Windows. The umbrella issue structure is good for tracking the root cause.

[Hona]

on windows bun, the ctrl+c sigint gets sent to all process+childprocess, so the bun run wrapper instantly kills its child.
i need to check what happens with the published app too...
i have a bun wip branch that is a poc fixing this, but it janky.
not sure its something opentui/opencode can handle as a workaround if its parent process is killing it