Bug: apply_patch fails with "fs sandbox helper did not stop after its response" on Windows

When using Codex local, the apply_patch component fails to update existing files after executing one or two successful patches. The issue originates entirely within Codex's internal protected editor/sandbox mechanism, rather than the project environment, version control, or OS permissions.

Environment Data
• Codex Version: 26.825.32147
• Operating System: Windows

Observed Behavior & Key Clues
• File Reading works: Codex can read all project files without any issues.
• Command Execution works: Running compilations and shell commands works fine.
• The Failure: After applying 1 or 2 patches successfully, the internal apply_patch component becomes unable to read/lock an existing file for updating, triggering the following error:

Codex local: apply_patch cannot update existing files.

Error: fs sandbox helper did not stop after its response.

What has been ruled out (Not the cause):
• It is not a project issue or source code problem.
• It is not a Git lock
• It is not a generic Windows file permission (ACL) issue, as initial patches go through and reading always works.
• Creating a new Codex chat or restarting Windows does not fix the issue.

Reproduce on Windows by applying one or two successful patches, then updating an existing file and capturing the sandbox helper failure. Trace the internal protected editor/sandbox lifecycle around the helper response; done means repeated apply_patch operations can update existing files without the helper-stop error.