Rows `decryptChromiumValue` could not read were dropped without a trace, so an
import that recovered a fraction of the database still reported a clean
success. They now reach the user as part of the skipped total.

This matters most on Linux, where records written under a keyring-derived
`v11` key are unreadable unless that secret is reachable — see the note in
`ChromiumKeys`.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>