Expanding on this comment from WT-10779: https://jira.mongodb.org/browse/WT-10779?focusedCommentId=8495751&focusedId=8495751&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-8495751

There's a git branch wt-10779-reeanble-verify-key-hs. This branch reenables a long-dormant check in verify_key_hs. This checks that timestamp ordering between the HS and DS make sense for a given key.

Unfortunately, this check trips. While it's possible the changes I made to to revive this check are somehow broken, I've done as much as I can to verify this isn't the case (see linked comment for a full writeup).

The specific error message is of the form file:T00001.wt, WT_SESSION.verify: [WT_VERB_DEFAULT][ERROR]: __verify_key_hs, 1394: key 0000000623.00/opqrstu has a overlap of timestamp ranges between history store stop timestamp (0, 55020) being newer than a more recent timestamp range having start timestamp (0, 50979): WT_ERROR: non-specific WiredTiger error, see the comments for a patch build link.

But there's also an easy local repro, if you check out that branch and run ./t -c ../../../test/format/CONFIG.stress you should see it trip within a couple of minutes.