Sorry for the delay. This was our update test script. core/upgrade-test.sh at main · classic-terra/core · GitHub
And everything passed the test. Everything also worked fine on testnet, and on a full node running on mainnet. This is when we posted the first edition of v1.0.5. There was no problem with the v1.0.5
Then I decided to do a full simulation of the upgrade to v2.0.4 (our next upgrade). This is when I caught the issue. The code that was supposed to trigger and load the module states into memory never got triggered. It was triggered in our original test because the state was loaded from genesis. Ultimately, we decided to trigger the module code at a certain block height in order to get it to run. This enables us to proceed with the v2 upgrade.