To reproduce:

• create a pack with 3 paths "x", "y", "z"
• edit the package by deleting the "y", then adding it back (so its now the 3rd path and you have "x", "z", "y"), then save
• BUG - observe path list of just "x", "z", EXPECT "x", "z", "y" or at least all three paths in the list

Did some light debugging while building D11652 and I believe this is a problem in the javascript layer - the server ends up getting back "x", "z" as the set of paths. (It might even be an issue with the core multi row manager...)