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

Open saved Today item details and queue replies offline #345

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

Problem

The opted-in offline My Work snapshot only stores card metadata. A cold-offline operator can see Today priorities but openRoutedWork blocks every card, even though issue/PR detail sheets and the durable authored-message outbox already exist.

Vertical slice

Persist a bounded, account-bound, seven-day cache of safe issue/PR read detail when those items are opened online. On cold-offline launch, saved Today issue/PR cards open the existing mobile sheet from that cache. Keep server-state controls disabled, but allow comment/reply composition to enter the existing idempotent authored outbox. Show saved freshness and explicit reconnect guidance when detail is absent. Purge details with opt-out/clear/expiry.

Acceptance tests

  • Detail records retain only allowlisted issue/PR read fields and newest conversation data, are bounded, account-bound, and expire after seven days.
  • An offline saved issue or PR with cached detail opens its existing sheet without a network request and shows the saved timestamp.
  • An uncached saved card reports Details not saved—reconnect rather than silently refusing to open.
  • Offline state-changing controls remain disabled; a safe comment is queued through the existing authored outbox with account binding/idempotency.
  • Opt-out, clear, expiry, and account mismatch prevent detail access.
  • Mobile sheet behavior remains keyboard-safe at phone widths and the full suite passes.

Non-duplication evidence

Issue #228 intentionally shipped metadata-only read-only offline My Work; #234/#252 shipped authored-message queueing; #279 shipped Today ordering; #215/#217 shipped online read-first sheets. None caches or opens issue/PR details from a cold-offline Today queue. Audited all 175 historical issue titles, 166 PRs, 166 releases, and recent origin/main history before filing.

## Problem The opted-in offline My Work snapshot only stores card metadata. A cold-offline operator can see Today priorities but `openRoutedWork` blocks every card, even though issue/PR detail sheets and the durable authored-message outbox already exist. ## Vertical slice Persist a bounded, account-bound, seven-day cache of safe issue/PR read detail when those items are opened online. On cold-offline launch, saved Today issue/PR cards open the existing mobile sheet from that cache. Keep server-state controls disabled, but allow comment/reply composition to enter the existing idempotent authored outbox. Show saved freshness and explicit reconnect guidance when detail is absent. Purge details with opt-out/clear/expiry. ## Acceptance tests - Detail records retain only allowlisted issue/PR read fields and newest conversation data, are bounded, account-bound, and expire after seven days. - An offline saved issue or PR with cached detail opens its existing sheet without a network request and shows the saved timestamp. - An uncached saved card reports `Details not saved—reconnect` rather than silently refusing to open. - Offline state-changing controls remain disabled; a safe comment is queued through the existing authored outbox with account binding/idempotency. - Opt-out, clear, expiry, and account mismatch prevent detail access. - Mobile sheet behavior remains keyboard-safe at phone widths and the full suite passes. ## Non-duplication evidence Issue #228 intentionally shipped metadata-only read-only offline My Work; #234/#252 shipped authored-message queueing; #279 shipped Today ordering; #215/#217 shipped online read-first sheets. None caches or opens issue/PR details from a cold-offline Today queue. Audited all 175 historical issue titles, 166 PRs, 166 releases, and recent origin/main history before filing.
timmy self-assigned this 2026-08-08 21:51:40 +00:00
timmy closed this issue 2026-08-08 22:04:57 +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#345
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?