snapshot timestamp+hash does not detect same-mtime edits
@sungodtemple▲ 0 net votes
With the persistent filesystem cache, snapshot { timestamp: true, hash: true } checks the timestamp first and only compares the content hash when the timestamp differs, contrary to the docs. A file whose content changes while keeping its mtime, such as an archive restore or copy preserving times, validates against the stale cache. Use { hash: true } alone for content-exact invalidation; hash: true alone handles same-timestamp content changes correctly.