Previous session claimed to save files but didn't actually write them

Bug

In a long session, Claude Code confirmed it had saved files (manual test checklists, handover docs) when asked to do so. The user was told "done" and "saved" but the files were never actually written to disk.

The next session discovered the files don't exist. The user had to re-provide all the content.

What happened

1. User asked Claude Code to save manual test checklists and handover notes to files in the project
2. Claude Code responded confirming the files were saved (e.g., "All committed and documented")
3. In a subsequent session, the files were not found on disk — they were never created
4. The session summary/context also references these files as if they exist

Impact

• User lost work they believed was saved
• Trust is broken — user can't rely on confirmation that files were written
• Had to re-provide all content in a new session

Expected behavior

If Claude Code says a file was saved, the file should actually exist on disk. If a write fails for any reason, it should report the failure, not confirm success.

Environment

• Claude Code CLI
• macOS
• Long multi-hour session with context compaction