it wont run when i type in kiro-cli

### 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 26.6.1 (25G76)

### Expected behaviour

when I type Kiro-cli it will open the cli version

### Actual behaviour

It just say
kiro-clierror: No such file or directory (os error 2)

### Steps to reproduce

_No response_

### Environment

```yaml

[q-details]
version = "2.18.1"
hash = "74b78bb5a369788e393b06654b2b213d937a41d2"
date = "2026-08-13T23:20:56.707604Z (4d ago)"
variant = "full"

[system-info]
os = "macOS 26.6.1 (25G76)"
chip = "Apple M4"
total-cores = 10
memory = "16.00 GB"

[environment]
cwd = "/Users/USER/Desktop/python"
cli-path = "/Users/USER/Desktop/python"
os = "Mac"
shell-path = "/bin/zsh"
shell-version = "5.9"
install-method = "brew"

[env-vars]
PATH = "/opt/homebrew/opt/ruby/bin:/opt/homebrew/lib/ruby/gems/4.0.0/bin:/Users/USER/.local/bin:/opt/homebrew/opt/openjdk/bin:/Users/USER/.codeium/windsurf/bin:/Users/USER/.local/bin:/opt/homebrew/opt/ruby/bin:/opt/homebrew/lib/ruby/gems/4.0.0/bin:/Users/USER/.local/bin:/opt/homebrew/opt/openjdk/bin:/Users/USER/.codeium/windsurf/bin:/Users/USER/.local/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/pkg/env/global/bin:/opt/homebrew/bin"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
ZDOTDIR = "/Users/USER/.cache/terax/shell-integration/zsh"
__CFBundleIdentifier = "app.crynta.terax"
```

Inizia riproducendo `kiro-cli` nell’ambiente macOS zsh segnalato dopo aver eseguito `q doctor` e `q restart`, quindi verifica come viene installato il comando CLI e come viene risolto tramite PATH. Il lavoro è completato quando hai identificato perché il comando restituisce `No such file or directory` e confermato che il comando apre la CLI oppure che il problema è stato diagnosticato chiaramente.

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