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

Resume guided Prepare Today across urgent queues #899

New Issue
Closed
opened 2026-08-15 14:49:37 +00:00 by timmy · 0 comments
timmy commented 2026-08-15 14:49:37 +00:00
Owner
Copy Link

Evidence

The current Prepare Today coordinator launches only the first non-empty phase (frontend/mobile-start-day.js), while Agenda and Filed terminal paths return to their queue routes (frontend/dashboard.js) rather than continuing the start-day sequence. No active pass is persisted, so reload or PWA restart loses the workflow. Issue #897 delivered the briefing/launcher but not cross-phase continuity. The full historical issue-title and recent-commit audit found no equivalent behavior.

User impact

A mobile operator can complete Agenda → Attention → Updates → Filed as one resumable start-day pass, with live counts determining the next phase, instead of repeatedly rediscovering and reopening each queue.

Acceptance criteria

  • Starting Prepare Today persists an account/day-scoped active pass and launches the first live urgent phase.
  • Completing a phase resolves fresh counts and offers the next phase in Agenda → Attention → Updates → Filed order, skipping phases that became empty.
  • Reloading on the same account/day exposes Resume preparation; another account cannot resume it.
  • Finish for now clears only the checkpoint; completing all urgent phases continues to Today or Find Work and clears it.
  • The handoff remains keyboard accessible and usable without horizontal overflow at 320px/390px.
  • Behavioral tests cover persistence, account/day isolation, phase handoff, stale count skipping, finish, and completion.
## Evidence The current Prepare Today coordinator launches only the first non-empty phase (`frontend/mobile-start-day.js`), while Agenda and Filed terminal paths return to their queue routes (`frontend/dashboard.js`) rather than continuing the start-day sequence. No active pass is persisted, so reload or PWA restart loses the workflow. Issue #897 delivered the briefing/launcher but not cross-phase continuity. The full historical issue-title and recent-commit audit found no equivalent behavior. ## User impact A mobile operator can complete Agenda → Attention → Updates → Filed as one resumable start-day pass, with live counts determining the next phase, instead of repeatedly rediscovering and reopening each queue. ## Acceptance criteria - Starting Prepare Today persists an account/day-scoped active pass and launches the first live urgent phase. - Completing a phase resolves fresh counts and offers the next phase in Agenda → Attention → Updates → Filed order, skipping phases that became empty. - Reloading on the same account/day exposes Resume preparation; another account cannot resume it. - Finish for now clears only the checkpoint; completing all urgent phases continues to Today or Find Work and clears it. - The handoff remains keyboard accessible and usable without horizontal overflow at 320px/390px. - Behavioral tests cover persistence, account/day isolation, phase handoff, stale count skipping, finish, and completion.
timmy self-assigned this 2026-08-15 14:49:37 +00:00
timmy closed this issue 2026-08-15 15:05:18 +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#899
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?