stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Keep Today and Later edits lossless across browser tabs #373

New Issue
Closed
opened 2026-08-09 05:23:37 +00:00 by timmy · 0 comments
timmy commented 2026-08-09 05:23:37 +00:00
Owner
Copy Link

User impact

Today and Later queues use whole-array localStorage read/modify/write. A delivery receipt in one tab can overwrite an edit queued by another tab, silently losing an operator’s plan before it reaches the server.

Scope

Store pending planning operations as independently keyed records, coordinate Today/Later drains across tabs with the existing outbox coordinator, migrate legacy array queues, and notify peer tabs when work is queued.

Acceptance tests

  • Concurrent Today enqueues in two tabs both remain durable and are delivered exactly once.
  • Removing a delivered operation cannot erase another tab’s newly queued operation.
  • The same guarantees hold for Later, with the newest same-item intent applied deterministically.
  • Only one active PATCH drain runs per account and skipped peers resume after a queue signal.
  • Existing array queues migrate without data loss; account boundaries and all existing sync behaviors remain intact.
  • Focused tests and the complete suite pass; the updated service-worker shell contains the changed assets.

Evidence / non-duplication

frontend/today-sync.js and frontend/later-sync.js currently rewrite one shared JSON array. frontend/outbox-coordinator.js supports only issue/authored signals. Historical #242 coordinated issue/authored outboxes before planning sync existed; #361/#363/#365/#367 cover snapshots, cross-device sync, retries, and same-tab draining, not atomic cross-tab planning queues. No open/closed issue title or recent commit implements this behavior.

## User impact Today and Later queues use whole-array localStorage read/modify/write. A delivery receipt in one tab can overwrite an edit queued by another tab, silently losing an operator’s plan before it reaches the server. ## Scope Store pending planning operations as independently keyed records, coordinate Today/Later drains across tabs with the existing outbox coordinator, migrate legacy array queues, and notify peer tabs when work is queued. ## Acceptance tests - Concurrent Today enqueues in two tabs both remain durable and are delivered exactly once. - Removing a delivered operation cannot erase another tab’s newly queued operation. - The same guarantees hold for Later, with the newest same-item intent applied deterministically. - Only one active PATCH drain runs per account and skipped peers resume after a queue signal. - Existing array queues migrate without data loss; account boundaries and all existing sync behaviors remain intact. - Focused tests and the complete suite pass; the updated service-worker shell contains the changed assets. ## Evidence / non-duplication `frontend/today-sync.js` and `frontend/later-sync.js` currently rewrite one shared JSON array. `frontend/outbox-coordinator.js` supports only issue/authored signals. Historical #242 coordinated issue/authored outboxes before planning sync existed; #361/#363/#365/#367 cover snapshots, cross-device sync, retries, and same-tab draining, not atomic cross-tab planning queues. No open/closed issue title or recent commit implements this behavior.
timmy self-assigned this 2026-08-09 05:23:37 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#373
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?