It might seem odd that this release contains functions for both inbound and outbound migration, even though this is the first release of Enzyme v2.
Indeed, there can be no inbound migrations to the first deployment of this release, as legacy v1 funds are un-migratable.
The reasons for including inbound migration functions here are:
to put inbound migration logic into practice for architecting and testing
to get inbound migration logic audited, so that in the case of critical bug discovery, we can quickly iterate to a new release deployment without writing inbound migration logic from scratch
If it's the recommendation of the audit, we can remove (or comment out) all release-level inbound migration logic for the production deployment of this release.