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

Review and resume snoozed mobile deadline reminders #1104

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

Problem

The lock-screen deadline digest can now be snoozed for one hour, but Agenda does not show that reminders are paused and offers no way to reverse an accidental snooze. The device-bound snoozed_until state already exists server-side but is omitted from preferences.

User flow

After snoozing from the lock screen, reopening mobile Agenda shows the localized resume time. Review now clears only the current device snooze and takes the user into the existing urgent deadline / Protect Today flow. A failed clear remains retryable and does not claim success.

Acceptance criteria

  • Current-device deadline preferences expose an active snoozed_until; expired state is absent.
  • An authenticated device-bound endpoint clears only the current session snooze.
  • Mobile Agenda renders a touch-safe status/action without horizontal overflow.
  • Review now clears the snooze and opens the existing urgent deadline flow.
  • Failure preserves the status and retry action.
  • Behavioral API/UI/release tests cover active, expired, success, failure, and device isolation.

Non-duplication evidence

Historical titles and recent commits contain only #1102/#1103, which added lock-screen snoozing. No issue, PR, or commit adds in-app snooze visibility, cancellation, or an Agenda recovery flow.

## Problem The lock-screen deadline digest can now be snoozed for one hour, but Agenda does not show that reminders are paused and offers no way to reverse an accidental snooze. The device-bound `snoozed_until` state already exists server-side but is omitted from preferences. ## User flow After snoozing from the lock screen, reopening mobile Agenda shows the localized resume time. **Review now** clears only the current device snooze and takes the user into the existing urgent deadline / Protect Today flow. A failed clear remains retryable and does not claim success. ## Acceptance criteria - Current-device deadline preferences expose an active `snoozed_until`; expired state is absent. - An authenticated device-bound endpoint clears only the current session snooze. - Mobile Agenda renders a touch-safe status/action without horizontal overflow. - Review now clears the snooze and opens the existing urgent deadline flow. - Failure preserves the status and retry action. - Behavioral API/UI/release tests cover active, expired, success, failure, and device isolation. ## Non-duplication evidence Historical titles and recent commits contain only #1102/#1103, which added lock-screen snoozing. No issue, PR, or commit adds in-app snooze visibility, cancellation, or an Agenda recovery flow.
timmy was assigned by rockachopa 2026-08-19 00:51:00 +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#1104
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?