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

Pause active Today timing while reviewing mobile Insights #1082

New Issue
Closed
opened 2026-08-18 14:19:27 +00:00 by timmy · 0 comments
timmy commented 2026-08-18 14:19:27 +00:00
Owner
Copy Link

Problem

Opening the mobile Insights route hides the active Today HUD while leaving its timer running. Time spent reviewing metrics is silently charged to the active task, corrupting actual-time and capacity signals.

Evidence: frontend/mobile-insights.js changes the route and hides Today surfaces without using the durable detour lifecycle already used by quick capture, Search, Find Work, and Queues. No open/closed issue or recent commit covers Insights timer integrity; #994 only introduced Back-safe Insights navigation.

Vertical slice

Pause a running Today item while mobile Insights is open, explain the pause in the rendered view, and let the user return directly to the same Today item. Closing through Close, browser Back, or Escape must restore timing exactly once. Manual pauses and replaced/completed items must never be resumed.

Acceptance tests

  • A running item enters a durable insights detour and elapsed time does not grow while Insights is open.
  • Close, Back, Escape, and Return to Today resume the same item exactly once.
  • Reload on #/insights restores the paused detour.
  • A manually paused, replaced, or completed item is not resurrected.
  • Mobile Insights renders a visible paused-task status and a minimum 44px Return to Today target.
  • Focused and full test suites pass; packaged mobile behavior is exercised.
## Problem Opening the mobile Insights route hides the active Today HUD while leaving its timer running. Time spent reviewing metrics is silently charged to the active task, corrupting actual-time and capacity signals. Evidence: `frontend/mobile-insights.js` changes the route and hides Today surfaces without using the durable detour lifecycle already used by quick capture, Search, Find Work, and Queues. No open/closed issue or recent commit covers Insights timer integrity; #994 only introduced Back-safe Insights navigation. ## Vertical slice Pause a running Today item while mobile Insights is open, explain the pause in the rendered view, and let the user return directly to the same Today item. Closing through Close, browser Back, or Escape must restore timing exactly once. Manual pauses and replaced/completed items must never be resumed. ## Acceptance tests - A running item enters a durable `insights` detour and elapsed time does not grow while Insights is open. - Close, Back, Escape, and Return to Today resume the same item exactly once. - Reload on `#/insights` restores the paused detour. - A manually paused, replaced, or completed item is not resurrected. - Mobile Insights renders a visible paused-task status and a minimum 44px Return to Today target. - Focused and full test suites pass; packaged mobile behavior is exercised.
timmy self-assigned this 2026-08-18 14:19:27 +00:00
timmy closed this issue 2026-08-18 14:54:50 +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#1082
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?