Under the hood
Useful2 Signal3
Memory sync now warns when fetched content does not match the digest recorded for it.
What's wrong with this entry?
Anonymous. No account, no email.
What
The sync result now carries counts of digest mismatches and restored empty files, and a warning is logged when fetched bodies did not match the digest recorded for them. Such content is filed under the digest actually computed rather than the one claimed.
Evidence
read body/bodies did not match their declared sha256; recorded under the computed sha
Strings lifted out of the shipped bundle, so the claim above can be checked against them.