Write-ahead log for LoraDB.
lora-wal is the additive durability layer that sits between
[lora_store::MutationEvent] producers (the in-memory engine) and a
durable byte stream on disk. It is deliberately separate from
lora-store:
lora-storestays storage-only — backends do not learn about logs, segments, or fsync. The mutation surface they already expose (MutationEvent+MutationRecorder) is the only seam.lora-walowns segment files, framing, replay, and truncation. Consumers depending on the no-WAL story (wasm, embedded read-only) can avoid this crate entirely.lora-databaseglues the two together: it installs a [WalRecorder] onto the store and brackets each query witharm/commit/abortmarkers so replay sees query-atomic units even though the recorder fires per primitive mutation.
See docs/decisions/0004-wal.md for the full design and
docs/operations/wal.md for operator-facing semantics.