ArchiveIndexer.SyncAsync and the ingest's in-step append (and the first
frame of an API sequence) read the sequence row and upsert the whole row
from that read in one transaction. On PostgreSQL (READ COMMITTED) a
PATCH accepted between the read and the upsert was written back over:
its settings were lost and settings_version went back, so the PC that
pushed them later pulled the old settings over its edit.
The row is now read with SequenceRepository.GetForUpdateAsync (FOR
UPDATE, as EditAsync takes it). A PATCH committed first is then moved by
the insertion like any position; one arriving later sees the new frames
version and gets 409 frames_conflict.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC