Unclear The finding doesn't say what heldTree represents conceptually or what user-visible effect this has on sync behavior.
What
The internal function that builds a git snapshot (covering checkout, head, basis, and parent commits) for cloud and remote sync now accepts a new heldTree option, which is validated as a git object id. It uses this to work out which file paths are "lacking" relative to both the basis and the held tree, adding an extra asynchronous check before deciding what stays staged.
Why
This refines how the sync process figures out which files are missing or need attention when building a snapshot, by comparing against an additional reference point (the held tree) rather than just the basis.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding doesn't say what `heldTree` represents conceptually or what user-visible effect this has on sync behavior.