[Windows] AppX update probes missing old package path after repair

Summary

After updating the Windows desktop app from 26.820.7780.0 to 26.825.6671.0, the installed package is 26.825.6671.0, but startup still probes the previous AppX path. The previous package directory is absent. Windows Repair reduced the latest startup time, but did not stop the stale lookup.

Environment

• OS: Windows 11 Enterprise, build 26200, x64
• AppX package: OpenAI.Codex_26.825.6671.0_x64__2p2nqsd0c76g0
• Desktop app version: 26.825.6671.0
• Runtime version seen in the log: 0.151.0-alpha.7.2
• Distribution: Windows AppX / Microsoft Store package

Steps to reproduce

1. Update the Codex Windows desktop app from 26.820.7780.0 to 26.825.6671.0.
2. Launch the desktop app.
3. Observe bundled_executable_relocation_failed with ENOENT for the old package path.
4. Run Windows Settings > Apps > Codex > Advanced options > Repair, then launch again.

Actual result

• The current executable exists at:

  C:\Program Files\WindowsApps\OpenAI.Codex_26.825.6671.0_x64__2p2nqsd0c76g0\app\resources\codex.exe

• The old executable path does not exist, but startup still runs stat_source against it.

• Before Repair, one affected launch had a startup critical path of 128399 ms, including 124069 ms waiting for shell environment.

• After Repair, the latest launch completed its startup critical path in 4354 ms, but stale old-path warnings remained.

Redacted log excerpt

warning bundled_executable_relocation_failed
errorCode=ENOENT
operation=stat_source
sourceKind=windowsapps
sourcePath="C:\Program Files\WindowsApps\OpenAI.Codex_26.820.7780.0_x64__2p2nqsd0c76g0\app\resources\codex.exe"

Start by tracing the bundled_executable_relocation_failed warning and the stat_source operation for sourceKind=windowsapps. Reproduce the update and Repair sequence on Windows 11, then verify startup no longer probes the absent 26.820.7780.0 path while still locating the current executable.