File sync now refuses large checkouts purely on byte size, not untracked file count.
What's wrong with this entry?
When a cloud session declines to offer file sync because your checkout has too much uncommitted content, the reason is now always a byte size compared against a fixed limit, replacing an earlier three-way check that could also refuse for having too many untracked files.
- The single reason reported is
untracked_too_large, and the user-facing line always cites a size.
File sync is not offered for this checkout:
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.