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

Make Prepare Today the primary truthful mobile work entry #1024

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

Problem

On a fresh mobile launch, the primary Work dock action opens the first urgency queue directly while the guided Prepare Today flow is hidden under Queues. Its briefing sums overlapping Agenda, Attention, Updates, and Filed memberships, overstating the amount of unique work.

Product slice

  • Keep Continue Today highest priority for an active Today session.
  • With no active session and preparation work remaining, label the primary dock action Prepare/Resume preparation and open the Prepare Today briefing.
  • Count each work identity once, assigning it to the highest-priority phase: Delivery, Agenda, Attention, Updates, Filed.
  • Preserve existing checkpoint and phase handoff behavior.

Acceptance

  • The primary Work action opens the briefing instead of an issue when preparation remains.
  • An active Today session still continues directly.
  • Overlapping queue memberships contribute once to the briefing total and only to their highest-priority phase.
  • A saved checkpoint exposes Resume preparation.
  • Focused behavioral tests, full suite, and packaged mobile viewport validation pass.

Evidence / non-duplication

Current mobile-work-entry.js prioritizes queueLauncher.recommend() before Today preparation, while mobile-start-day.js adds independent queue counts. Historical #897/#899/#901 created and resumed the briefing; #755 added direct priority routing. No open/closed title or recent commit makes preparation primary while de-duplicating phase identities.

## Problem On a fresh mobile launch, the primary Work dock action opens the first urgency queue directly while the guided Prepare Today flow is hidden under Queues. Its briefing sums overlapping Agenda, Attention, Updates, and Filed memberships, overstating the amount of unique work. ## Product slice - Keep Continue Today highest priority for an active Today session. - With no active session and preparation work remaining, label the primary dock action Prepare/Resume preparation and open the Prepare Today briefing. - Count each work identity once, assigning it to the highest-priority phase: Delivery, Agenda, Attention, Updates, Filed. - Preserve existing checkpoint and phase handoff behavior. ## Acceptance - The primary Work action opens the briefing instead of an issue when preparation remains. - An active Today session still continues directly. - Overlapping queue memberships contribute once to the briefing total and only to their highest-priority phase. - A saved checkpoint exposes Resume preparation. - Focused behavioral tests, full suite, and packaged mobile viewport validation pass. ## Evidence / non-duplication Current `mobile-work-entry.js` prioritizes `queueLauncher.recommend()` before Today preparation, while `mobile-start-day.js` adds independent queue counts. Historical #897/#899/#901 created and resumed the briefing; #755 added direct priority routing. No open/closed title or recent commit makes preparation primary while de-duplicating phase identities.
timmy self-assigned this 2026-08-17 13:21:55 +00:00
timmy closed this issue 2026-08-17 13:41:25 +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#1024
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?