v2026.5.14 - SPEC-065 v0.3: Persistent STLStore Closure
v2026.5.14 - SPEC-065 v0.3: Persistent STLStore Closure
Section titled “v2026.5.14 - SPEC-065 v0.3: Persistent STLStore Closure”Release date: 2026-05-14
Profiles affected: :core
Status: Storage feature closure
SPEC-065 v0.3 closes the last runtime gaps in the LSM-backed std.stl.lsm_store path.
What Shipped
Section titled “What Shipped”rebuild_rank_sidecarnow repairs the rank sidecar from primary STL entries and restoresMODE_HEALTHYon success.- The S9 v2 smoke is active and proves rebuild across a clean close/open replay.
mt_deinitnow frees the MemTable-owned skiplist and its nodes instead of acting as a no-op.gs_flush_bytesresets the bytes-owned pool after a successful flush.- A focused regression pins pool reset behavior.
- Reference docs and a tutorial now cover the persistent STL workflow.
Why It Matters
Section titled “Why It Matters”The STL primary keyspace is the durable ledger truth. The rank sidecar is the append-order index that auditors, witnesses, proof generators, and replay validators need. v0.3 makes that index repairable, which turns degraded sidecar state into an operational recovery path instead of a dead end.
The pool reset also changes long-running producer behavior. The owned bytes pool now bounds one in-memory batch. After a successful flush, earlier MemTable slices have been encoded into the SSTable image and the pool can be reused.
Remaining Work
Section titled “Remaining Work”SPEC-061 v2 and SPEC-088 still need their consumer-side amendments. Commit proof production and sovereign durability policy remain outside the v0.3 facade.