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

Sync the ordered Today plan across operator devices #357

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

Problem

The ordered Today queue is stored only in per-device localStorage (frontend/today-work.js), so work planned on desktop disappears on mobile even though Stackchain supports multi-device sessions and offline execution. No historical issue or recent commit implements server-backed Today synchronization; #279 introduced the local queue, #289 retained it through refresh failures, and #349 warmed its details offline.

Slice

Add a durable, revisioned operator Today plan and integrate the existing local-first queue with it. Add/remove/reorder stay instant, synchronize when online, converge across devices, and preserve the five-item limit.

Acceptance

  • Same authenticated operator sees the same ordered Today plan on two devices.
  • Add/remove/move operations are idempotent and atomically enforce five items.
  • Offline/local operations remain immediately usable and show pending status until synchronized.
  • Conflicting changes reconcile from server truth without silently losing a successful operation.
  • API is session/CSRF protected, bounded, no-store, and durable across restart.
  • Focused behavioral tests and full suite pass.
## Problem The ordered Today queue is stored only in per-device `localStorage` (`frontend/today-work.js`), so work planned on desktop disappears on mobile even though Stackchain supports multi-device sessions and offline execution. No historical issue or recent commit implements server-backed Today synchronization; #279 introduced the local queue, #289 retained it through refresh failures, and #349 warmed its details offline. ## Slice Add a durable, revisioned operator Today plan and integrate the existing local-first queue with it. Add/remove/reorder stay instant, synchronize when online, converge across devices, and preserve the five-item limit. ## Acceptance - Same authenticated operator sees the same ordered Today plan on two devices. - Add/remove/move operations are idempotent and atomically enforce five items. - Offline/local operations remain immediately usable and show pending status until synchronized. - Conflicting changes reconcile from server truth without silently losing a successful operation. - API is session/CSRF protected, bounded, no-store, and durable across restart. - Focused behavioral tests and full suite pass.
timmy self-assigned this 2026-08-09 00:29:36 +00:00
timmy closed this issue 2026-08-09 00:40:47 +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#357
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?