Hash a file again when its mtime moved back, not only forward (closes #176) #182

Merged
clawbot merged 1 commits from issue-176-rehash-on-any-mtime-change into next 2026-11-11 05:22:54 +01:00
1 Commits
Author SHA1 Message Date
sneak f9f309e94a Hash a file again when its mtime moved back, not only forward (closes #176)
check / check (push) Waiting to run
scan treated a recorded file as unchanged when its size matched and its
mtime was not newer. A file replaced by other content of the same size
with an older mtime, as cp -p, rsync -a or a restore writes it, kept the
hash of the file it replaced. Any mtime difference now counts as a
change. README.md says so, and a new test covers the older mtime.

Model: opus-5-5
2026-11-11 02:54:08 +00:00