That would be interesting to try, to see what happened. I’ll try to import it into my standard test project.
I’ve restored a backup so I’m ok as far as this project goes. But in the process, I’m remined of how restoring a backup is more cumbersome and with more potential risk than it might be. I’ve posted about this before. But here’s the main takeaway:
When Scrivener creates the timestamped zip file with the name “ProjectName-bak-2022-02-26T16-18.zip,” it should also rename the internal project folder and scrivx files with the same timestamp, locking container and contents together as a unique backup set. That would make it impossible for a bak to overwrite a current [project pf the same name.]