Fusion "Local" tool library does not update local tool library file (*.hsmlib or *.json) after import

[manseekingknowledge]

When using HSMWorks, changes to a local tool library file (*.hsmlib or *.json) are realized immediately when the local tool library file is changed.  This is great for organizations with where everything is tracked.  Tool library files can be stored in version control systems like Git and easily update by all users while also maintaining a log of tool library changes.

In Fusion there is a "Local" library section in the "Tool Library" view, but it appears that after a tool library file is imported, the link to the local file is lost.  Changes made to the local tool library file are not recognized in Fusion, likewise, changes made in Fusion do not update the local file.  It appears the only way to update the local tool library file is to use the "Export library" feature, and the only way to update Fusion with a local tool library file is to delete any existing library of the same name and re-import it with the "Import libraries" feature.  Also annoying, the "Import tools" feature blindly imports ALL tools from a library, with total disregard for any tool data (like the GUID that every tool and holder has), causing all tools to be duplicated if they already exist in the library.

Assuming "this is just how it is", is there any API call or command line option that might assist with re-establishing the link between the Fusion tool library and the local tool library file?  Or is there something I'm missing here that will allow a tool library to be truly "local", thus allowing changes to the tool library to be tracked via version control like we can already do in HSMWorks?  This can be a critical quality management issue for organizations operating under AS9100, ISO9001, and the like.