Problem
The SequentialQueue subsystem — the offline-first WRITE queue that serialises every mutating API call — lacked a dedicated reference document. Engineers had no single observational guide covering the coordinator, persisted store, throttling, anti-flicker buffers, middleware boundary, and known sharp edges.
Solution
Added contributingGuides/SEQUENTIAL_QUEUE.md, mirroring the style of NETWORK_STATE_DETECTION.md. The doc explains how SequentialQueue works today (state machine, PersistedRequests in-memory-authoritative pattern, RequestThrottle backoff, QueuedOnyxUpdates, offline/pause/multi-tab behaviour, conflict resolution, and test coverage) and includes an Open Questions appendix for intent-ambiguous items needing maintainer confirmation.
PR
#93279
Issue Owner
Current Issue Owner: @adhorodyski
Problem
The SequentialQueue subsystem — the offline-first WRITE queue that serialises every mutating API call — lacked a dedicated reference document. Engineers had no single observational guide covering the coordinator, persisted store, throttling, anti-flicker buffers, middleware boundary, and known sharp edges.
Solution
Added
contributingGuides/SEQUENTIAL_QUEUE.md, mirroring the style ofNETWORK_STATE_DETECTION.md. The doc explains how SequentialQueue works today (state machine, PersistedRequests in-memory-authoritative pattern, RequestThrottle backoff, QueuedOnyxUpdates, offline/pause/multi-tab behaviour, conflict resolution, and test coverage) and includes an Open Questions appendix for intent-ambiguous items needing maintainer confirmation.PR
#93279
Issue Owner
Current Issue Owner: @adhorodyski