windows codex app lost php.exe

I observed a case on Windows 11 Home where an executable that is available on PATH in a normal terminal is not recognized by Codex's command execution environment.

In this case, the executable was PHP.

Observed behavior
- In a normal PowerShell session, both `where.exe php` and `php -v` run successfully
- However, when running `php -v` from Codex, it fails with an error indicating that the `php` command cannot be found
- The behavior changed depending on where `php.exe` was located

Environment
- OS: Windows 10 home 
- Target command: `php` installed winget

What I confirmed
1.
When `php.exe` was located at the following path and that location was added to PATH, `php -v` worked in normal PowerShell, but Codex could not recognize `php`.

`C:\Users\mail_\AppData\Local\Microsoft\WinGet\Packages\PHP.PHP.8.5_Microsoft.Winget.Source_xxxxxxxx\php.exe`

2.
When `php.exe` was moved to the following location and that location was added to PATH, Codex was also able to run `php -v` successfully.

`C:\Program Files\php\php.exe`

Expected behavior
- On Windows, if an executable is available on PATH, Codex should recognize it in the same way as a normal terminal
- If there are restrictions on which PATH entries or executable directories Codex can use, that should be clearly documented or surfaced in the UI

Additional notes
- I understand that Codex may need to be restarted after PATH changes
- However, even after restarting Codex, `php.exe` under `AppData\Local\Microsoft\WinGet\Packages\...` was still not recognized
- In contrast, placing it at `C:\Program Files\php\php.exe` worked correctly