chore(review): 1105 브라우저 파일·캐시·저장소 조치 브랜치를 합친다
This commit is contained in:
@@ -52,8 +52,22 @@ export type PublicCacheInspection = Readonly<{
|
||||
activeReleaseRegistryId: string | null;
|
||||
ownedCacheCount: number;
|
||||
unreadableOwnedCacheCount: number;
|
||||
/**
|
||||
* 0929/02-02. Every owned release cache with a readable marker. To fill
|
||||
* `verified`, inspect reads back every entry of every candidate, so its cost
|
||||
* grows with caches times entries. It has no cursor, deadline or signal
|
||||
* (VD-15's target runtime adds a cursor and a deadline). Keep it off a boot
|
||||
* path.
|
||||
*/
|
||||
releaseCandidates: readonly Readonly<{
|
||||
releaseRegistryId: string;
|
||||
/**
|
||||
* `true` only when every entry was read back and matched the manifest.
|
||||
* `false` when an entry is missing or no longer matches, and also when it
|
||||
* could not be read at all (a failed body read or lookup): inspect does
|
||||
* not tell those apart. Activating the candidate does, and staging the
|
||||
* same manifest again rewrites either (1105/02-02).
|
||||
*/
|
||||
verified: boolean;
|
||||
entryCount: number | null;
|
||||
}>[];
|
||||
|
||||
@@ -152,12 +152,15 @@ export type OpfsPolicyMaintenanceReport = Readonly<{
|
||||
moreObjectsAvailable: boolean;
|
||||
deadlineReached: boolean;
|
||||
/**
|
||||
* 05-04. LOGOUT and ACCOUNT_DELETION only, once every object is removed and
|
||||
* no put or delete of the partition is unfinished: how the sweep of the
|
||||
* partition's now unreferenced chunks ended. For those two reasons the
|
||||
* partition's bytes are gone exactly when this is `COMPLETED` or
|
||||
* `partitionDeleted` is set; a put that begins after the purge reached its
|
||||
* journal check is kept (2026-11-03 05-01).
|
||||
* 05-04. How a LOGOUT or ACCOUNT_DELETION chunk sweep ended.
|
||||
*
|
||||
* @deprecated The reference runtime and the recipe fake no longer set it
|
||||
* (1103/05-01 rest): a sweep after the object walk missed a new object
|
||||
* another tab's put settled during the walk, and the staging of a stopped
|
||||
* put whose journal row lost its partition key, and still said
|
||||
* `COMPLETED`. Such a purge now ends in the partition delete, so
|
||||
* `partitionDeleted` is the one completion signal. Kept so code that reads
|
||||
* it still compiles; it is always absent.
|
||||
*/
|
||||
chunkSweep?: "COMPLETED" | "DEADLINE_REACHED" | "STAGING_STATE_UNREADABLE";
|
||||
/**
|
||||
@@ -166,12 +169,16 @@ export type OpfsPolicyMaintenanceReport = Readonly<{
|
||||
*/
|
||||
corruptObjects?: number;
|
||||
/**
|
||||
* [0929] 05-01. An approved LOGOUT or ACCOUNT_DELETION that damage kept
|
||||
* from finishing, or that found an unfinished put or delete of the
|
||||
* partition (2026-11-03 05-01), removed the whole partition directory and
|
||||
* the partition's journal rows instead, after every put and delete of the
|
||||
* partition then running in any tab had returned. Every byte of the
|
||||
* partition is gone.
|
||||
* [0929] 05-01. An approved LOGOUT or ACCOUNT_DELETION removed the whole
|
||||
* partition directory and the partition's journal rows, after every put
|
||||
* and delete of the partition then running in any tab had returned. Every
|
||||
* byte of the partition is gone; a put that begins after that delete is
|
||||
* kept. A purge that walked every object always ends this way (1103/05-01
|
||||
* rest). One the budget or another tab's change stopped part-way ends this
|
||||
* way only when damage or an unfinished put or delete of the partition
|
||||
* (2026-11-03 05-01) was met; otherwise it reports `moreObjectsAvailable`
|
||||
* and the caller runs it again. For these two reasons the partition's bytes
|
||||
* are gone exactly when this is set.
|
||||
*/
|
||||
partitionDeleted?: true;
|
||||
}>;
|
||||
|
||||
Reference in New Issue
Block a user