Feel your pain.
Unlike the above post, I don't move what I would call orphan files, I change the file type from .rb or what ever is the orphan's file name extension to .ken. This way I can sort of file types and see all the files that I have some concerns. I also do this with folders, adding the ken to the front of the folder's names.
If a problem occurs, I look at the missing file if it gives an unable to load error, and I can quickly fine the folder or file.
Onto a related but other subject, I would gladly contribute to a large fund, to have the ruby gurus, look at each and every plugin, and make the following suggestions.
To the author of the plugin, how to make his plugin error free, if that is possible. Plugins that have been modified and have been given the "star of approval' to be listed in plugin in master error free list.
2.If the author doesn't have the time of maybe not the knowledge, and the plugin is worthy, have one of the gurus complete the task if that is OK with the author. The guru would be paid of course.
A plugin in naming systems that gives you some kind of hint which plugin is involved when you look at the plugin in the drop down or context menus. So when you invoked a plugin and it fails, you have some idea which plugin in involved in the plugin directory.
And the last, some time ago I started a database that listed each plugin that I had on my computer, and tied context names to the plugin. Such as, if the plugin was to divided, I would list the plugin, and add the context words, divide, split, cut and so on. That way I could fire up the database, and search on the function I wanted, and the database would give me my choices.
Sorry to drift off subject.
Ken, thanks for you forbearance.
