Thanks for cutting it down a little. Simpler leaves less guessing about real cause.
I think what’s happening is that some consistency checking code that was added March 10 is upset about the partial database that the direct restore is creating, as only the specified version is put in the database (it’s the only needed one), yet the other dlist files are still visible. Normally this is inconsistent, but it’s proper here.
You can probably see the same issue in a regular repair with a single version, specifying dbpath to avoid guessing where it is, but making sure it doesn’t exist.
This turns repair into recreate. If you don’t give version the database gets all, which is slower but makes the database look consistent, to avoid triggering check.
After that, you can see if restore works with whatever version you really want.