kiro-cli exit and return 1 after integration

### 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

macOS 12.7.2 (21G1974)

### Expected behaviour

1. after install, kiro-cli can interact with user
2. after integration, it should interact with me

### Actual behaviour

1. after install, kiro-cli can interact with user
2. after integration, include grant access, kiro-cli exit with 1, there is no prompts
3. kiro-cli --tui exit 0
4. kiro-cli --classic works

### Steps to reproduce

1. install
2. .local/bin/kiro-cli works
3. integration by Kiro CLI Settings
4. grant accessbility it required
5. new terminal
6. kiro-cli : exit 0
7. kiro-cli --tui: exit 0
8. kiro-cli --classic: works

### Environment

```yaml

[q-details]
version = "2.0.1"
hash = "4a41569da83e25b6ab94898d7c4c83fa18cb5216"
date = "2026-04-17T02:21:00.156808Z (2d ago)"
variant = "full"

[system-info]
os = "macOS 12.7.2 (21G1974)"
chip = "Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz"
total-cores = 2
memory = "16.00 GB"

[environment]
cwd = "/Volumes/Data/Users/USER"
cli-path = "/Volumes/Data/Users/USER"
os = "Mac"
shell-path = "/bin/bash"
shell-version = "3.2.57"
terminal = "macOS"
install-method = "unknown"

[env-vars]
PATH = "/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/Volumes/Data/Users/USER/.local/bin:/usr/local/opt/redis@6.2/bin/:/Volumes/Data/Users/USER/Develop/apache-maven-3.9.6/bin:/Volumes/Data/Users/USER/Library/Android/sdk/platform-tools/:/Applications/scrcpy"
QTERM_SESSION_ID = "61b8b013ea6f45c1a5e85b5583bef892"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "2.0.1"
SHELL = "/bin/bash"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.apple.Terminal"
```

Inizia riproducendo il comando predefinito integrato nell’ambiente macOS segnalato, quindi confronta il suo comportamento con `kiro-cli --tui` e `kiro-cli --classic`. Usa `q doctor` e `q restart` come indicato e traccia l’integrazione e il percorso di concessione dell’accessibilità fino a identificare la causa di exit-1. Il lavoro è completato quando il comando integrato richiede input e interagisce normalmente dopo la configurazione, senza compromettere le modalità funzionanti.

Scritto dal modello di indicizzazione a partire dal testo della issue.