`Kiro CLI Chat hangs silently with no output on Arch Linux (Kitty/Gnome Terminal)`.

### 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.12.57-1-lts - Arch Linux

### Expected behaviour

I expected 'kiro-cli chat' to launch, display the interactive chat interface (including the Kiro CLI logo and welcome messages), and allow me to start chatting with Kiro.

### Actual behaviour

When I run 'kiro-cli chat' in my terminal, it shows no output whatsoever and appears to hang indefinitely. It never displays the interactive chat interface, and no error messages are presented.

### Steps to reproduce

_No response_

### Environment

```yaml

[q-details]
version = "1.24.1"
hash = "ffce156030f05d9cec3d4817c3a64245a967db74"
date = "2026-01-27T20:40:33.213575Z (6d ago)"
variant = "minimal"

[system-info]
chip = "Intel(R) Core(TM) i3-1005G1 CPU @ 1.20GHz"
total-cores = 2
memory = "3.64 GB"

[system-info.os.linux]
kernel_version = "6.12.57-1-lts"
id = "arch"
name = "Arch Linux"
pretty_name = "Arch Linux"
build_id = "rolling"

[environment]
cwd = "/home/USER"
cli-path = "/home/USER"
os = "Linux"
shell-path = "/usr/bin/zsh"
shell-version = "5.9"
terminal = "Kitty"
install-method = "unknown"

[env-vars]
DISPLAY = ":1"
PATH = "/home/USER/miniconda3/bin:/home/USER/miniconda3/condabin:/home/USER/.local/bin:/home/USER/.nvm/versions/node/v22.19.0/bin:/home/USER/.cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/USER/.local/bin"
QTERM_SESSION_ID = "1bde5181c17a40e891b2771a82228fe5"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.24.1"
SHELL = "/usr/bin/zsh"
TERM = "xterm-kitty"
XDG_CURRENT_DESKTOP = "Hyprland"
XDG_SESSION_DESKTOP = "Hyprland"
XDG_SESSION_TYPE = "wayland"
```

Beginne damit, `kiro-cli chat` unter Arch Linux in Kitty und GNOME Terminal zu reproduzieren, und führe dann `q doctor` und `q restart` in der betroffenen Sitzung aus. Verfolge den Einstiegspunkt beim Chat-Start und vergleiche das Verhalten des Terminals und der Umgebung. Als erledigt gilt die Aufgabe, wenn die Benutzeroberfläche auf dem gemeldeten Setup mit sichtbarer Ausgabe oder einer eindeutigen Diagnose startet.

Vom Indexierungsmodell aus dem Issue-Text verfasst.