q doctor CLI path validation error persists after correct symlink setup

### 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 15.5.0 (24F74)

### Expected behaviour

* q doctor should validate the CLI path successfully when a correct symbolic link is created at ~/.local/bin/q pointing to the Amazon Q executable

### Actual behaviour

* q doctor continues to show error: "Valid CLI path: CLI (/Users/****/.toolbox/tools/q/1.12.6/Amazon Q.app/Contents/MacOS/q) must be in /Users/***/.local/bin/q" despite having the correct symbolic link in place

### Steps to reproduce

1. Install Amazon Q
2. Run q doctor (shows CLI path error)
3. Create symbolic link using: ln -s "/Users/****/.toolbox/tools/q/1.12.6/Amazon Q.app/Contents/MacOS/q" ~/.local/bin/q
4. Verify link exists and is correct using: ls -l ~/.local/bin/q
5. Run q doctor again - error persists despite correct setup
6. System details: macOS (include version if known)

### Environment

```yaml

[q-details]
version = "1.12.6"
hash = "9c083cf7e8f7de077eb116c3993823b82f71ca12"
date = "2025-07-18T21:39:58.652366Z (2d ago)"
variant = "full"

[system-info]
os = "macOS 15.5.0 (24F74)"
chip = "Apple M1 Pro"
total-cores = 10
memory = "32.00 GB"

[environment]
cwd = "/Users/USER"
cli-path = "/Users/USER"
os = "Mac"
shell-path = "/Users/USER/.toolbox/tools/toolbox/1.1.1986.0/toolbox-exec"
shell-version = "5.9"
terminal = "iTerm 2"
install-method = "toolbox"

[env-vars]
PATH = "/Users/USER/.config/smithy-mcp/mcp-servers:/opt/homebrew/opt/tomcat@8/bin:/Library/Java/JavaVirtualMachines/amazon-corretto-8.jdk/Contents/Home/bin:/opt/homebrew/opt/node@18/bin:/Users/USER/.toolbox/bin:/Users/USER/.console-ninja/.bin:/Users/USER/Documents/Apache/apache-maven-3.9.3/bin:/Users/USER/.pyenv/shims:/opt/homebrew/bin:/opt/homebrew/sbin:/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:/Library/Apple/usr/bin:/usr/local/MacGPG2/bin:/Users/USER/.cargo/bin:/Applications/iTerm.app/Contents/Resources/utilities:/Users/USER/.local/bin:/Users/USER/Library/Application Support/JetBrains/Toolbox/scripts"
QTERM_SESSION_ID = "418524e477ae46edb74e91d6c880e070"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.12.6"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.googlecode.iterm2"
```

Inizia riproducendo il problema con q doctor dopo aver creato il symlink documentato su macOS, quindi confronta il percorso CLI segnalato con la destinazione del link. Traccia il punto di ingresso della convalida dei percorsi di q doctor; il lavoro è terminato quando un symlink corretto ~/.local/bin/q viene accettato senza l’errore di convalida persistente.

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