Currently rollback-to-stable with no stable timestamp yet skips the data store but rolls back the history store, causing history to be lost. This is because there's a missing check in the flow for the history store.

Arguably if this ever comes up it's an application bug (it requires committing timestamped data and checkpointing without ever setting the stable timestamp) but it's still better for the system to behave consistently.