[Bug] File read-tracking state not reset when conversation is rewound

Bug Description
Rewinding a conversation After Claude reads a file, the harness tracks it as "already read / unchanged" to suppress redundant reads. When the user rewinds the conversation to a point before that Read call, the tool result is removed from Claude's context — but the harness's read-tracking state persists. On the next attempt, Claude is told the file is unchanged and the re-read is blocked, even though Claude no longer has the file contents in context. Result: Claude must act on a file it cannot see, with no path to recover the content (only via Bash).

Environment Info

• Platform: darwin
• Terminal: Apple_Terminal
• Version: 2.1.123
• Feedback ID: e4deb6f5-6205-480c-a3d9-881a1bde72f7

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/user/.local/share/claude/versions/2.1.123 (expected in multi-process scenarios)\n    at x86 (/$bunfs/root/src/entrypoints/cli.js:2769:2177)\n    at Jw8 (/$bunfs/root/src/entrypoints/cli.js:2769:1257)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-29T12:37:19.849Z"}]