I removed the statement “extension”: false; from the library.json file and Omnis Studio v10.1 built a new library. With that I was able to replicate the behavior you describe. Interesting, in the wrong way. 🙂
I cannot think of a workaround at the moment, but I will consider this further in the days ahead.