Many migrations are not proper rails migrations, they are changes to Wagn content. Sometimes this is just loading some new cards, but often it will involve manipulations to rule cards.
We need a framework for loading and modifying card content whenever code changes are deployed. This is a critical need for Wagn Core, and it will be important to support the Wagneering of packs in the Wagn 2.0 API.
duplicate of support card content migrations
+discussed in support tickets+relevant user stories