fix(storage): delete a partition's IndexedDB dataset when an authorized purge cannot open it (05-03)
LOGOUT and ACCOUNT_DELETION purged row by row and so needed an open that a corrupt budget or binding row always rejected, leaving personal rows on the device. After authority approval, a purge that finds the dataset rejected by admission now deletes that partition's own database and reports it; healthy datasets and other partitions are untouched. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
9cae587aea
commit
3e37fbf0ed
@@ -144,6 +144,13 @@ export type IndexedDbLifecycleBatchReceipt = Readonly<{
|
||||
scannedRows: number;
|
||||
deletedRows: number;
|
||||
budgetExhausted: boolean;
|
||||
/**
|
||||
* 05-03. Present when an authorized LOGOUT or ACCOUNT_DELETION found the
|
||||
* dataset's governance rows unreadable, so no row could be purged one by
|
||||
* one, and deleted the partition's whole database instead. Rows are then
|
||||
* not counted.
|
||||
*/
|
||||
datasetDeleted?: true;
|
||||
}>;
|
||||
|
||||
export type IndexedDbLifecycleAuthorityRequest = Readonly<{
|
||||
|
||||
Reference in New Issue
Block a user