Verify the output, not the report. Especially before a delete
rsync -rcni SRC/DEST/ | grep -v "^\. d" | head # anything printed is a differencemd5 -q SRC/file DEST/file
Get the free fixes for code AI gets wrong
Each one shows what the AI wrote, what it should have written, and how to check your own app
What is going on
Exit codes, summaries, and "9 files matched" are reports. The file on the drive with the right checksum is the output. Tools that summarize will summarize wrong in exactly the cases that matter, and the cases that matter are the destructive ones.
Where it bit
A background shell wrote to the archive drive, exited 0, and had written nothing, because background bash cannot write to mounted volumes on that machine. An earlier pass claimed nine exports matched by checksum; a later pass found two were not on the drive at all, and all fourteen were re-hashed before anything was deleted.
The practice
Archive, verify in directory mode with itemized output, checksum the files themselves, then delete. Never in the reverse order and never on a summary. Measure with the tool that reads the object (md5, ffprobe, a real request), not the tool that reads the log.
Get this check as a script you can run tonight

Make your coding agent prove it didn't cheat
Coding agents special-case, skip or edit tests so the check goes green. A five-sentence prompt Anthropic tested took Claude Opus 4 from cheating in 47% of runs to 5%- 3 min read
How to pick who fixes your vibe-coded app
Your app was built fast with AI and now something is wrong. Here is who can fix it, what they should do before they quote, the questions to ask and the red flags to walk away from - 3 min read
What an app check covers
An app check is an engineer reading the app your AI tools wrote, ranking what will break and writing the fix for each problem. Here is every area it covers, how the five days run and what you keep at the end
If this check came back with more than you expected, that is worth a conversation