transaction-recovery-has-no-crash-path

Status: IN

Transaction abort is a status-change-only operation with no disk rollback, and MVCC correctness depends on monotonic counters that have no persistence mechanism, meaning a crash simultaneously leaves aborted-transaction writes on disk and resets the ordering counters that determine visibility — both invariants fail together.

Justifications

Both abort cleanup and ordering invariants exist only in volatile memory

Depends on (SL): abort-is-status-change-not-disk-rollback, mvcc-counters-must-be-monotonic

JSON