For the "small default" release, we skipped this migration. Before deploying as default to the remaining wikis, we will copy over preferences as follows:Copy over any opt-out beta preferences so these users still have the legacy conflict workflow after deploying TwoColConflict as the new default.
The opt-in beta feature preference is `twocolconflict` and the newWe skipped this migration for the "small default" release, opt-out preference is `twocolconflict-enabled`but it needs to be completed before going default on the remaining wikis.
| **priorbeta pref staterence** | **new pref staterence** | **behavior** |
| no preference | opted-in or no preferencee yet | default to enabled |
| no preference | opted in | en-out | disabled |
|| opted-in | opted-in or no preference | opted out | disabled |e yet | enabled; delete beta preference |
| beta feature en| opted-in | opted-out | disabled | no preference | enabled |; delete beta preference |
| beta feature en| opted-out | opted-in or no preference yet | disabled | opted in | enabled |; set new preference to opt-out; delete beta preference |
| beta feature enabled | opted out | disabled |
| opted out | no preference | disabled |
| opted out | opted in | enabled |
| opted out | opted out | disabledopted-out | opted-out | disabled; delete beta preference |
So the mergeThe logic is simplye: If a beta opt-out exists, `$newPref ??copy that to an opt-out for the new preference, $oldPref ??overwriting it. The beta preference is removed to prevent this from happening a second time (for example, true`after the user opts-in).