Repository navigation
Foldlite DB 0.2.0
Foldlite DB 0.2.0 unifies native and Python callback document acceptance, commits, and replay, and closes all ten findings in the engineering review.
- Native reset holds stable ownership locks; checkpoint paths cannot overwrite another database's log.
- New FOLDLOG2 frames persist predecessor hashes to detect omitted, reordered, and spliced frames.
- Every callback append API uses native preparation and deduplication. Maps, reducers, and finalizers complete before durable commit; disposable callback caches recover from original batches.
- External projection descriptors bind state and consumed progress together. Version/reference changes rebuild from the authoritative source.
- Native and browser hosts share metadata-source, payload-depth, and relocated Wasm output-buffer rules, with shared conformance fixtures.
- Core checks run before PR merges. Storage failure injection, lifecycle oracles, real legacy migration fixtures, and measured replay/memory/latency reports strengthen validation.
This minor release includes deliberate compatibility changes. Existing FOLDLOG1 logs remain readable and exportable, but new appends require verified copy migration:
from foldlitedb import Database
# Close the source owner first; the destination must not exist.
Database.migrate("old.fold", "migrated.fold")Migration preserves original batch boundaries and leaves the source unchanged. Keep the original backup until the migrated database has been verified with its view.
Primary filenames ending .cache/.lock or containing .cache. are reserved for sidecars. Source names beginning _ are retained metadata and do not contribute to views in either host. A primary callback now supplies query()/rows(); callback preview()/changes() explicitly reject unsupported operations. Python callbacks remain trusted deterministic code and require version/reference changes when their behavior changes.
Local validation passed 185 Python, 53 Rust, 17 Chromium, and 13 Node tests, plus source-rebuilt wheel checks, executable documentation, reproducible compiled modules, and 1k/10k/100k replay fixtures. The publishing workflow tests five native-wheel platforms and a rebuilt source archive, validates the exact distributions, and publishes those artifacts without rebuilding.
See the engineering review and resolution, API and migration guide, and PRs #6, #7, #8, #9, and #10.