@flyedge great info, thank you…
I see the issue, but don’t yet know why it is behaving this way (compared to previous releases) and don’t know how to fix it yet.
luxon (which returns the dates matching a repeating rule RRULE) might have fixed their bad behavior…
where they jammed the non UTC date onto the UTC time
in this old case it would have been
2022-02-5-10T01:00:00Z
where I was correcting the mangled event date