Connection Close and Fault Scope in Acknowledged Write Recovery from Chromium SQLite IndexedDB

Transaction completion alone does not establish recovery after a crash. We examined how connection closure and fault scope relate to acknowledged writes in Chromium's explicitly enabled SQLite IndexedDB backend. A prospectively registered campaign ran in an ARM64 Ubuntu guest on an Apple Silicon Mac mini. Recovery varied with connection handling even when the delayed-close condition had the later ACK-relative fault deadline. The close-aligned comparison and the immediate-versus-delayed close comparison passed the prespecified Holm correction; the held-duration comparison did not. In the selected fault-scope conditions, browser-process termination preserved relaxed writes that were lost after guest reboot. Retaining additional database connections and silently dropping writes after ACK also removed recovery in the immediate-close condition. File-level records and available traces were consistent with later synchronization after connection release, but did not identify the causal callback or fully explain recovery while connections remained open. These findings apply to the tested host, guest, and forced backend. Physical power loss was not tested, and no safe waiting time or portability guarantee is established.