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

Control an active Today session from the mobile lock screen #1026

New Issue
Closed
opened 2026-08-17 14:35:33 +00:00 by timmy · 0 comments
timmy commented 2026-08-17 14:35:33 +00:00
Owner
Copy Link

User problem

When an operator backgrounds the installed mobile dashboard during an active Today session, pause/resume and return-to-work controls disappear behind the app. The timer keeps running, but correcting it requires reopening and navigating back to the active item.

Vertical slice

Add an explicit, account-scoped opt-in for a privacy-safe active-session notification. While opted in and a Today session exists, keep one tagged notification synchronized with running/paused state. Its Pause/Resume action updates an already-open dashboard without navigation; when the app is closed it opens the validated Today route carrying a one-shot timer action. Opening the notification returns to Today. End, handoff, sign-out, or disabling the preference removes it. Never put repository or issue text on the lock screen.

Acceptance tests

  • Opt-in requests notification permission only from the user gesture and reports denied/unsupported state truthfully.
  • Running and paused timer snapshots replace one privacy-safe tagged notification with the correct action.
  • Notification Pause/Resume reaches an open dashboard client, or opens only the validated Today route with a one-shot action when closed.
  • The page consumes a valid one-shot action once and removes it from history; invalid actions are ignored.
  • Ending the session or disabling the setting closes the tagged notification.
  • Focused tests and full suite pass; the release journey includes the new module in the packaged/offline shell.

Non-duplication evidence

All 515 historical issue titles and recent origin/main commits were checked on 2026-08-17. No title or commit mentions lock-screen Today controls or a Today timer notification. Existing #550 covers unread-update notifications, while recent #1022/#1024 cover cross-device session handoff and the primary mobile entry, not background controls.

## User problem When an operator backgrounds the installed mobile dashboard during an active Today session, pause/resume and return-to-work controls disappear behind the app. The timer keeps running, but correcting it requires reopening and navigating back to the active item. ## Vertical slice Add an explicit, account-scoped opt-in for a privacy-safe active-session notification. While opted in and a Today session exists, keep one tagged notification synchronized with running/paused state. Its Pause/Resume action updates an already-open dashboard without navigation; when the app is closed it opens the validated Today route carrying a one-shot timer action. Opening the notification returns to Today. End, handoff, sign-out, or disabling the preference removes it. Never put repository or issue text on the lock screen. ## Acceptance tests - Opt-in requests notification permission only from the user gesture and reports denied/unsupported state truthfully. - Running and paused timer snapshots replace one privacy-safe tagged notification with the correct action. - Notification Pause/Resume reaches an open dashboard client, or opens only the validated Today route with a one-shot action when closed. - The page consumes a valid one-shot action once and removes it from history; invalid actions are ignored. - Ending the session or disabling the setting closes the tagged notification. - Focused tests and full suite pass; the release journey includes the new module in the packaged/offline shell. ## Non-duplication evidence All 515 historical issue titles and recent origin/main commits were checked on 2026-08-17. No title or commit mentions lock-screen Today controls or a Today timer notification. Existing #550 covers unread-update notifications, while recent #1022/#1024 cover cross-device session handoff and the primary mobile entry, not background controls.
timmy self-assigned this 2026-08-17 14:35:33 +00:00
timmy closed this issue 2026-08-17 14:53:44 +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#1026
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?