Send opt-in mobile deadline reminders into Agenda #709

Closed
opened 2026-08-13 04:51:14 +00:00 by timmy · 0 comments
Owner

User problem

The mobile Agenda now discovers, launches, and replans every assigned deadline, but operators must remember to open Stackchain. Existing Web Push only reports unread updates, so approaching deadlines can remain unseen while the PWA is closed.

Proposed vertical slice

Add a separate, explicit deadline-reminder preference to the existing device Push subscription. At the device's configured local morning hour, send at most one privacy-safe digest per local day when assigned work is overdue or due soon. Tapping the digest opens #/my-work/agenda so the existing Agenda completes the review/start/replan flow.

Acceptance criteria

  • Deadline reminders are a distinct opt-in and reuse the existing browser Push subscription without a second permission prompt.
  • Persist an IANA timezone and local reminder hour per subscribed device.
  • A complete bounded assigned-work scan sends one private digest when deadlines need attention; incomplete scans send nothing.
  • Durable per-device/local-day checkpoints prevent duplicates across restarts and competing workers.
  • Payloads contain no repository, issue title, body, comment, or assignee content.
  • Tapping opens the addressable Agenda route.
  • Revoked/expired sessions receive nothing; endpoint failures remain isolated.
  • Mobile controls remain at least 44 CSS px and tests cover preference, dispatch deduplication/privacy, and service-worker routing.

Non-duplication evidence

All 357 historical issue titles and recent commits were searched for deadline reminders, Agenda notifications, and due-date Push; no matching behavior exists. Related #685-#708 built the reactive Agenda flow, while #549-#574 only delivers unread-update Push.

## User problem The mobile Agenda now discovers, launches, and replans every assigned deadline, but operators must remember to open Stackchain. Existing Web Push only reports unread updates, so approaching deadlines can remain unseen while the PWA is closed. ## Proposed vertical slice Add a separate, explicit deadline-reminder preference to the existing device Push subscription. At the device's configured local morning hour, send at most one privacy-safe digest per local day when assigned work is overdue or due soon. Tapping the digest opens `#/my-work/agenda` so the existing Agenda completes the review/start/replan flow. ## Acceptance criteria - Deadline reminders are a distinct opt-in and reuse the existing browser Push subscription without a second permission prompt. - Persist an IANA timezone and local reminder hour per subscribed device. - A complete bounded assigned-work scan sends one private digest when deadlines need attention; incomplete scans send nothing. - Durable per-device/local-day checkpoints prevent duplicates across restarts and competing workers. - Payloads contain no repository, issue title, body, comment, or assignee content. - Tapping opens the addressable Agenda route. - Revoked/expired sessions receive nothing; endpoint failures remain isolated. - Mobile controls remain at least 44 CSS px and tests cover preference, dispatch deduplication/privacy, and service-worker routing. ## Non-duplication evidence All 357 historical issue titles and recent commits were searched for deadline reminders, Agenda notifications, and due-date Push; no matching behavior exists. Related #685-#708 built the reactive Agenda flow, while #549-#574 only delivers unread-update Push.
timmy self-assigned this 2026-08-13 04:51:14 +00:00
timmy closed this issue 2026-08-13 05:11:30 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
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#709
No description provided.