That layer comes from inconsistent OSM data; note how when you get south of AAA Boulevard it becomes DE 7, just like OSM.
Oh bleh. OK so if we go back to the tags in the traffic count data, it's 1 up to 95, then 7 north of 95... but it's also only just 1 immediately south of 95, with 7 having a gap. I could see this being interpreted as 1 ending at 95 there, and 7 just not being shown between 95 and where it leaves 1 because both routes are not shown where there is a concurrency. But this doesn't explicitly mean 1 ends at 95, it could just mean the primary flips from 1 to 7 at 95.
So... yeah need a more conclusive official answer than we've got to change anything I'd say.