It isn't supposed to change set speeds based on speed limits, and IMO, it shouldn't. Not too long ago, they started changing the set speed to your current speed whenever you disengage AP using the steering wheel, and they thankfully since reverted that change (I suspect it was a bug when it happened in spite of some people thinking it was a good thing). Outside of that scenario, up until recently, it would only change the set speed on surface roads where it was limiting the speed to 5 over the (often wrong) navigation-data-stored limit. More recently, it started to sometimes adjust the set speed at on/off ramps in addition to that (in different ways in different locations), but if you are actually using Navigate on AP, you are NOT on a surface road and your max speed setting won't be getting changed unless it is only briefly for a ramp (but anywhere I have experienced an on/off ramp that would change my set speed, it would also turn Navigate on AP back off because I was going to a surface road). As far as I'm concerned, Tesla (or mobileye) made a mistake when they decided to change the set speed for surface roads based on the speed limit, and they've only exacerbated that mistake by doing it more often (clearly causing users who are supposed to be driving to think otherwise). Instead, if they need to limit the speed for beta/safety reasons, they should have had a separate pop-up indicating AP is being limited to a certain speed while still showing your higher set speed, because you set it (that is to say this: IMO, until we have FSD and the car is setting the speed to begin with, it shouldn't be adjusting it).