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

Sync recent work across signed-in mobile devices #1475

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

Evidence

frontend/mobile-recent-work.js stores the five-item continuation list only in account-keyed localStorage, while adjacent queue priority already synchronizes encrypted account-scoped state. Operators cannot resume an issue, pull, review, or update opened on another signed-in device. Audit of all 741 historical issue titles and recent commits found only #1471 (same-device local Recent work), not cross-device synchronization.

Acceptance

  • Opening supported work records locally remains immediate and bounded to five canonical routes.
  • Signed-in devices merge and deduplicate Recent work through an authenticated, CSRF-protected, no-store API.
  • Durable item content is encrypted at rest and account scoped.
  • Offline/transient failure leaves a visible pending state and retries without blocking route opening or creating duplicates.
  • Account changes cannot apply a stale in-flight response to the new account.
  • Store, API, browser behavior, packaged mobile flow, focused tests, and full suite pass.
## Evidence `frontend/mobile-recent-work.js` stores the five-item continuation list only in account-keyed localStorage, while adjacent queue priority already synchronizes encrypted account-scoped state. Operators cannot resume an issue, pull, review, or update opened on another signed-in device. Audit of all 741 historical issue titles and recent commits found only #1471 (same-device local Recent work), not cross-device synchronization. ## Acceptance - Opening supported work records locally remains immediate and bounded to five canonical routes. - Signed-in devices merge and deduplicate Recent work through an authenticated, CSRF-protected, no-store API. - Durable item content is encrypted at rest and account scoped. - Offline/transient failure leaves a visible pending state and retries without blocking route opening or creating duplicates. - Account changes cannot apply a stale in-flight response to the new account. - Store, API, browser behavior, packaged mobile flow, focused tests, and full suite pass.
timmy self-assigned this 2026-08-27 17:23:05 +00:00
timmy closed this issue 2026-08-27 17:45:03 +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#1475
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?