What
When directory sync is on, a message you send to a cloud session is held until the session confirms it applied the files uploaded from your machine, polled with exponential backoff up to a cap. If that never happens you get a plain-language explanation instead of silence.
Details
- Timeout produces its own message; a partial apply names how many files could not be fetched.
- Each container-side refusal maps to a sentence, covering a bundle timeout, the uploaded state not being a descendant of what the session has, a dirty working tree, a refused checkout and a git timeout.
- Two new telemetry events record the wait and each held send.
- Only sessions with directory sync active reach this path.
Evidence
Strings lifted out of the shipped bundle, so the claim above can be checked against them.