embedded object are meant to be embedded in the patch (hence the name) ,
but yes it can be 'saved to disk' if you wish...
I quote this, since in the new version, instead what you do if you want a copy outside a patch, is to 'add to library...'
this add a version to your (selected library), which then could potentially unloaded to the community.
but could be in a local library, if you do not want to share (yet i hope )
I followed the approach to stop users modifying factory objects... (instead you get your own personalised copy in your library) which could create a support nightmare!
(its also handles things like creating new uuids )
again, id highlight the workflow is fixed/improved in the next version, ignore 1.0.8 in this regard as its got quite a few issues.
and no, Ive no idea when 1.0.9 will be released, what I do know is that we know of a couple of outstanding issues, that it makes sense to fix before we release it... hopefully then 1.0.9 could be a 'release candidate', such that if there are no show stoppers found it could then be a 'proper' release.
(note: this obviously means, its likely its own bug fixes before that release, to ensure stability)