kiro-cli-term fails to launch on Ptyxis 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 7.0.0-22-generic - Ubuntu 26.04 LTS

### Expected behaviour

kiro-cli-term should launch automatically when opening a new terminal session in Ptyxis (the default GNOME terminal on Ubuntu 26.04 LTS), and `kiro-cli doctor` should pass all checks.

### Actual behaviour

`kiro-cli-term` does not launch. `kiro-cli doctor` reports:

✘ Kiro CLI terminal integrations: kiro-cli-term is not running in this terminal, please try restarting your terminal

The root cause is that `kiro-cli _ should-figterm-launch` does not recognize `ptyxis-agent` as a valid terminal emulator:

❌ ptyxis-agent | ptyxis-agent (334372) <- ✅ zsh (343580)
exit: 1

This causes `SHOULD_QTERM_LAUNCH` to be hardcoded as "1" (don't launch) in the output of `kiro-cli init zsh pre`.

### Steps to reproduce

1. Install Kiro CLI (minimal install) on Ubuntu 26.04 LTS with Ptyxis terminal
2. Run `kiro-cli integrations install dotfiles`
3. Open a new terminal session in Ptyxis
4. Run `kiro-cli doctor`
5. Observe the error: "kiro-cli-term is not running in this terminal"
6. Run `kiro-cli _ should-figterm-launch` — outputs "❌ ptyxis-agent" with exit code 1

### Environment

```yaml
[q-details]
version = "2.6.1"
hash = "979b991de95e75ddf2318f67c6d196532502cad9"
date = "2026-06-08T21:12:27.520701Z (7d ago)"
variant = "minimal"

[system-info]
chip = "11th Gen Intel(R) Core(TM) i5-1145G7 @ 2.60GHz"
total-cores = 4
memory = "30.51 GB"

[system-info.os.linux]
kernel_version = "7.0.0-22-generic"
id = "ubuntu"
name = "Ubuntu"
pretty_name = "Ubuntu 26.04 LTS"
version_id = "26.04"
version = "26.04 LTS (Resolute Raccoon)"

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

[env-vars]
DISPLAY = ":0"
PATH = "/home/USER/.local/bin:/home/USER/.sdkman/candidates/java/current/bin:/home/USER/.nvm/versions/node/v24.15.0/bin:/home/USER/.sdkman/candidates/quarkus/current/bin:/home/USER/.sdkman/candidates/maven/current/bin:/home/USER/.sdkman/candidates/java/current/bin:/home/USER/.sdkman/candidates/gradle/current/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin:/home/USER/.local/bin"
QT_IM_MODULE = "ibus"
SHELL = "/usr/bin/zsh"
TERM = "xterm-256color"
XDG_CURRENT_DESKTOP = "ubuntu:GNOME"
XDG_SESSION_DESKTOP = "ubuntu"
XDG_SESSION_TYPE = "wayland"
XMODIFIERS = "@im=ibus"
```

Beginne mit dem Einstiegspunkt `kiro-cli _ should-figterm-launch` und vergleiche dessen Umgang mit `ptyxis-agent` mit der Ausgabe von `kiro-cli init zsh pre`. Reproduziere das Problem in Ptyxis und überprüfe anschließend, dass die Terminalintegration in einer neuen Sitzung automatisch gestartet wird und dass `kiro-cli doctor` alle Prüfungen besteht.

Vom Indexierungsmodell aus dem Issue-Text verfasst.