Hello! I have been updating the poor quality roads in South Dakota in OSM for both overall correctness and so CityStrides is up-to-date. Some of the cleanup edits don’t seem to be processing correctly, e.g. 20th Avenue Southwest - CityStrides and 10th Street Southwest - CityStrides are overlapping when they shouldn’t be. Just wanted to give a heads up.
The map visual is handled by Mapbox - I have no control over when they update that visual.
The street/node data is managed by me. The date of the last city sync is shown on the city page, just under its name. It looks like the city was last synced in December, so that could be the reason for your latest edits not being reflected in CityStrides.
So the changes did show up (I cleaned up Watertown last year), but they showed up weird. The area I highlighted should just be 10th Street Southwest, but when you look at 20th Avenue Southwest it has nodes that should be just in 10th Street Southwest.
To help clarify, this does seem to be a bug in CityStrides. The north few nodes of 20th Avenue Southwest in Citystrides were last called 20th Avenue Southwest in OSM on 2 January 2024, when they were corrected to 10th Street Southwest. It seems both of the CityStrides streets have those north nodes while only 10th Street Southwest should have them. The update in OSM was long enough ago that CS would have picked up on it by now.
Ah, yeah, I was not handling the situation where a Way is renamed from one Street name that exists in CityStrides to another Street name that exists in CityStrides for the same city.
I think I have a fix worked out, but I need to review it a bit more to make sure I’m not causing other different problems. 
OK, the updated code did remove the nodes this time.
It seemed to leave some cache in place, which was unexpected. I’m looking into that now.