I'm trying to follow and understand this thread and the whole library system, to no avail. I have a couple of small projects and finally I had to fix them manually by opening the symbols from eeschema using right click on symbol -> Properties -> Edit Properties -> Component Name. I found out that when the automatic rescuing succeeded the name is in the form library_name:component_name instead of just component_name. And both the lib name and component name are "rescue"-something. That works but doesn't look nice so I changed them manually even for the components which worked after the automatic process (and mostly they didn't work). First I of course had to fix the project-specific libraries in Manage Symbol Library (Schematic Library Tables).
Then I started to wonder why this two-stage (or three-stage, or four-stage, depending on how you look at it) process at all in such a way. Basically what I want to have is libraries I have used previously in my project to be used in a new way, and the components I had to be prepended with the new library names. So that intead of having
in the symbol library manager I would have
And in the schematics instead of
I would have
And I wonder why that can't be automatic and why there are two dialogs which then convert my symbol libraries and names to the form which has "rescue" in them instead of just having one dialog and automatically changing old symbol names to new library:symbol names.
But I never understood the library system to begin with and didn't get it to work like I wanted. In the new system it seems to be easier with new projects. Previously I ended up adding new libraries in the old Component Libraries dialog directly by adding a User defined search path, instead of first adding library folders in the Manage Symbol Library (Schematic Library Tables) dialog. Maybe that messed up the migration system so that rescuing didn't work well.
And if you didn't notice it already, I didn't understand almost a word about the directions given in the blog post.
Anyways, KiCad is going into a good direction, it's exciting to learn to use it and to follow where it's going and I wish I can help development in the future.