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

Keep Today lock-screen action capabilities out of navigation URLs #1172

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

Problem

Cold-start lock-screen actions currently put today_timer_action and a one-shot today_action_token in the initial dashboard navigation URL. History cleanup occurs only after the HTTP request, so the capability can enter proxy/access logs.

User flow

Preserve one-tap Pause, Resume, and Finish when the PWA is closed, but open a clean #/my-work/today route. Transfer a bounded one-shot command privately through the service worker, scoped to the opened client, then retain the existing active-identity token validation before mutation. Fail closed on expiry, replay, wrong client, purge, or persistence failure.

Acceptance criteria

  • Cold notification activation opens a URL containing neither action parameter nor token.
  • The intended client can claim the action exactly once after bootstrap.
  • Wrong-client, expired, malformed, replayed, and purged commands do nothing.
  • Existing already-open-client actions remain supported.
  • Focused service-worker/Today/private-data tests and the full suite pass.

Non-duplication evidence

All 588 historical issue titles, 580 PR titles, 8 open issues, 0 open PRs, recent commits, and releases through f56ca63 were checked. Prior #1032 introduced the tokenized URL and #903 removed sensitive share-target URL data; no issue or commit removes Today action capabilities from navigation URLs.

## Problem Cold-start lock-screen actions currently put `today_timer_action` and a one-shot `today_action_token` in the initial dashboard navigation URL. History cleanup occurs only after the HTTP request, so the capability can enter proxy/access logs. ## User flow Preserve one-tap Pause, Resume, and Finish when the PWA is closed, but open a clean `#/my-work/today` route. Transfer a bounded one-shot command privately through the service worker, scoped to the opened client, then retain the existing active-identity token validation before mutation. Fail closed on expiry, replay, wrong client, purge, or persistence failure. ## Acceptance criteria - Cold notification activation opens a URL containing neither action parameter nor token. - The intended client can claim the action exactly once after bootstrap. - Wrong-client, expired, malformed, replayed, and purged commands do nothing. - Existing already-open-client actions remain supported. - Focused service-worker/Today/private-data tests and the full suite pass. ## Non-duplication evidence All 588 historical issue titles, 580 PR titles, 8 open issues, 0 open PRs, recent commits, and releases through `f56ca63` were checked. Prior #1032 introduced the tokenized URL and #903 removed sensitive share-target URL data; no issue or commit removes Today action capabilities from navigation URLs.
timmy self-assigned this 2026-08-20 07:52:44 +00:00
timmy closed this issue 2026-08-20 08:16:46 +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#1172
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?