Codex Review pane shows phantom Arabic filenames after failed tool calls

What happened

During a long-running Codex desktop task with a large working diff, the Last Turn Review pane displayed two phantom zero-line files named لعاب. (+0 -0). They appeared immediately after malformed/failed tool invocations.

The files did not exist in Git or on disk. I verified with:

• git status --short -z
• git ls-files -co --exclude-standard
• a filesystem scan for non-ASCII paths

All checks returned no non-ASCII filenames. The Review pane nevertheless rendered the two Arabic-looking entries.

Expected behavior

Failed tool-call payloads must never be interpreted as file paths or diff entries. Review entries should be derived only from the repository diff, and refreshing should not retain phantom zero-line files.

Reproduction

1. Run a long Codex desktop task that produces a large diff.
2. Trigger a malformed tool invocation that fails before execution.
3. Open Review → Last Turn.
4. Observe phantom +0 -0 entries not present in Git or the filesystem.

Environment

• Codex desktop on macOS
• Observed 2026-09-13
• Repository worktree with a large mixed staged/unstaged diff

A screenshot is available in the originating Codex task, but is not attached here because it includes workspace source code.

Start at the desktop Review → Last Turn pane and trace how failed tool invocations become review entries. Reproduce the malformed invocation with a large mixed staged/unstaged diff, then compare displayed entries with git status --short -z, git ls-files -co --exclude-standard, and the filesystem. Done means failed payloads produce no phantom paths and refreshing does not retain zero-line entries.