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

Make mobile Draft replacement and discard failure-safe #625

New Issue
Closed
opened 2026-08-12 05:50:33 +00:00 by timmy · 0 comments
timmy commented 2026-08-12 05:50:33 +00:00
Owner
Copy Link

Evidence

Draft metadata is currently rewritten before screenshot deletion in frontend/unfiled-captures.js. If IndexedDB deletion fails, replacement/discard rejects after the visible Draft has already changed, contradicting the preserving UI. Existing tests cover only successful attachment deletion.

User impact

Mobile operators must never lose or replace a Draft when screenshot cleanup fails. The UI must report the true committed state and retain resumable work.

Acceptance criteria

  • A failed replacement attachment deletion restores the exact prior Draft list and removes the staged replacement attachment.
  • A failed discard attachment deletion leaves the Draft visible and resumable.
  • Successful replacement/discard keep metadata and screenshots synchronized.
  • Concurrent/stale replacement remains guarded by the expected oldest ID.
  • Focused fault-injection tests and the full suite pass.
## Evidence Draft metadata is currently rewritten before screenshot deletion in `frontend/unfiled-captures.js`. If IndexedDB deletion fails, replacement/discard rejects after the visible Draft has already changed, contradicting the preserving UI. Existing tests cover only successful attachment deletion. ## User impact Mobile operators must never lose or replace a Draft when screenshot cleanup fails. The UI must report the true committed state and retain resumable work. ## Acceptance criteria - A failed replacement attachment deletion restores the exact prior Draft list and removes the staged replacement attachment. - A failed discard attachment deletion leaves the Draft visible and resumable. - Successful replacement/discard keep metadata and screenshots synchronized. - Concurrent/stale replacement remains guarded by the expected oldest ID. - Focused fault-injection tests and the full suite pass.
timmy self-assigned this 2026-08-12 05:50:33 +00:00
timmy closed this issue 2026-08-12 05:56:47 +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#625
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?