PandaStudio

Concurrent editor saves: verbs that analyse for a while (remove-silences, remove-fillers, delete-words, insert-pause, space-out, set-audio-ducking, caption emphasis, place-on-beats, track-focus-face / track-region, convert-to-keyframes, auto-sync-podcast, set-clip-webcam, layouts, and the async jobs: transcription, voiceover, audio cleanup, rendered graphics, auto-reframe, downloads) measure on the project as read and apply their result to the project as it is on disk when they write, keeping edits that landed meanwhile. They do NOT fail because the editor saved. If what they measured changed (the clip was swapped, the words retimed) they measure again; if it keeps changing they fail with code: "project_changed_during_analysis" (409) and change nothing: wait for the other edit, then run the verb once more. Saves that change nothing no longer bump revision. project.batch retries a conflicting command up to three times. An explicit expectedRevision is checked when the verb starts (code: "revision_conflict", status: 409, expected, actual); re-read before retrying, never write back an old snapshot.