[CaffeinatedCoder]

Part of #296 (section 8, "wrong today"). Docs only, README.md only.

The README showed APIs that BLite does not have, so a sample copied from it did not compile, and nuget.org shows the same README for every package. Each corrected sample was compiled and run against src/ at 0450b97 in a scratch console app (not committed): 12 checks, all pass.

Section	Was	Now	Evidence
Custom ID converters	collection.FindById(...)	await collection.FindByIdAsync(...)	v4 removed sync CRUD
Encryption: master key, multi-process	new AppDb(...)	new AppDbContext(...)	the generator only handles a class whose name ends in Context (BLiteConventions.DbContextClassSuffix); the encryption sample declares AppDbContext
Encryption: migration and key rotation	MigrateToEncryptedAsync, MigrateToPlaintextAsync, RotateEncryptionKeyAsync, KeyRotationOptions	one sentence saying there is no such API yet	no match in src/
Secure erase	HasSecureErase(true), db.VacuumAsync() on a context	what the code does: a delete zero-fills its bytes on the page (DocumentCollection.DeleteCore → CompactPage + Clear, DynamicCollection.DeleteSlot → SlottedPageUtils.CompactAndErase); the file gets the zeroed page at the next checkpoint; VacuumAsync(new VacuumOptions { SecureErase = true }) on the engine or a collection, then CheckpointAsync	HasSecureErase has no match; DocumentDbContext has no VacuumAsync. Checked at run time: a marker string is gone from the typed .db after delete and dispose; on a BLiteEngine it stays in .db until CheckpointAsync
TimeSeries	engine.Commit()	await engine.CommitAsync()	BLiteEngine has CommitAsync only
Schema-less read	d.GetString("status")	d.TryGetString("status", out var s) && s == "pending"	BsonDocument has no GetString
Zero-copy scan	orders.Scan(...) with reader.TryReadString(...)	ScanAsync with the element loop the tests use	no Scan on DynamicCollection, no TryReadString on BsonSpanReader
Index management	CreateIndex, CreateVectorIndex, CreateSpatialIndex	the *Async forms	DynamicCollection has async index creation only
Reading fields	FindById, doc.GetString, doc.GetDouble, doc.Id	FindByIdAsync, GetValue(...).AsString/AsDouble, TryGetId, TryGetString	BsonDocument API
Sessions	col.Insert(eventDoc)	await col.InsertAsync(eventDoc, ct)	v4
Multi-file migration	BLiteMigration.ToMultiFile( / ToSingleFile(	await ...ToMultiFileAsync( / ToSingleFileAsync(	only the async forms exist
Roadmap list	"offline migration helpers, and online key rotation"; HasSecureErase(true); ToMultiFile()	removed / corrected to match the above	as above
Documentation links	RFC.md, C-BSON.md (relative)	absolute GitHub links	relative links break in the packed README on nuget.org

Not changed here (separate items in #296): the README structure, the outdated version banners, the duplicated BLQL section, and RFC.md / C-BSON.md themselves.

Found while checking, not fixed here:

• GdprStrictValidator warns at run time that "Deleted document slots are not currently zeroed at the page layer", but both delete paths zero them (checked at run time above). The warning, and its pointer to MISSING_FEATURES.md §3, look out of date.
• A DocumentDbContext subclass whose name does not end in Context gets no generated code and no diagnostic; its collection properties stay null and the first call throws a NullReferenceException.

Line endings stay CRLF; the diff touches only the changed lines.

Conflicts with other open PRs

Conflicts with #310 (write-write conflict detection) in README.md, in the roadmap list. Resolution: #310's BLiteSession line (the first committer wins) and this PR's migration line (ToMultiFileAsync / ToSingleFileAsync). Either PR can land first; I will push the resolution to the second.

🤖 Generated with Claude Code

[CaffeinatedCoder]

The two findings listed under "Found while checking" are now issues:

• GdprMode.Strict warns that deleted documents are not zeroed, but every delete zero-fills them #299 — GdprMode.Strict warns that deleted documents are not zeroed, but every delete zero-fills them (overflow pages included). The database file gets the zeroed page at the next checkpoint, which is the only real caveat.
• A DocumentDbContext whose class name does not end in "Context" gets no generated code and no diagnostic; its collections stay null #300 — a DocumentDbContext whose class name does not end in Context gets no generated code and no diagnostic, so its collections stay null. That is why this PR renames AppDb to AppDbContext in the samples.

Both are also listed in #296 section 8.

[mrdevrobot]

Changes requested. Every changed line checks out against the source. But the same Read block (README ~801–808) still shows orders.QueryIndex(...), VectorSearch(...), Near(...) and Within(...), which do not exist: DynamicCollection only has the *Async forms returning IAsyncEnumerable<BsonDocument>. Fix those four lines with await foreach and this can go in.

[CaffeinatedCoder]

Done in f38f1e0: the four lines now use await foreach over QueryIndexAsync, VectorSearchAsync, NearAsync and WithinAsync with the parameter names from DynamicCollection.cs:1041–1142, and a scratch project compiles them against BLite.Core.