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

Keep the Today queue automatically ready offline #349

New Issue
Closed
opened 2026-08-08 23:09:15 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-08 23:09:15 +00:00
Member
Copy Link

Problem

Operators who opt into offline work still have to open every Today item while online. The dashboard saves Today issue/PR details only from openIssueSheet / openPullSheet, so an unopened planned item fails offline with “Details not saved—reconnect”.

Slice

After a fresh authenticated snapshot, proactively warm allowlisted detail for the bounded Today queue. Refresh only items whose updated_at changed, use at most two concurrent requests, retain prior detail on transient failure, and expose an accessible readiness summary with retry. PR review diffs remain online-only.

Acceptance

  • An opted-in five-item Today queue becomes 5/5 offline-ready without opening sheets.
  • Unchanged revisions make no detail requests; one changed revision refreshes only that item.
  • At most two fetches run concurrently; failures preserve prior cached detail and are retryable.
  • Wrong-account, expired, opt-out, and allowlist protections remain intact.
  • Mobile readiness/retry controls are accessible at 390px and the app shell precaches the coordinator.
  • Focused tests and full suite pass.

Duplicate check

Historical #345/#346 opens details already saved by manually opening Today items; #347/#348 does the same for unread updates. No historical issue title or recent commit implements proactive Today hydration or revision-aware readiness.

## Problem Operators who opt into offline work still have to open every Today item while online. The dashboard saves Today issue/PR details only from `openIssueSheet` / `openPullSheet`, so an unopened planned item fails offline with “Details not saved—reconnect”. ## Slice After a fresh authenticated snapshot, proactively warm allowlisted detail for the bounded Today queue. Refresh only items whose `updated_at` changed, use at most two concurrent requests, retain prior detail on transient failure, and expose an accessible readiness summary with retry. PR review diffs remain online-only. ## Acceptance - An opted-in five-item Today queue becomes 5/5 offline-ready without opening sheets. - Unchanged revisions make no detail requests; one changed revision refreshes only that item. - At most two fetches run concurrently; failures preserve prior cached detail and are retryable. - Wrong-account, expired, opt-out, and allowlist protections remain intact. - Mobile readiness/retry controls are accessible at 390px and the app shell precaches the coordinator. - Focused tests and full suite pass. ## Duplicate check Historical #345/#346 opens details already saved by manually opening Today items; #347/#348 does the same for unread updates. No historical issue title or recent commit implements proactive Today hydration or revision-aware readiness.
timmy was assigned by rockachopa 2026-08-08 23:09:15 +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#349
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?