"Agent connection closed unexpectedly" during mid-answer

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

Linux 6.18.33.2-microsoft-standard-WSL2 - Kali GNU/Linux Rolling

### Expected behaviour

I expect not to crash. The only solution is just to use /exit and restart the same session.

### Actual behaviour

The kiro-cli stops reposnding after, even certain / commands wont work. Needs to be restarted.

### Steps to reproduce

Randomly happening very frequently

### Environment

```yaml

[q-details]
version = "2.12.0"
hash = "dadabd517d97d983075d024197e594c9499043be"
date = "2026-07-09T02:16:33.224593Z (7h ago)"
variant = "minimal"

[system-info]
chip = "11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz"
total-cores = 4
memory = "15.46 GB"

[system-info.os.linux]
kernel_version = "6.18.33.2-microsoft-standard-WSL2"
id = "kali"
name = "Kali GNU/Linux"
pretty_name = "Kali GNU/Linux Rolling"
version_id = "2024.4"
version = "2024.4"

[environment]
cwd = "/home/USER/workspace/ab"
cli-path = "/home/USER/workspace/ab"
os = "Linux"
shell-path = "/usr/bin/zsh"
shell-version = "5.9"
install-method = "unknown"
in-wsl = true

[env-vars]
DISPLAY = ":0"
PATH = "/home/USER/.local/bin:/home/USER/.opencode/bin:/home/USER/.nvm/versions/node/v22.22.0/bin:/home/USER/.cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib:/home/USER/.local/bin"
QTERM_SESSION_ID = "f0e4dab1eefb448ab9bbf62e5fb6b0d0"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "2.12.0"
SHELL = "/bin/bash"
TERM = "xterm-256color"
```

Es sind keine Quelldatei und kein Test identifiziert. Beginne mit dem gemeldeten q doctor- und q restart-Workflow im betroffenen WSL2-Terminal und beobachte dann den Verbindungsfehler mitten in der Antwort sowie, ob Befehle weiterhin reagieren. Erledigt ist es, wenn der Agent nicht mehr unerwartet geschlossen wird und die Sitzung nicht /exit und einen Neustart erfordert.

Vom Indexierungsmodell aus dem Issue-Text verfasst.