Ensuring transaction isolation level integrity after backup restoration in jeet

Ensuring transaction isolation level integrity after backup restoration in jeet

The goal is to verify whether the transaction isolation level guarantees remain intact after a backup of a jeet database is restored in production.

Constraints include scarce official documentation for jeet's isolation implementation and generic backup/restore procedures that may not account for version‑specific behavior in operational environments.

Can we verify that restored data respects the configured isolation level for ongoing transactions?