What
Cloud sessions that begin before your files have arrived now have a defined path: sync records that it started empty, checks out the first upload from your machine, and if that fails it turns sync off with a stated reason. New messages tell the model whether files are still coming, arrived late, or that sync stopped and work must continue on your own machine.
Details
- Disarm reasons include: the directory was not empty, the first uploaded object could not be read, the bundle failed verification, the container was recreated, or the git checkout failed.
- Adds a log point for an unread empty-start marker,
dir_sync_git_empty_start_flag_unread. - Part of the git-based cloud directory sync; no separate flag turns this path on or off.
Evidence
Directory sync could not check in before this turn began, and this working directory is EMPTY.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.