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

Add an actionable offline delivery center #481

New Issue
Closed
opened 2026-08-10 11:49:45 +00:00 by timmy · 0 comments
timmy commented 2026-08-10 11:49:45 +00:00
Owner
Copy Link

Problem

Offline authored work is durable, but its delivery state is hidden inside the Drafts list. Operators cannot tell waiting work from active sends, see a recent transient failure, or safely retry all eligible queued work after reconnecting.

Evidence

  • frontend/issue-outbox.js and frontend/authored-outbox.js persist queued/sending/attention states.
  • frontend/drafts.js flattens delivery records into individual draft rows without an aggregate delivery status or queue-wide safe retry.
  • The current service worker reports individual completion/failure, not an actionable queue overview.
  • All 243 historical issue titles/bodies and 234 PRs were checked: no Delivery Center, sync-status, or retry-queued flow exists. Closest work (#234, #260, #297, #305, #319, #479) built complementary queue durability and individual controls.

Acceptance criteria

  • Drafts and queued deliveries are presented as distinct sections.
  • Delivery summary shows accurate Waiting, Sending, and Needs attention counts.
  • A 44px mobile-safe Retry waiting action retries safe queued records through existing authored outbox drains.
  • Retry excludes attention, uncertain-delivery, and account-mismatched records.
  • Queue events refresh the summary without page polling.
  • Behavior is covered by focused tests and the full suite remains green.
## Problem Offline authored work is durable, but its delivery state is hidden inside the Drafts list. Operators cannot tell waiting work from active sends, see a recent transient failure, or safely retry all eligible queued work after reconnecting. ## Evidence - `frontend/issue-outbox.js` and `frontend/authored-outbox.js` persist queued/sending/attention states. - `frontend/drafts.js` flattens delivery records into individual draft rows without an aggregate delivery status or queue-wide safe retry. - The current service worker reports individual completion/failure, not an actionable queue overview. - All 243 historical issue titles/bodies and 234 PRs were checked: no Delivery Center, sync-status, or retry-queued flow exists. Closest work (#234, #260, #297, #305, #319, #479) built complementary queue durability and individual controls. ## Acceptance criteria - Drafts and queued deliveries are presented as distinct sections. - Delivery summary shows accurate Waiting, Sending, and Needs attention counts. - A 44px mobile-safe **Retry waiting** action retries safe queued records through existing authored outbox drains. - Retry excludes attention, uncertain-delivery, and account-mismatched records. - Queue events refresh the summary without page polling. - Behavior is covered by focused tests and the full suite remains green.
timmy closed this issue 2026-08-10 11:59:25 +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
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#481
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?