I think the summary here is:
- it’s unclear how the account was set to ADT in the past, but it’s correct now
- the observations with incorrect time zones can be (painstakingly) batch updated
- if they are not updated to the correct time zone, then they will continue to sort “incorrectly” because iNat has no way of knowing the time zone is wrong – this is not an issue the developers can fix
- there is still a known bug with the apps, which will probably be fixed when the new app is released
- there is also a planned feature for auto-assigning timezones in the web uploader based on location that will hopefully mitigate future issues like this
- improved onboarding is on the agenda, which would probably also prevent similar issues
If there are steps to reproduce the incorrect account time zone, that can be further investigated. Otherwise, there isn’t much to do.