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

Queue offline issue checklist progress for conflict-safe delivery #907

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

User problem

A mobile operator can reopen cached Today issue details offline, but checklist controls are disabled. This makes the core execution list unusable during an outage even though comments, blockers, reviews, and closure already support durable reconnect delivery.

Scope

Allow an eligible cached open assigned issue checklist toggle to be admitted durably to the account-bound authored outbox, render the intended state as pending, and deliver the exact revision-checked issue body on reconnect. Upstream revision conflicts must remain in Drafts/Attention rather than overwrite newer content.

Acceptance criteria

  • Cached open writable issue details expose 44px checklist controls offline.
  • Toggle success is shown only after durable outbox admission and survives reload under the same account.
  • Delivery PATCHes the intended title/body with expected_updated_at; an already-applied body is confirmed, while a changed revision becomes Attention.
  • Read-only/completed/other-account data remains non-interactive and private-data purge covers the queue through the existing authored outbox boundary.
  • Focused behavioral tests, full suite, and release browser gate pass.

Evidence / non-duplication

Issue #905 intentionally shipped cached details with disabled checkboxes. Historical issue and recent-commit review found no offline checklist delivery implementation; #533 covers blockers, #423 reviews, #427 closure, and #481 delivery-center recovery, but none queues checklist body mutations.

## User problem A mobile operator can reopen cached Today issue details offline, but checklist controls are disabled. This makes the core execution list unusable during an outage even though comments, blockers, reviews, and closure already support durable reconnect delivery. ## Scope Allow an eligible cached open assigned issue checklist toggle to be admitted durably to the account-bound authored outbox, render the intended state as pending, and deliver the exact revision-checked issue body on reconnect. Upstream revision conflicts must remain in Drafts/Attention rather than overwrite newer content. ## Acceptance criteria - Cached open writable issue details expose 44px checklist controls offline. - Toggle success is shown only after durable outbox admission and survives reload under the same account. - Delivery PATCHes the intended title/body with `expected_updated_at`; an already-applied body is confirmed, while a changed revision becomes Attention. - Read-only/completed/other-account data remains non-interactive and private-data purge covers the queue through the existing authored outbox boundary. - Focused behavioral tests, full suite, and release browser gate pass. ## Evidence / non-duplication Issue #905 intentionally shipped cached details with disabled checkboxes. Historical issue and recent-commit review found no offline checklist delivery implementation; #533 covers blockers, #423 reviews, #427 closure, and #481 delivery-center recovery, but none queues checklist body mutations.
timmy self-assigned this 2026-08-15 17:20:51 +00:00
timmy closed this issue 2026-08-15 17:39:44 +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#907
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?