Status: IN
The LSM read path maintains correctness across memtable flushes by searching newest-first (memtable then SSTables in reverse sequence order) using a reference swap rather than deep copy for the frozen memtable.
The newest-first search order is correct but the flush implementation creates a window where data exists in neither memtable nor SSTable list, causing transient read misses
Depends on (SL): lsm-newest-first-read-path, lsm-memtable-swap-is-reference-not-copy
Unless: flush-clears-then-appends