Status: IN
The conflict-check-then-commit sequence in `MVCCDatabase.commit()` is not atomic — no locking protects the window between checking versions and marking committed, requiring single-threaded execution for correctness.
Source: entries/2026/05/29/snapshot-isolation-mvcc_database-commit.md