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

Review unseen Following changes during Prepare Today #1301

New Issue
Closed
opened 2026-08-23 09:54:12 +00:00 by timmy · 0 comments
timmy commented 2026-08-23 09:54:12 +00:00
Owner
Copy Link

Product gap

Following now supports changed-first sequential review, but it remains detached from the primary mobile Prepare Today journey. Operators can start Today while watched changes are still unseen unless they independently discover and open Following.

Vertical slice

  • Refresh Following only when the operator opens Prepare Today (no background request on dashboard load).
  • Add unseen watched revisions after Filed in the Prepare Today briefing.
  • Launch the existing sequential Following review directly from the Prepare Today primary action.
  • On the final reviewed revision, return to Prepare Today and offer Continue Today or Find Work.
  • Preserve truthful retry state when Following refresh fails; never report the phase clear from a failed request.

Acceptance

  1. Opening the dashboard alone does not request Following; opening Prepare Today refreshes it once.
  2. The briefing counts unseen Following changes after Filed and launches review directly.
  3. Completing all captured unseen revisions completes the Following phase and hands back to Prepare Today.
  4. Failed refresh remains retryable and does not silently clear Following.
  5. Focused behavior tests, full suite, packaged bundle/service worker tests, and 320x568 rendered mobile test pass.

Evidence / non-duplication

Current origin/main is 875ec45. Historical issue scan found Following issues #1293/#1297/#1299 and Prepare Today issues #897/#899/#901/#1010/#1024, but no issue integrating the two flows. Recent commits add Following queue, changed-first ordering, and sequential review only. frontend/mobile-start-day.js review order ends at Filed while frontend/following.js already exposes sequential review behavior.

## Product gap Following now supports changed-first sequential review, but it remains detached from the primary mobile Prepare Today journey. Operators can start Today while watched changes are still unseen unless they independently discover and open Following. ## Vertical slice - Refresh Following only when the operator opens Prepare Today (no background request on dashboard load). - Add unseen watched revisions after Filed in the Prepare Today briefing. - Launch the existing sequential Following review directly from the Prepare Today primary action. - On the final reviewed revision, return to Prepare Today and offer Continue Today or Find Work. - Preserve truthful retry state when Following refresh fails; never report the phase clear from a failed request. ## Acceptance 1. Opening the dashboard alone does not request Following; opening Prepare Today refreshes it once. 2. The briefing counts unseen Following changes after Filed and launches review directly. 3. Completing all captured unseen revisions completes the Following phase and hands back to Prepare Today. 4. Failed refresh remains retryable and does not silently clear Following. 5. Focused behavior tests, full suite, packaged bundle/service worker tests, and 320x568 rendered mobile test pass. ## Evidence / non-duplication Current `origin/main` is `875ec45`. Historical issue scan found Following issues #1293/#1297/#1299 and Prepare Today issues #897/#899/#901/#1010/#1024, but no issue integrating the two flows. Recent commits add Following queue, changed-first ordering, and sequential review only. `frontend/mobile-start-day.js` review order ends at Filed while `frontend/following.js` already exposes sequential review behavior.
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
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#1301
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?