Windows Codex Desktop repeatedly creates cua_node .staging runtime directories under mojibake Chinese user path, filling disk #28258

Environment:

• OS: Windows
• Codex Desktop package: OpenAI.Codex_26.609.4994.0_x64__2p2nqsd0c76g0
• Windows user profile contains Chinese characters: C:\Users<ChineseUser>
• Codex app runs Windows-native / PowerShell agent

Issue:
Codex Desktop repeatedly creates full runtime staging directories for cua_node under a mojibake path derived from the Chinese username.

Bad path observed:
C:\Users<mojibake-ChineseUser>AppData\Local\OpenAI\Codex\runtimes\cua_node

In my case the path looked like:
C:\Users\LBX_XXB_鐩涘畯浼焅AppData\Local\OpenAI\Codex\runtimes\cua_node

Observed behavior:

• Codex repeatedly creates directories named .staging-789504f803e82e2b-*
• Each staging directory is about 272 MB
• It accumulated 70 staging directories again, about 19 GB
• Previously it accumulated hundreds of staging directories and filled the disk
• The completed runtime directory 789504f803e82e2b already exists
• Codex still attempts to create new staging directories

Expected behavior:

• Codex should use the correct Unicode user profile path:
  C:\Users<ChineseUser>\AppData\Local\OpenAI\Codex
• Runtime installation should complete once and not leave repeated .staging directories
• It should not repeatedly download/extract cua_node when the runtime already exists

Evidence:

• Final runtime dir exists: 789504f803e82e2b
• Staging count reached 70
• Runtime staging consumed about 19 GB
• Workaround applied locally: deny WriteData/AddFile and AppendData/AddSubdirectory on the cua_node parent directory to stop disk growth

Impact:
This can rapidly fill both C: or any redirected target disk on Windows machines with non-ASCII user profile paths.

Notes:
codex doctor could not be run from the WindowsApps package path due to Access is denied.