[delayed]

Unironically, try asking Claude to make it for you.

Then please publish it. Others can ask Claude too but it's stupid, and one central repository will have everyone's bugfixes and feature recommendations.

Do you have suitable aerial imagery available? Because if it that's the case (and this is the case in most countries) aligning 30 or so roads is an evening of mapping once you've bitten the bullet and learned to use JOSM (which is really not hard for most people with some technical background).

Did you ask for help in the community group for your country?

> That could be fixed easily if there was a convenient app that recorded my driving and uploaded it to a central source, processed it, and converted that into edits for me to confirm.

Mapping requires more than that. GPS traces can be useful in areas where no recent aerial imagery is available, but automated importing of that would cause a lot of errors.

[delayed]

Record your driving using any app that can export a GPX file (e.g. Strava, RideWithGPS, or Komoot). Import that GPX file into the standard OSM web editor and trace the displayed tracks.

[delayed]

Have your phone camera pointing at the road as you drive, uploading shots to Mapillary. Mapillary will automatically detect signs from the photos. In JOSM you can toggle an imagery layer of those detected signs. This is how speed limits, stop/give-way signs, maxweight and other details have been mapped in many regions.

Start with one, that already makes the map better.