jerry/buzz
1
0
Fork 0
mirror of https://github.com/block/buzz.git synced 2026-10-29 05:21:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(desktop): share draft intent authority across composer visits

Browse Source 
Keep authored intent in the scoped draft store independently of value deletion. Supersede recovery, sent cleanup and lifecycle persistence across reentry and remount while preserving ordinary destination-bound sends and untouched optimistic recovery. Keep editability and automatic prefix restoration programmatic. Exercise the real store, React lifecycle transition matrix and retained browser editor.

Co-authored-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz>
Signed-off-by: Logan Johnson <loganj@squareup.com>
(cherry picked from commit ff140562c693147730d548582bc39a12d37ce210)
Signed-off-by: Logan Johnson <loganj@squareup.com>
(cherry picked from commit 4b99bc705ebb8a6920c114620360433556bf88f9)
Signed-off-by: Logan Johnson <loganj@squareup.com>
This commit is contained in:
Logan Johnson
2026-08-31 16:05:43 -04:00
parent 8e49ba0b11
commit a89eae5dce
12 changed files with 955 additions and 402 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
docs/remote-mention-routing.md
View File

@@ -54,11 +54,12 @@ Invitation intent belongs to one visit of the effective persistence key and
channel, not just the mounted composer or destination channel. Same-channel
thread changes and A → B → A invalidate the original visit. The visible owner gates
optimistic clear, editor recovery and pending state. Storage recovery instead
consults the captured source visit's authored revision even after that visit
exits; losing visible ownership never revokes an authored deletion. The lifecycle
retains a per-visit revision record through its captured accessor, so B's edits
cannot authorize or suppress A's recovery. Preflight recovery and sent-draft
cleanup use that same source authority. Invalidation makes recovery durable
consults shared authored intent for the source draft key, even after exit,
re-entry or unmount. The draft store retains a revision and authoritative-empty
marker independently of the stored value. Later same-key authored text/deletion
or a new send revokes older recovery and sent-draft cleanup; editing B does not
change A's authority. A visit-specific accessor reads that shared authority while
preserving the separate visible-owner identity. Invalidation makes recovery durable
synchronously, before a later visit can load or edit the source draft; late async
completion cannot revive that recovery or release a newer attempt's latch.
@@ -71,8 +72,12 @@ refs, writing them into the editor only while the original visit/revision remain
current. Normal persona creation/reuse and ordinary destination-bound background
sends retain their existing behavior; accepted membership is never rolled back.
Recovery still compares stored content/media/refs rather than implementing a
versioned draft database. Final membership/policy reads are not atomic with send,
Recovery additionally compares stored content/media/exact refs before replacing
an existing record. Programmatic persistence does not itself change semantic
intent. Explicit inbox deletion and replacement do; scope reset invalidates old
handles. This is same-window authority for live continuations, not cross-window
synchronization or a versioned storage protocol. Reload destroys continuations;
authored deletion has already removed the durable value. Final membership/policy reads are not atomic with send,
and cancellation cannot retract an already dispatched publication. Standalone
forum transport-failure binding recovery and native compatibility remain separate
review/follow-up boundaries.