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

Reply to updates and continue Today in one action #451

New Issue
Closed
opened 2026-08-10 04:09:43 +00:00 by timmy · 0 comments
timmy commented 2026-08-10 04:09:43 +00:00
Owner
Copy Link

User problem

Unread-update conversations make a mobile operator send a reply and then separately find and tap Mark read & next to continue an active Today session. Issue and pull conversations already offer a one-action comment-and-continue flow, but updates do not.

Evidence

  • frontend/index.html exposes separate Send reply and Mark read & next controls.
  • frontend/dashboard.js implements those as independent handlers.
  • frontend/comment-next.js already provides single-flight, offline-safe submit-and-advance behavior for issue/pull comments.
  • No historical issue/PR title or recent commit implements reply-and-next for updates.

Acceptance criteria

  • The current checkpointed Today update exposes a thumb-safe Reply & next action; non-current updates do not.
  • Online success posts once, clears the reply draft, completes only the current Today item, and advances through the existing readiness gate.
  • Retryable outages advance only after durable update-reply outbox admission.
  • Blank input, permanent failure, or failed durable admission preserves the draft and Today position.
  • The notification remains unread; Mark read & next remains explicit acknowledgement.
  • Rapid double taps cannot reply or advance twice.
  • Behavioral tests cover wiring, payload identity, failure retention, offline admission, and single-flight execution.
## User problem Unread-update conversations make a mobile operator send a reply and then separately find and tap **Mark read & next** to continue an active Today session. Issue and pull conversations already offer a one-action comment-and-continue flow, but updates do not. ## Evidence - `frontend/index.html` exposes separate **Send reply** and **Mark read & next** controls. - `frontend/dashboard.js` implements those as independent handlers. - `frontend/comment-next.js` already provides single-flight, offline-safe submit-and-advance behavior for issue/pull comments. - No historical issue/PR title or recent commit implements reply-and-next for updates. ## Acceptance criteria - The current checkpointed Today update exposes a thumb-safe **Reply & next** action; non-current updates do not. - Online success posts once, clears the reply draft, completes only the current Today item, and advances through the existing readiness gate. - Retryable outages advance only after durable `update-reply` outbox admission. - Blank input, permanent failure, or failed durable admission preserves the draft and Today position. - The notification remains unread; **Mark read & next** remains explicit acknowledgement. - Rapid double taps cannot reply or advance twice. - Behavioral tests cover wiring, payload identity, failure retention, offline admission, and single-flight execution.
timmy self-assigned this 2026-08-10 04:09:43 +00:00
timmy closed this issue 2026-08-10 04:17:32 +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#451
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?