Change Details

In rEGREc7b68947a4480cf63846d9d8926ec022b3ae9353 we introduced a migration script to copy the values for the `awayStatusTimestamp` from user options to community configuration, however we haven't actually run in production or anywhere yet. The script checks for differences and valid configuration before storing. Within this task we should check if there are differences in dry mode before the real run so we can analyze if the code that writes into community config is indeed preserving the same data as we used in user options **Acceptance criteria** - [] Run script in dry mode and analyze possible differences - [] If the diff is correct, run the script in all growth wikis **Note on the differences:** Acceptable differences would be storing a long timestamp (maximum span is 1 year ago), so there could be mentors who haven't updated it after we started writing the values in config around Aug 6 2025/wmf-24 (rEGRE8bfc6b50e7e823396f42c304a3632065bc69af01). No other differences should be found unless we identify an issue with the writing code.

In rEGREc7b68947a4480cf63846d9d8926ec022b3ae9353 we introduced a migration script to copy the values for the `awayStatusTimestamp` from user options to community configuration, however we haven't actually run in production or anywhere yet. The script checks for differences and valid configuration before storing. Within this task we should check if there are differences in dry mode before the real run so we can analyze if the code that writes into community config is indeed preserving the same data as we used in user options **Acceptance criteria** - [] Run script in dry mode and analyze possible differences - [] If the diff is correct, run the script in all growth wikis **Note on the differences:** Acceptable differences would be storing a timestamp not updated in a long time (maximum span is 1 year ago), so there could be mentors who haven't updated it after we started writing the values in config around Aug 6 2025/wmf-24 (rEGRE8bfc6b50e7e823396f42c304a3632065bc69af01). No other differences should be found unless we identify an issue with the writing code.

In rEGREc7b68947a4480cf63846d9d8926ec022b3ae9353 we introduced a migration script to copy the values for the `awayStatusTimestamp` from user options to community configuration, however we haven't actually run in production or anywhere yet. The script checks for differences and valid configuration before storing. Within this task we should check if there are differences in dry mode before the real run so we can analyze if the code that writes into community config is indeed preserving the same data as we used in user options **Acceptance criteria** - [] Run script in dry mode and analyze possible differences - [] If the diff is correct, run the script in all growth wikis **Note on the differences:** Acceptable differences would be storing a long timestamptimestamp not updated in a long time (maximum span is 1 year ago), so there could be mentors who haven't updated it after we started writing the values in config around Aug 6 2025/wmf-24 (rEGRE8bfc6b50e7e823396f42c304a3632065bc69af01). No other differences should be found unless we identify an issue with the writing code.