Add CheckpointAsync and DisposeAsync to DocumentDbContext

[Copilot]

DocumentDbContext.Dispose() releases the storage engine without flushing the WAL, leaving the .blite file potentially non-self-contained — fragile to copy or ship cold.

Changes

• IDocumentDbContext — extends IAsyncDisposable; adds Task CheckpointAsync(CancellationToken ct = default)
• DocumentDbContext — implements CheckpointAsync() (delegates to _storage.CheckpointAsync(ct)); implements DisposeAsync() which checkpoints under a try/finally so resources are released even if the checkpoint throws
• Tests — three new tests covering explicit CheckpointAsync, await using auto-checkpoint, and interface-level access

Usage

// Option 1: explicit flush before close
using var db = new HelpDbContext(path);
await db.HelpChunks.InsertBulkAsync(chunks, transaction: null);
await db.CheckpointAsync(); // WAL merged into page file

// Option 2: auto-checkpoint via DisposeAsync
await using var db = new HelpDbContext(path);
await db.HelpChunks.InsertBulkAsync(chunks, transaction: null);
// DisposeAsync checkpoints automatically — file is self-contained after this point

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• av-build-tel-api-v1.avaloniaui.net
  • Triggering command: /usr/share/dotnet/dotnet dotnet exec --runtimeconfig /home/REDACTED/.nuget/packages/avalonia.buildservices/11.3.2/tools/netstandard2.0/runtimeconfig.json /home/REDACTED/.nuget/packages/avalonia.buildservices/11.3.2/tools/netstandard2.0/Avalonia.BuildServices.Collector.dll (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[Copilot]

Pull request overview

This PR adds an explicit checkpointing API to DocumentDbContext and introduces async disposal semantics so callers can ensure committed WAL records are merged into the main page file before closing—making the primary .blite/.db file self-contained for cold copy/shipping scenarios.

Changes:

• Extend IDocumentDbContext to IAsyncDisposable and add Task CheckpointAsync(CancellationToken ct = default).
• Implement DocumentDbContext.CheckpointAsync() (delegates to StorageEngine.CheckpointAsync) and DocumentDbContext.DisposeAsync() (checkpoint + guaranteed resource cleanup via try/finally).
• Add tests for explicit checkpointing, await using auto-checkpoint, and interface-level access.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
tests/BLite.Tests/DbContextTests.cs	Adds tests for explicit CheckpointAsync, DisposeAsync auto-checkpoint, and interface exposure.
src/BLite.Core/IDocumentDbContext.cs	Extends the interface with IAsyncDisposable and adds CheckpointAsync(ct).
src/BLite.Core/DocumentDbContext.cs	Adds CheckpointAsync(ct) and DisposeAsync() implementation to checkpoint WAL before releasing resources.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.