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

Review kept-unread outcomes after mobile Updates triage #765

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

Evidence

Mobile Updates currently routes both Keep unread and Mark read through the same completion path (frontend/update-triage-session.js) and unconditionally announces Updates cleared (frontend/dashboard.js), even when retained unread items remain. No open issue, historical issue title, open PR, release title, or recent commit covers truthful per-session outcome review.

User flow

Record each bounded triage decision. At completion, show a mobile outcome review with reviewed/marked-read/kept-unread counts. Offer a one-tap bounded pass over only retained items that remain unread; only say Updates cleared when none remain. Persist outcomes account-bound across interruption.

Acceptance

  • A keep/read/keep pass reports 3 reviewed, 1 marked read, 2 kept unread.
  • Review kept unread opens only retained IDs that remain in the unread snapshot.
  • All-resolved sessions truthfully announce Updates cleared.
  • Outcome state resumes only for the authenticated account.
  • Mobile controls are full-width/safe-area aware, at least 44px, focusable, and do not horizontally overflow at 320–390px.
  • Focused and full suites pass.
## Evidence Mobile Updates currently routes both `Keep unread` and `Mark read` through the same completion path (`frontend/update-triage-session.js`) and unconditionally announces `Updates cleared` (`frontend/dashboard.js`), even when retained unread items remain. No open issue, historical issue title, open PR, release title, or recent commit covers truthful per-session outcome review. ## User flow Record each bounded triage decision. At completion, show a mobile outcome review with reviewed/marked-read/kept-unread counts. Offer a one-tap bounded pass over only retained items that remain unread; only say `Updates cleared` when none remain. Persist outcomes account-bound across interruption. ## Acceptance - A keep/read/keep pass reports 3 reviewed, 1 marked read, 2 kept unread. - Review kept unread opens only retained IDs that remain in the unread snapshot. - All-resolved sessions truthfully announce Updates cleared. - Outcome state resumes only for the authenticated account. - Mobile controls are full-width/safe-area aware, at least 44px, focusable, and do not horizontally overflow at 320–390px. - Focused and full suites pass.
timmy self-assigned this 2026-08-13 19:18:21 +00:00
timmy closed this issue 2026-08-13 19:23:53 +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#765
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?