Cloud directory sync no longer holds a turn waiting for an announced upload

What

Directory sync copies the files on your machine, uncommitted edits included, to the cloud machine where a cloud session runs. Before this release, when your machine announced it was uploading, the cloud-side worker held the start of each turn in a retry loop while it waited. It could then tell Claude that your machine "announced newer changes but has gone quiet before they finished uploading (it may be asleep or offline)". Now:

• The wait is gone. The worker no longer takes announcedUploadQuietMs, announcedUploadNoHeartbeatQuietMs or quietWindowReadGapMs, and its heartbeat and quiet-window tracking are removed. It only records whether your machine's sync journal is absent, announcing an upload, or something else.
• The "gone quiet" and "could not upload its latest changes" notices are removed.
• If an upload is under way when a turn starts, Claude gets a new notice: "Directory sync: the user's machine began uploading its current files, uncommitted edits included; until they arrive here, this turn runs on the session's starting files." It is also told that if you mention files or edits it cannot see, it should say they have not arrived yet.
• For a session that started empty, when no sync status has arrived yet, Claude gets a one-time notice. There are separate notices for three cases: nothing synced, upload under way, and upload abandoned.

Why

Cloud turns no longer stall while a slow laptop upload finishes. The trade-off is that the first turn can run without your latest edits, and Claude is now told when that is the case instead of working as if the files were current.