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

Show and safely clear private device storage #998

New Issue
Closed
opened 2026-08-17 03:20:37 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-17 03:20:37 +00:00
Member
Copy Link

Problem

Stackchain stores private drafts, queued actions, offline work, and caches across browser storage, but Device setup neither inventories that data nor lets an operator reclaim only reproducible caches. The existing clear action targets offline work while full purge is coupled to sign-out, so operators on shared or storage-constrained phones cannot make an informed choice.

Vertical slice

Add a Private device storage section to Device setup that reports browser usage, distinguishes unsynced private work from cache copies, supports cache-only cleanup without deleting drafts/outboxes, and guards full private-data cleanup behind explicit confirmation when unsynced work exists. Reuse the authoritative private-data registry and report partial failures honestly.

Acceptance tests

  • Inventory reports registered Stackchain databases and owned caches without exposing private content.
  • Cache-only cleanup deletes Stackchain caches while preserving private databases and stackchain.* storage.
  • Full cleanup requires a second confirmation when unsynced work is reported, stops worker delivery, and uses the shared purge path.
  • Blocked deletion produces an actionable failure instead of a false success.
  • Unsupported quota/storage APIs degrade safely.
  • Packaged frontend includes the storage controller and focused/full suites pass.
## Problem Stackchain stores private drafts, queued actions, offline work, and caches across browser storage, but Device setup neither inventories that data nor lets an operator reclaim only reproducible caches. The existing clear action targets offline work while full purge is coupled to sign-out, so operators on shared or storage-constrained phones cannot make an informed choice. ## Vertical slice Add a Private device storage section to Device setup that reports browser usage, distinguishes unsynced private work from cache copies, supports cache-only cleanup without deleting drafts/outboxes, and guards full private-data cleanup behind explicit confirmation when unsynced work exists. Reuse the authoritative private-data registry and report partial failures honestly. ## Acceptance tests - Inventory reports registered Stackchain databases and owned caches without exposing private content. - Cache-only cleanup deletes Stackchain caches while preserving private databases and stackchain.* storage. - Full cleanup requires a second confirmation when unsynced work is reported, stops worker delivery, and uses the shared purge path. - Blocked deletion produces an actionable failure instead of a false success. - Unsupported quota/storage APIs degrade safely. - Packaged frontend includes the storage controller and focused/full suites pass.
timmy was assigned by rockachopa 2026-08-17 03:20:37 +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#998
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?