Thanks for fixing some of those issues! Just be careful: you removed a valid address point without adding its tags to any other object. I've re-added the address in question.

D'oh! Pardon this seeming out-of-place edit from this account, it should have been done under my personal username. I stand by the edit regardless, but it's not normal procedure for Kendall County GIS to be editing so far from the county boundary.

I think this would be a good spot for "short_name". I favor the "name" key essentially being equivalent to "official_name", then using "short_name" for any informal common abbreviation.
In my hometown, we had the "Alex M Mantino Junior High School", but everyone just called it "Mantino", even in official communications from school staff. But it's still not the official name.

And jeez, looking at it now, I've fallen way behind on some of this new construction and bike paths!

I do! You can see the latest Kendall County aerials on our GIS portal. Here's the webmap for our "latest imagery" basemap.
https://maps.co.kendall.il.us/portal/apps/mapviewer/index.html?webmap=49b9629323544f6c8b2482b51a80bf58
Imagery was flown this March.

There are two segments of 126, just east of US 30 / IL 59, which have the tag "la2=separate" added to them. I'm assuming that's a typo of some sort, but it wasn't obvious what it should have been, so I left it alone.

Oh yeah! Mapping electric utilities can get super intense and detailed. I only know a bit about it myself, but take a look at power=* for examples of all kinds of stuff.
The power lines you added might even be considered "minor_line", which I forgot about until I was reading the wiki page just now. The points themselves would probably just be power=pole.

Looks great! If you can tell from the imagery, it's a good idea to add some kind of tag to the nodes, too, to indicate what kind of utility pole / structure they are.

No worries! It wasn't too difficult to fix.

Done! From recent imagery I'd call a few of them medium, but the rest sparse.

D'oh! You're absolutely right, it should have been. The correct tag slipped my mind at the time. I have fixed these. Thanks!

Thanks for adding the different wings of the school. However, adding a feature with "area=yes" on it is generally not very useful unless it includes other tags. In this case, you could split the school feature and add these wing designations as a ref tag, or else add building_part features inside of the main building feature.

This is a residential area, and is seems very doubtful that JNS Glass is actually operating here. Can you please elaborate on why you think this feature should be here?

US 30 and 34 had a bunch of issues. 30 is fixed now, though, and I'll probably work through 34 today.
Sounds like they were broken before you got to them, then. The curse of being the last modifier, I suppose.

It's possible they were broken before you got to them, too, I didn't do a deep dive on the history. It just seemed similar to something I did in the past.

Nice to see all the lane attributes getting added, but are you by chance loading the features w/ an Overpass query? I ask because a bunch of route relations whose member ways you edited got broken, and I have done that very same thing with lane tagging and sparse editing in JOSM.
There's a way to modify your query to tell it to "recurse up relations" and get any relations that the downloaded features belong to, which would avoid this sort of thing.

What was the conflation process, exactly? Oswego, IL, for example, has 4 existing fire stations, all of them in OSM already, and none in the location imported by this changeset. Aurora, IL also had a duplicated station node, and that's just things within a few miles of me. I have to assume with a 2-changeset country-spanning import like this, there are going to be a lot of similar situations.

I get that, and sometimes that's the case. In my opinion, the business is not the building, it just happens to be using the building. Handling business entities as areas introduces a lot of complexity and arbitrariness.
To pick two examples outs of this changeset: suppose I am out in the Menards lumberyard area, or eating at the Chick-fil-A outdoor seating. Have I left the "place of business"? Not really, no. But how do we map that out? Does it stop at the parking lot, or include that, too? Are we just mapping parcels at that point?
It's worth pointing out that there's no rule that a business area has to correspond to a building. Mapping the "place of business" as an area independent of building features is actually how some mappers are addressing multi-business buildings like malls.
It doesn't help that iD has `building=yes` built into a lot of the business area presets.
It's OSM, so, y'know, do whatever you want! I just feel that maintaining businesses as POIs is clearer, easier to maintain, and sidesteps the entire issue of "how many businesses are in the building" and "does the business operate outside of the building".
Final point: keep in mind that having one POI just means there's one POI *mapped*. The Target near me has an optical store, a Starbucks, and a CVS inside, each operating independently. Or in downtown Yorkville, many of the businesses are just the first floor, with apartments above. To say the building itself is the business is inaccurate. But a point that says "this business is here", that's correct!

Hello, fellow mapper! Thanks for doing some much-needed cleaning in the area.

Is there a particular reason to merge business POIs into the footprint geometry?

Looks great! Thanks for adding this kind of local knowledge to the map!
Just a heads up, though: you (probably unintentionally) edited a boundary feature. In iD, you can go into the settings and turn those features off to avoid accidentally snapping to / moving them.