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

Resume interrupted Today sessions #395

New Issue
Closed
opened 2026-08-09 10:51:23 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-09 10:51:23 +00:00
Member
Copy Link

Product gap

Today sessions keep their active item only in JavaScript memory. A mobile reload, PWA eviction, or browser interruption loses the operator’s place even though the Today plan and offline item details remain durable.

User flow

Persist an account-bound checkpoint while a Today session is active. After reload, offer Resume Today and reopen the saved item (or the next surviving item). Clear the checkpoint when the session finishes or the user ends it. Never expose one account’s checkpoint to another account.

Acceptance criteria

  • Starting/navigating a Today session persists the current stable work identity for the confirmed account.
  • Reloading online or from the cached shell offers Resume Today and reopens that item.
  • Missing items reconcile to the next surviving Today item; an empty plan clears the checkpoint.
  • Finishing or explicitly ending the session clears the checkpoint.
  • A different/unconfirmed account cannot resume the checkpoint.
  • Storage failure leaves the current session usable and reports safe recovery guidance.
  • Controls are keyboard accessible, at least 44px on phones, and covered by behavioral tests.

Non-duplication evidence

All 391 historical issue/PR records and recent commits through ff0e47c were searched. Related work added in-memory session navigation (#193), review progress (#125), durable planning (#289), and offline Today details (#345), but none persists and resumes the active Today-session cursor across application restarts.

## Product gap Today sessions keep their active item only in JavaScript memory. A mobile reload, PWA eviction, or browser interruption loses the operator’s place even though the Today plan and offline item details remain durable. ## User flow Persist an account-bound checkpoint while a Today session is active. After reload, offer **Resume Today** and reopen the saved item (or the next surviving item). Clear the checkpoint when the session finishes or the user ends it. Never expose one account’s checkpoint to another account. ## Acceptance criteria - Starting/navigating a Today session persists the current stable work identity for the confirmed account. - Reloading online or from the cached shell offers Resume Today and reopens that item. - Missing items reconcile to the next surviving Today item; an empty plan clears the checkpoint. - Finishing or explicitly ending the session clears the checkpoint. - A different/unconfirmed account cannot resume the checkpoint. - Storage failure leaves the current session usable and reports safe recovery guidance. - Controls are keyboard accessible, at least 44px on phones, and covered by behavioral tests. ## Non-duplication evidence All 391 historical issue/PR records and recent commits through `ff0e47c` were searched. Related work added in-memory session navigation (#193), review progress (#125), durable planning (#289), and offline Today details (#345), but none persists and resumes the active Today-session cursor across application restarts.
timmy was assigned by rockachopa 2026-08-09 10:51:23 +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#395
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?