You added layer=-1 to a ton of tunnel=building_passage, but generally, they shouldn't have a layer tag at all, since both the tunnel and building are on the ground level.
tunnel=building_passage

Hi, I was wondering if George Babcock Road itself is private, or if the signs were instead for the property to the south? On East Haddam GIS, it doesn't seem to be on private property (named Dolbia Hill Road there): https://next.axisgis.com/East_HaddamCT/

I see. There are specific guidelines for Connecticut, although I don't necessarily agree with them:
osm.wiki/Connecticut/Highway_classification
Previously I was going by the wiki page for highway=unclassified:
highway=unclassified
which says "Residential roads, primarily for access to properties, should be tagged highway=residential instead". Obviously the road has a number of residences along it, although it's hard to say whether it's primarily used by residents or through traffic. I think the Connecticut default has been to tag/leave them as highway=residential. Minor roads without residences are quite rare here (unlike the UK), although at the same time they aren't exactly dense and suburban, so I see your point.

Why are you changing highway=residential to highway=unclassified (for example, way/659232442). Also why are you changing asphalt to paved?

Why did you replace surface=compacted with surface=unpaved?

Hi, I've noticed in many places you've changed surface=earth or surface=dirt to surface=ground. But according to the wiki, earth/dirt is a specific type of ground; ground can also be grass, sand, clay, etc. So the more specific tags are preferred.
surface=ground

Ah ok, oops!

You changed the name for the entire Yale University relation to "Yale University (West Campus)"

I saw that on the wiki but didn't really vibe with it -- I feel like capped landfills aren't really "abandoned" or even "disused". They're still being used in the sense that they're continuing to hold the waste that was put there, and are probably still monitored and tested regularly. Maybe there should be a specific tag to indicate that it's capped.

I think way/29373850 (Naugatuck River outline) should stop where it meets the Housatonic in Derby? Currently it extends a few miles south. My computer is broken at the moment so I can't fix it very easily :)

I think you're misunderstanding the wiki page. The text is: "Do not use this tag *just* for marking bridges", as in, don't use it for normal bridges that don't have a roof and walls. The tag is still valid for bridges that are both bridges *and* buildings, as it is in this case and all the others you deleted. Otherwise the tag would have been deprecated on the wiki.

Why are you removing building=bridge? This is a wooden covered bridge (with walls).

tracktype=grade1 is generally specifically for paved surfaces. Most of Goat Hill Road for example would probably be best tagged as grade4. See the table here: tracktype=*

Can I suggest returning the name to "Country Club of Woodbridge"? There's a nature reserve / trail system called Racebrook Tract about 1 mile southwest, so it's somewhat confusing. I see the NH Register article that says "Woodbridge recently issued a Request for Proposals to develop the former Country Club of Woodbridge on Racebrook Tract". Perhaps there's a larger collection of properties called Racebrook Tract...so perhaps this abandoned golf course alone shouldn't bear the name alone. Maybe a relation, although the golf course isn't designated open space. Open to your thoughts.

Hi, thanks for adding sidewalks. It would be best however if you could add a separate way for the crossings and tag them as footway=crossing, instead of having a continuous footway=sidewalk. Thanks!
footway=crossing

Gotcha, I didn't realize it was blazed. I went there last year and it kinda just looked like a water tunnel that people snuck through. Seems fine in the name tag I guess.
As for trail names, generally I prefer the CT way of doing it. Of course, many segments of larger trails have their own names, and segments may be part of multiple trails, so having it in the relation only is often the least messy/d.r.y. solution. Of course, the downside is that the default OSM layer doesn't render trail relation names, which is probably why it can be seen as acceptable to do it in other places. Though to me that's kinda borderline "Tagging for the renderer" (see wiki page).

No need to explain, I do the same all the time (roughly aligning trails with strava + garmin), but yeah in this case it was just multiple parallel paths in close proximity, which could have been seen with aerial imagery since there isn't tree cover there. Fixed by adding way/1202683830 if you want to see. Obviously on the heat map that would just show as one big blob, and I'm not sure the garmin is always accurate enough.
Also check out the "CT ECO Shaded Relief" elevation layer -- it can be far more accurate than Strava or modern gps for aligning hiking trails.

Be careful with strava, for example around (41.7923442, -72.7903154) it seems you blindly moved the track from where it was / should be, to where the heat map was the strongest -- though there actually seems to be a parallel path there causing the "heat" that should have been mapped instead (about 25 ft over). Thanks.

For the tunnel under CT 2, is "The Tubes" the official name? Or would it be better to put that under loc_name

Thoughts on making a classification exception for Birch Mountain Road? Feels tertiary. Double yellow and guardrails. (two disconnected sections with Villa Louisa Road in between)