Tracking and resolving a schema drift cause

Yeah its thousands of existing topics and related content so the one offs a are bit of a mess

Merge two Discourse sites into one which uses a different script, but the same basic idea.

Did discover another nuance of schemas. So we removed the automation plugin from the deployment and redeployed. Then i noticed that schema_migration seemed to revert back to 0823 as the latest. So I thought I was good to go without installing the automation plugin into the instance that I am merging in. Well when i did another run of import i got a PG::UndefinedTable: ERROR: relation "discourse_automation_automations" does not exist error so even though the migrations version rolled back the schema changes tied to it in the actual db were still around it seems.