File sync now accounts for replacements, kept copies and already-judged deletions when resolving conflicts.
What's wrong with this entry?
Per-file sync results and the running totals gained fields for files replaced without keeping a copy, copies kept, and deletions already judged, and conflict resolution now passes the local file hash into its fallback path. It is how conflicting remote replacements get accounted for.
replacedWithoutCopy
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.