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

Preserve My Work conversation photo drafts across interruptions #963

New Issue
Closed
opened 2026-08-16 12:20:55 +00:00 by timmy · 0 comments
timmy commented 2026-08-16 12:20:55 +00:00
Owner
Copy Link

Problem

My Work already persists reply text per issue, pull request, and unread update, but photo bundles live only in memory. Closing a sheet, switching work, reloading, restarting the PWA, or losing connectivity silently discards captured evidence, captions, ordering, edits, and stable upload operation IDs. Search replies solved this for Search only in #957; the primary My Work flow remains exposed.

Vertical slice

Persist and restore complete photo bundles for issue comments, pull-request comments, and unread-update replies, scoped to the confirmed account and exact conversation. Preserve drafts across close/reopen and reload; clear them only after confirmed posting, durable offline admission, or explicit removal of all photos. Include private-data purge and offline shell registration.

Acceptance

  • Issue, pull, and update photo bundles restore with bytes, order, captions, edits, confirmed upload markdown, and operation IDs.
  • Drafts never leak across accounts or targets.
  • Close/reopen does not erase photos; stale async restores cannot paint another conversation.
  • Successful send or durable offline admission removes the stored bundle; failure preserves it.
  • Removing all photos deletes the stored bundle.
  • Sign-out/private-data purge removes the database.
  • Focused behavioral tests and the full suite pass.

No historical issue or recent commit covers durable My Work conversation photo drafts; #957 is explicitly Search-only.

## Problem My Work already persists reply text per issue, pull request, and unread update, but photo bundles live only in memory. Closing a sheet, switching work, reloading, restarting the PWA, or losing connectivity silently discards captured evidence, captions, ordering, edits, and stable upload operation IDs. Search replies solved this for Search only in #957; the primary My Work flow remains exposed. ## Vertical slice Persist and restore complete photo bundles for issue comments, pull-request comments, and unread-update replies, scoped to the confirmed account and exact conversation. Preserve drafts across close/reopen and reload; clear them only after confirmed posting, durable offline admission, or explicit removal of all photos. Include private-data purge and offline shell registration. ## Acceptance - Issue, pull, and update photo bundles restore with bytes, order, captions, edits, confirmed upload markdown, and operation IDs. - Drafts never leak across accounts or targets. - Close/reopen does not erase photos; stale async restores cannot paint another conversation. - Successful send or durable offline admission removes the stored bundle; failure preserves it. - Removing all photos deletes the stored bundle. - Sign-out/private-data purge removes the database. - Focused behavioral tests and the full suite pass. No historical issue or recent commit covers durable My Work conversation photo drafts; #957 is explicitly Search-only.
timmy self-assigned this 2026-08-16 12:20:55 +00:00
timmy closed this issue 2026-08-16 12:38:08 +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#963
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?