puter/paseo
1
0
Fork 0
mirror of https://github.com/getpaseo/paseo.git synced 2026-11-06 16:34:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(app): settle submissions in either acknowledgement order

Browse Source 
Complete submission transactions when RPC and provider acknowledgement arrive in either order. Cache only transaction-owned local rows as transient data, preserve canonical ID-less prompts, and invalidate ambiguous legacy display caches instead of inventing provider identity.
This commit is contained in:
Mohamed Boudra
2026-07-27 17:49:42 +02:00
parent 292cea4bcc
commit 5334008e44
7 changed files with 107 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/timeline-sync.md
+1 -1
View File
@@ -104,7 +104,7 @@ The daemon's accepted response already waits for the correlated run start, but i
directory update reach client state separately. An accepted transaction remains active until the
directory observes that run or canonical ingestion acknowledges the prompt, bridging those ordered
authorities without inspecting timeline snapshots. Either signal clears only an RPC-accepted
transaction; it cannot settle a fresh send.
transaction, regardless of which arrived first; it cannot settle a fresh send.
Overlapping sends settle independently rather than collapsing to one newest pending message.
Canonical submitted user rows carry the provider's `messageId` and Paseo's optional