Status: OUT
No storage engine has a fully safe crash recovery path: compaction lacks atomicity, WAL replay ignores batch boundaries, and CRC checksums leave routing metadata unprotected — corruption can enter via unprotected metadata, persist through non-validating compaction, and survive recovery via batch-unaware replay.
Three independent crash-recovery gaps compound: atomic file operations are absent, batch integrity is unchecked during replay, and metadata sits outside CRC coverage
Depends on (SL): compaction-lacks-crash-safety-across-implementations, replay-lacks-batch-atomicity-across-implementations, payload-only-crc-leaves-metadata-unprotected