You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(indexing): relay self-supersede on stale base + db_version provenance (#1589)
Two changes for the basic-memory-cloud #1589 collab persistence redesign:
1. Relay self-supersede: the accepted-note base-checksum precondition now
accepts a stale base when BOTH the current accepted version's last_source
and the incoming request source are collaboration_relay. A relay persist
that times out client-side after committing leaves the relay's recorded
base one version behind its own write; rejecting that wedges every
subsequent store in a 409 loop (observed live in cloud production
2026-07-23: zero persists for 10+ minutes while the user typed). The
relay's next snapshot always supersedes its own prior write - the live
Y.Doc is the merge of everything the relay ever persisted. Foreign
writers keep full guarded semantics; the deleted-entity 409 also stays.
2. db_version provenance on index results: RuntimeNoteObjectProvenance now
parses bm-db-version alongside actor/source; it threads through
IndexedFileLiveUpdatePlan, IndexFileJobResult, and
IndexFileNoteLiveUpdatePlan (withheld for superseded content, like
content_checksum) so cloud's index-completion live updates can carry the
monotonic version. Consumers then decide echo-vs-out-of-band by version
arithmetic instead of checksum guessing.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013wFpjrd126rVe6VisiYVDD
0 commit comments