Photoshop Cloud Documents and Creative Cloud sync: duplicate writes on retried saves

Photoshop's Cloud Documents feature saves files directly to Creative Cloud storage, where Adobe's sync service handles auto-save and version history. When a save request fails partway through, for example after a dropped connection or a timeout, the save engine may retry the write. What happens at the boundary between Photoshop's save engine and the Creative Cloud sync service in that scenario is not publicly documented.

The unresolved point is whether retried writes are idempotent. If the sync service keys each retry to the original save transaction, a duplicate write can be discarded and only one version entry recorded. If retries are treated as independent writes, an interrupted save could leave duplicate versions or an intermediate document state. This question is scoped to cloud documents in recent Photoshop releases; local PSD saves do not cross this boundary.

• Does the Photoshop to Creative Cloud save path use an idempotency or transaction identifier so that a retried write after a network failure cannot create a second version entry?
• If a write is partially persisted before the connection drops, does Photoshop surface a conflict or recovery state on the next save attempt, or complete the transaction silently?