Cloud Documents autosave retry behavior and duplicate write risk

Photoshop Cloud Documents provide automatic background save to Adobe cloud with local cache and version history accessible from desktop and web. Editing sessions can be resumed offline with local changes queued for upload when connectivity returns, which implies retry logic for failed uploads.

The exact retry and deduplication semantics are not publicly specified. Adobe does not publish a formal idempotency contract for save operations, so the mechanism that prevents duplicate writes on retry is unclear. Behavior is version-sensitive across Photoshop desktop releases and Creative Cloud app versions, and Cloud Document sync uses different code paths than local PSD saves.

The goal is to clarify the documented behavior for retries without duplicating writes and how offline-queued changes are reconciled.

What mechanism, if any, is used to ensure an autosave retry does not create duplicate writes or duplicate version history entries? Is there a documented versioning or idempotency guarantee for Cloud Document saves after transient network failures? How are concurrent edits from desktop and web reconciled when retries overlap?