yeah, if we keep the multi objects per file, we need to add support for this in the editor....
I guess as a 'bug fix' we could make objects within a multi file 'read only', this would mean the owner would not do this accidentally.
that seems like a bug... another user should not be able to save/edit one of your files... the save option should not be available, they should have to 'copy to library' , which would then 'not be a problem'.
this is an important bug, since Axoloti 'reserves the right' to reset a change that is made to a library object that you 'dont own' i.e. factory object or outside your area in the community library.
(of course, id recommend users use a GitHub library for even their own personal objects, so changes are not lost, as can be reverted via GitHub)
feel free to update the user guide with a warning, though frankly i suspect it'll be a detail that even if a user reads will be quickly 'forgotten', so we need the application to enforce/remind.