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

Complete unread discovery before mobile Updates triage #749

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

Problem

Mobile Updates triage snapshots only the currently loaded notification page. With more than 50 unread updates, it can start a partial session and report “Inbox cleared” while older unread updates remain.

User flow

Before opening the first update, discover every unread notification page with truthful progress. On discovery failure, keep the existing checkpoint, open no partial session, and let the operator retry. Duplicate launches share one in-flight discovery.

Acceptance tests

  • 73 unread updates are fully fetched before the detail sheet opens and progress starts at Update 1 of 73.
  • Duplicate launch taps share one discovery operation.
  • A failed page opens no partial triage session and preserves a resumable checkpoint.
  • Retry continues safely and snapshots each notification identity once.
  • Mobile controls remain at least 44px with no horizontal overflow.

Audit: no matching open issue or PR; related #747 resumes a loaded-set session, #573 completes Web Push pagination, and #219 loads complete conversations, but none completes unread discovery before interactive triage.

## Problem Mobile Updates triage snapshots only the currently loaded notification page. With more than 50 unread updates, it can start a partial session and report “Inbox cleared” while older unread updates remain. ## User flow Before opening the first update, discover every unread notification page with truthful progress. On discovery failure, keep the existing checkpoint, open no partial session, and let the operator retry. Duplicate launches share one in-flight discovery. ## Acceptance tests - 73 unread updates are fully fetched before the detail sheet opens and progress starts at Update 1 of 73. - Duplicate launch taps share one discovery operation. - A failed page opens no partial triage session and preserves a resumable checkpoint. - Retry continues safely and snapshots each notification identity once. - Mobile controls remain at least 44px with no horizontal overflow. Audit: no matching open issue or PR; related #747 resumes a loaded-set session, #573 completes Web Push pagination, and #219 loads complete conversations, but none completes unread discovery before interactive triage.
timmy self-assigned this 2026-08-13 15:21:07 +00:00
timmy closed this issue 2026-08-13 15:34:16 +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#749
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?