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

Make actionable delivery recovery a first-class mobile queue #1012

New Issue
Closed
opened 2026-08-17 08:24:40 +00:00 by timmy · 0 comments
timmy commented 2026-08-17 08:24:40 +00:00
Owner
Copy Link

Problem

The dashboard already computes actionable delivery recovery counts and can open the Delivery center, but the mobile queue sheet and primary Work continuation omit Delivery. A phone user can therefore start lower-priority work while a failed or uncertain authored action still needs intervention.

Scope

Surface actionable Delivery in the thumb-reachable queue sheet, queue summary, and Work continuation. Reuse the existing recovery center and count; do not treat ordinary waiting/sending records as actionable. An active Today session must continue to retain priority.

Acceptance criteria

  • With no active Today session, actionable Delivery is recommended ahead of Attention and opens the existing recovery center.
  • An active Today session still continues before Delivery recovery.
  • The mobile queue sheet exposes a dedicated Delivery row and actionable count.
  • Queue badges and accessible summaries include Delivery.
  • Clearing the final actionable record returns Work to the next live queue.
  • Packaged mobile behavior is covered by behavioral tests, including no horizontal overflow and a usable touch target.
  • Focused tests and the full suite pass.
## Problem The dashboard already computes actionable delivery recovery counts and can open the Delivery center, but the mobile queue sheet and primary Work continuation omit Delivery. A phone user can therefore start lower-priority work while a failed or uncertain authored action still needs intervention. ## Scope Surface actionable Delivery in the thumb-reachable queue sheet, queue summary, and Work continuation. Reuse the existing recovery center and count; do not treat ordinary waiting/sending records as actionable. An active Today session must continue to retain priority. ## Acceptance criteria - With no active Today session, actionable Delivery is recommended ahead of Attention and opens the existing recovery center. - An active Today session still continues before Delivery recovery. - The mobile queue sheet exposes a dedicated Delivery row and actionable count. - Queue badges and accessible summaries include Delivery. - Clearing the final actionable record returns Work to the next live queue. - Packaged mobile behavior is covered by behavioral tests, including no horizontal overflow and a usable touch target. - Focused tests and the full suite pass.
timmy self-assigned this 2026-08-17 08:24:40 +00:00
timmy closed this issue 2026-08-17 08:36: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#1012
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?