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

Undo accidental mobile update acknowledgements #649

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

Problem

Mobile update triage removes acknowledged conversations immediately, with no way to reverse an accidental tap. This affects Mark read & next, reaction acknowledgement, and bulk mark-read flows.

Slice

Add a bounded mark-unread API and a mobile-safe Undo action that restores the exact successfully acknowledged notification without repeating reactions or replies. Failed restoration must remain truthful and retryable.

Acceptance

  • Mark-unread validates a positive thread ID, calls Gitea to-status=unread, is bounded, and returns Cache-Control: no-store.
  • Foreground read/acknowledge exposes an accessible Undo action and restores the item/count on success.
  • Undo is single-flight and a failed restore remains retryable.
  • Mobile surface stays above the bottom dock and safe-area inset.
  • Focused and full suites pass.

Audit proof: all historical issue titles/bodies and recent commits were searched for undo/mark-unread behavior; related #135, #151, #351, #503, #545, and #561 only implement one-way acknowledgement.

## Problem Mobile update triage removes acknowledged conversations immediately, with no way to reverse an accidental tap. This affects Mark read & next, reaction acknowledgement, and bulk mark-read flows. ## Slice Add a bounded mark-unread API and a mobile-safe Undo action that restores the exact successfully acknowledged notification without repeating reactions or replies. Failed restoration must remain truthful and retryable. ## Acceptance - Mark-unread validates a positive thread ID, calls Gitea `to-status=unread`, is bounded, and returns `Cache-Control: no-store`. - Foreground read/acknowledge exposes an accessible Undo action and restores the item/count on success. - Undo is single-flight and a failed restore remains retryable. - Mobile surface stays above the bottom dock and safe-area inset. - Focused and full suites pass. Audit proof: all historical issue titles/bodies and recent commits were searched for undo/mark-unread behavior; related #135, #151, #351, #503, #545, and #561 only implement one-way acknowledgement.
timmy self-assigned this 2026-08-12 12:19:50 +00:00
timmy closed this issue 2026-08-12 12:37:13 +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#649
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?