StoreBootResolution
Defined in: packages/client/src/store-boot.ts:53
The outcome of resolveStoreBoot: the URL to open the store at, its backend, and the boot verdict.
Properties
Section titled “Properties”dataDir
Section titled “dataDir”dataDir:
string
Defined in: packages/client/src/store-boot.ts:55
The PGlite dataDir URL, always assembled by resolveStoreDataDir (the one URL assembler).
storageBackend
Section titled “storageBackend”storageBackend:
ResolvedStorageBackend
Defined in: packages/client/src/store-boot.ts:57
The resolved backend, for diagnostics.
verdict?
Section titled “verdict?”
optionalverdict?:StoreBootVerdict
Defined in: packages/client/src/store-boot.ts:65
The executed boot verdict — always a TERMINAL one (the record-clearing verdicts re-classify rather than
return). Absent on the passthrough backends (memory / filesystem), which have NO meta machinery.
Present on every browser classification — in particular it is the signal that an opfs CANDIDATE was stood
up UNCOMMITTED (virgin-create): the mint seam must run the commitment barrier before exposing that store
to writes (plan step 10b/11).