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

Pause Today while handling Attention #595

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

Product problem

Opening mobile Attention while a Today item is actively timed leaves that timer running, so urgent review/update work is incorrectly charged to the checkpointed Today item.

Vertical slice

  • Pause a running Today timer at the Attention handoff without changing the checkpoint or queue.
  • Show a persistent mobile interruption notice with a thumb-safe Return to Today action.
  • Return to the exact Today checkpoint and resume only when Attention auto-paused it; preserve a pre-existing manual pause.
  • Persist the account-scoped interruption across reloads and make repeated Attention taps idempotent.

Acceptance tests

  1. Time spent in Attention adds zero elapsed time to a running Today item.
  2. Return restores the exact checkpoint and resumes once only after an automatic pause.
  3. A manually paused timer remains paused after return.
  4. Reload and duplicate Attention entry preserve one account-bound interruption.
  5. Mobile notice/action has no phone-width overflow and a minimum 44px target.
  6. Existing Today, Attention, offline-shell, and full test suites remain green.

Non-duplication evidence

All 300 historical issue titles and recent commits through 9f3855d were checked. #593 made Attention independently reachable alongside Today but did not coordinate timer ownership or a return flow; #577 added manual timer controls and #591 handles app-background interruptions. No issue or commit implements this handoff.

## Product problem Opening mobile Attention while a Today item is actively timed leaves that timer running, so urgent review/update work is incorrectly charged to the checkpointed Today item. ## Vertical slice - Pause a running Today timer at the Attention handoff without changing the checkpoint or queue. - Show a persistent mobile interruption notice with a thumb-safe **Return to Today** action. - Return to the exact Today checkpoint and resume only when Attention auto-paused it; preserve a pre-existing manual pause. - Persist the account-scoped interruption across reloads and make repeated Attention taps idempotent. ## Acceptance tests 1. Time spent in Attention adds zero elapsed time to a running Today item. 2. Return restores the exact checkpoint and resumes once only after an automatic pause. 3. A manually paused timer remains paused after return. 4. Reload and duplicate Attention entry preserve one account-bound interruption. 5. Mobile notice/action has no phone-width overflow and a minimum 44px target. 6. Existing Today, Attention, offline-shell, and full test suites remain green. ## Non-duplication evidence All 300 historical issue titles and recent commits through `9f3855d` were checked. #593 made Attention independently reachable alongside Today but did not coordinate timer ownership or a return flow; #577 added manual timer controls and #591 handles app-background interruptions. No issue or commit implements this handoff.
timmy self-assigned this 2026-08-11 22:19:46 +00:00
timmy closed this issue 2026-08-11 22:32:21 +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#595
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?