These could use a bit more work on the shape.
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/64703221

This should not have a name and SR is the wrong abbreviation...

osm.wiki/Names#Name_is_the_name_only

Try ref=WA 18 and noname=yes instead?

Could we get the imagery you're seeing? Also don't forget to update or remove the source source:maxspeed tag
---

Published using OSMCha: https://osmcha.org/changesets/139917500

I guess it'd help if I paid closer attention to what actually got tagged. whoops
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/139888614

Section modified is not a bridge, it's on an embankment.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/139888614

access=yes is likely wrong as I'm pretty sure OKC prohibits pedestrians in the street when a sidewalk is available.
---

Published using OSMCha: https://osmcha.org/changesets/139605631

This is oneway only part of the day as indicated by oneway:conditional
---

Published using OSMCha: https://osmcha.org/changesets/139609051

There was no lane change count. Your mapper incorrectly tagged an exit ramp as another lane because it had a shoulder extension line across the opening, which is the standard US way of marking ramp entrances that do not have a dedicated lane since 1997.

Literally nobody familiar with US signage would come up with such an interpretation for the signage available.

I'm intimately familiar with the intersection in question, and if this is the case, then nobody on your team is qualified to map in the United States.

When more specific tags contain accurate information, please do not revert to more vague methods.

I'm intimately familiar with the intersection in question, and if this is the case, then nobody on your team is qualified to map in the United States.

I'm intimately familiar with the intersection in question, and if this is the case, then nobody on your team is qualified to map in the United States.

I'm intimately familiar with the intersection in question, and if this is the case, then nobody on your team is qualified to map in the United States.

When a more specific key is available and the information in it is valid, then that takes precident towards more general tagging schemes. Please don't iterate backwards.

I'm intimately familiar with the intersection in question, and if this is the case, then nobody on your team is qualified to map in the United States.

Sorry, my mistake, looks like a third one was added but you only changed the last one and did not add a placement value.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/139071591

There's clearly only two lanes here.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/139071591

Please stop tagging destination:lanes until after you've driven in the US; these values aren't accurate.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/139076821

Please stop changing destination:street to destination. There's no reason to do this.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/139082121

OK, for destination:lanes tagging, it's fairly obvious that you need someone who knows how to drive in the US to get the correct values. As for destination:street bulk retagging being a part of the workflow, please make it not part of your workflow and fix your data consumer.