Directory sync can upload straight to a file store when the server offers that route.
What's wrong with this entry?
Syncing a directory to a cloud session can now upload files directly to a file store over a begin/commit route with sha256 and etag checks, instead of the older path. There is no client flag: it is used whenever the server offers the route, and a response of unsupported is what turns it off.
- Includes stall detection and a single automatic restart when an upload expires or is cut.
- A probe latches once it sees the commit route is missing, so it stops retrying it for the session.
- Per-attempt telemetry is reported as
tengu_dir_sync_direct_upload, and failures surface as named errors.
tengu_dir_sync_direct_upload
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.