/status incorrectly reports ~/.local/bin not in PATH despite being configured

Bug Description

The /status command in Claude Code v2.1.34 incorrectly reports that ~/.local/bin is not in the PATH, despite it being properly configured and working correctly.

Environment

• Claude Code Version: v2.1.34
• OS: macOS (Darwin 21.6.0)
• Shell: zsh (/bin/zsh)
• Session ID: 35cc2aaa-f51f-4801-80d7-19bcdf88105a

Current Status

PATH is correctly configured:

$ python3 -c "import os; print(os.environ['PATH'].split(':')[0])"
/Users/wonseok/.local/bin

$ which claude
/Users/wonseok/.local/bin/claude

Shell configuration files (all have the required setting):

.zshrc (lines 19 and 22):

export PATH="$HOME/.local/bin:$PATH"

.zshenv:

export PATH="$HOME/.local/bin:$PATH"

.zlogin:

export PATH="$HOME/.local/bin:$PATH"

Expected Behavior

The /status command should recognize that ~/.local/bin is in the PATH and not display any warnings.

Actual Behavior

The /status command displays:

System Diagnostics
 ⚠ Native installation exists but ~/.local/bin is not in your PATH. Run:
   
   echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc && source ~/.zshrc
 ⚠ Native installation exists but ~/.local/bin is not in your PATH

Reproduction Steps

1. Configure ~/.local/bin in PATH via .zshrc, .zshenv, and .zlogin
2. Restart terminal and verify PATH with echo $PATH | tr ':' '\n' | head -1
3. Confirm which claude returns /Users/wonseok/.local/bin/claude
4. Start Claude Code CLI with claude
5. Run /status command
6. Observe the false positive warning

Additional Context

• The warning persists even after:
• Restarting the terminal
• Rebooting the system
• Restarting Claude Code CLI
• Adding the PATH export to multiple shell config files
• Adding the PATH export to the end of .zshrc (as suggested by the warning)

• All Claude Code functionality works correctly (commands are found, native tools work)
• This appears to be a false positive in the diagnostic logic

Suggested Fix

The PATH diagnostic logic should:

1. Check the actual runtime PATH environment variable, not just parse shell config files
2. Or, if parsing config files, check .zshenv and .zlogin in addition to .zshrc
3. Or, improve the regex/parsing logic to detect the PATH setting regardless of its position in the file