I was looking at the wt verify code and noticed that it's accumulated a lot of technical debt recently. A few of the args mentioned in the usage are either not parsed or aren't used (from what I saw, -a and -d dump_history).

Also, there doesn't seem to be a way to verify the history store from the command line. We seem to have switched to a model where we verify it on startup with the verify_metadata option to wiredtiger_open. But this isn't supported properly in the tool. Additionally, that function doesn't respect the flags that work for data files such as dump_pages.

If you try to verify it like any other data file, you get an EBUSY return code so something is not right here.