wired behavior after sudden stop

**Describe the bug**

I have reproduced this issue in multiple v2 versions.

it is not just happens at debug time, also happens in my prod env

https://github.com/user-attachments/assets/69342ce5-42a9-497d-a164-5d86f9ba8bb0

**To Reproduce**

step1.
choose one example file in official repo. e.g. `bubbletea/examples/mouse/main.go`

step2.
use vscode to debug it. launch.json is like this

···
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "Debug Current File",
"type": "go",
"request": "launch",
"mode": "debug",
"program": "${fileDirname}",
"args": [],
"console": "integratedTerminal",
"env": {
"LOG_LEVEL": "debug"
},
"showLog": true,
"trace": "verbose"
}
]
}
···

step3.

click stop debugger button.

then the whole screen runs into a mass.

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**

**Additional context**
Add any other context about the problem here.

Reproduce the problem with bubbletea/examples/mouse/main.go using the provided VS Code launch.json, then stop the debugger and observe the terminal screen. Start by comparing behavior in debug and production environments. Done means the terminal remains usable after the debugger is stopped.

Written by the indexing model from the issue text.