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

Launch Protect Today directly from deadline reminders #723

New Issue
Closed
opened 2026-08-13 08:52:46 +00:00 by timmy · 0 comments
timmy commented 2026-08-13 08:52:46 +00:00
Owner
Copy Link

Product gap

Deadline reminders currently open Agenda, forcing mobile users to rediscover the existing Protect Today action before they can reconcile overdue and due-today work.

Vertical slice

Add privacy-safe Protect Today and Open Agenda notification actions. The primary action deep-links into authoritative Agenda discovery and opens the existing review-before-save Protect Today planner. If discovery is incomplete, no partial plan is proposed and Agenda remains available with retry guidance.

Acceptance tests

  • Deadline payload and rendered notification expose no repository/title details.
  • Protect Today action opens #/my-work/protect-today; Open Agenda opens the existing Agenda route.
  • The deep link completes assigned-issue discovery before proposing urgent work.
  • No urgent work produces a truthful no-op without mutating Today.
  • Incomplete/offline discovery never proposes from a partial snapshot.
  • Existing explicit save/capacity/revision safeguards remain required.

Evidence / non-duplication

Current origin/main (cbe4017) routes deadline digests only to #/my-work/agenda; frontend/service-worker.js gives deadline notifications no actions. Historical work #709, #703, and #721/#722 supplied reminders, complete Agenda discovery, and the in-app Protect Today planner respectively, but no historical issue or recent commit connects the reminder directly to that planner.

## Product gap Deadline reminders currently open Agenda, forcing mobile users to rediscover the existing Protect Today action before they can reconcile overdue and due-today work. ## Vertical slice Add privacy-safe **Protect Today** and **Open Agenda** notification actions. The primary action deep-links into authoritative Agenda discovery and opens the existing review-before-save Protect Today planner. If discovery is incomplete, no partial plan is proposed and Agenda remains available with retry guidance. ## Acceptance tests - Deadline payload and rendered notification expose no repository/title details. - Protect Today action opens `#/my-work/protect-today`; Open Agenda opens the existing Agenda route. - The deep link completes assigned-issue discovery before proposing urgent work. - No urgent work produces a truthful no-op without mutating Today. - Incomplete/offline discovery never proposes from a partial snapshot. - Existing explicit save/capacity/revision safeguards remain required. ## Evidence / non-duplication Current `origin/main` (`cbe4017`) routes deadline digests only to `#/my-work/agenda`; `frontend/service-worker.js` gives deadline notifications no actions. Historical work #709, #703, and #721/#722 supplied reminders, complete Agenda discovery, and the in-app Protect Today planner respectively, but no historical issue or recent commit connects the reminder directly to that planner.
timmy self-assigned this 2026-08-13 08:52:46 +00:00
timmy closed this issue 2026-08-13 08:59:35 +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#723
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?