[Windows] Automation resume fails on path canonicalization mismatch (`C:\...` vs `\\?\C:\...`)

What version of the Codex App are you using (From “About Codex” dialog)?

0.128.0

What subscription do you have?

Pro

What platform is your computer?

Microsoft Windows NT 10.0.19044.0 x64

What issue are you seeing?

Summary
On Windows, Codex Desktop automation fails to start with:

Could not start automation
cannot resume running thread <thread-id> with mismatched path: requested C:\Users\Home\.codex\sessions\...\rollout-....jsonl, active \\?\C:\Users\Home\.codex\sessions\...\rollout-....jsonl

These paths point to the same file, but Codex treats them as different values and refuses to resume the thread.

What steps can reproduce the bug?

Steps to reproduce

1. Start an automation attached to an existing thread.
2. Stop it.
3. Start it again.
4. The resume fails with the mismatch error.

Actual behavior

• Automation does not start.
• The same error recurs across multiple automations, not just one thread.
• Restarting Codex, signing out/in, and rebooting the machine do not reliably fix it.

What is the expected behavior?

Expected behavior

• Codex should canonicalize Windows paths before comparing or persisting rollout/session paths.
• C:\... and \\?\C:\... should be treated as the same file on Windows.

Additional information

Notes

• This looks related to issue #16994, but that report says no rollout found.
• In this case the rollout/session file exists; the failure happens because the stored path is compared literally and resume is rejected.
• This appears to be an app-level Windows path normalization bug in automation/session resume logic, not an authentication issue.