The change-detection scan can be cancelled and now reports how many files it checked and how long it took.
What's wrong with this entry?
The scan that decides which files changed now consults git clean-filter blob ids, can be cancelled part-way, and reports how many files it asked about, how many settled, and how long it took.
- A file previously marked changed can be reclassified as unchanged once the filter answers.
- Two copies of a file are now also considered in agreement when their git blob id matches and etag and mode still line up, not only when their sha256 matches.
- There is a cap on how many decisions a worker will defer.
filter_settled
Strings lifted out of the shipped bundle, so the claim above can be checked against them.