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

Keep Today-to-Week rescheduling through offline reloads #1231

New Issue
Closed
opened 2026-08-21 17:53:07 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-21 17:53:07 +00:00
Member
Copy Link

Product gap

The active Today → Week Ahead flow rejects confirmed cached state and keeps its operation only in memory. A dropped connection or reload can lose the operator’s reschedule intent even though the server endpoint is atomic and idempotent. No historical issue or recent commit implements an offline durable cross-plan move.

Vertical slice

Admit one account-bound durable reschedule operation before changing the local Today/Week snapshots; restore it after reload; deliver the unchanged operation ID when connectivity returns; preserve the intent for review on revision conflict; and run the packaged mobile journey in CI.

Acceptance

  • Confirmed cached Today and Week snapshots open without a network dependency.
  • Confirming offline persists first, then shows the item moved locally once with sync pending.
  • Reload restores the pending move; retry/reconnect uses the same operation ID and clears it only after server confirmation.
  • Storage admission failure changes neither plan.
  • A 409 keeps the intent and adopts current server truth for explicit retry.
  • Packaged 320×568 and 390×844 mobile tests cover offline, reload, reconnect, and no horizontal overflow.
## Product gap The active Today → Week Ahead flow rejects confirmed cached state and keeps its operation only in memory. A dropped connection or reload can lose the operator’s reschedule intent even though the server endpoint is atomic and idempotent. No historical issue or recent commit implements an offline durable cross-plan move. ## Vertical slice Admit one account-bound durable reschedule operation before changing the local Today/Week snapshots; restore it after reload; deliver the unchanged operation ID when connectivity returns; preserve the intent for review on revision conflict; and run the packaged mobile journey in CI. ## Acceptance - Confirmed cached Today and Week snapshots open without a network dependency. - Confirming offline persists first, then shows the item moved locally once with sync pending. - Reload restores the pending move; retry/reconnect uses the same operation ID and clears it only after server confirmation. - Storage admission failure changes neither plan. - A 409 keeps the intent and adopts current server truth for explicit retry. - Packaged 320×568 and 390×844 mobile tests cover offline, reload, reconnect, and no horizontal overflow.
timmy was assigned by rockachopa 2026-08-21 17:53:07 +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#1231
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?