Quinn “The Eskimo!” states... "There are limited circumstances under which a bundle can be unloaded" Where does Apple document these 'limited circumstances'?

If an application calls CFBundleUnloadExecutable on a bundle that links to the Objective-C runtime the inference of the above referenced documents is that the Objective-C runtime will get corrupted. Surely macOS could catch this case and block CFBundleUnloadExecutable from doing the unload? Or provide some mechanism to define such a bundle as "not unloadable"?

Yes, what a pain are these all pervading property lists. No undo is, perhaps, not a serious problem, but I would really like the ability to just cancel my changes and start again from where the file was last saved (like every other development environment I have worked with, dare I say it!).

Now we have notarization .DS-Store files are a potential problem. I copied a notarized package over to another disk and Finder inserted .DS-Store files into the package folder structure, which invalidated the notarization. Come on Apple you have got to admit that is pretty dumb!