Agreed - I've added highway:construction=primary_link to indicate again the status once construction is complete.

The way you had this mapped gives the impression that the busway is already open, which it isn't. I've added/amended tags to show that it is still under construction, but I don't know if any parts are actually (either in the way object I updated, or in the parts further north). Are you able to check how much of the busway is still under construction, and fix any other incorrect tags? If necessary, you may need to split some existing ways.

You shouldn't add descriptions such as 'planned' or 'construction' to names - this may 'clarify' to a human reader, but OpenStreetMap data is also used algorithmically (e.g. by journey planners). You should instead use construction tags (or other appropiate lifecycle tags) - read highway=construction and osm.wiki/Category:Lifecycle for more information.

I agree that you aren't the original source; however, all the ones I'd noticed where ones where you'd changed the tag barrier=fence to barrier=hedge, without noticing the issue.

I just discovered the tunnel issue (the level crossings being the giveaway) too - this could have been fixed a week ago when you first discovered the mistake. I've removed the incorrect tunnel/layer tags, but I don't have enough information to work out what needs to be done with the Yox River crossing, so you'll have to fix that yourself.

There are a number of areas east of Hardwick that you have tagged as barrier=hedge and landuse=farmland. There are a couple of issues with this. Firstly, the use of a 'landuse' tag suggests that this way should be treated as an area, with the result that users of the data might incorrectly assume the whole field is a hedge (see e.g. the default renderer on openstreetmap.org at zoom levels 16 and above). Secondly, by tagging this on multiple adjoining fields (setting aside the area issue), you are effectively mapping the same hedge multiple times.
I'm wondering if you might be able to resolve these tagging issues - my suggestion would be to remove barrier=hedge from the fields and tag the hedges on separate non-overlapping (and probably shorter) ways.
I realise this issue partly predates your changeset (where the fields were tagged as fences instead of hedges). However, as the last person to have mapped these fields, and since I've never visited them myself, you are probably better placed than me to work out how to tag sections of the hedge appropriately (including knowing whether there should be any gaps in the hedges).

Since you've adjusted the roundabout exit, you should probably adjust the entrance under construction to a more accurate line as well (compare this to the nearby Girton West roundabout)

Yes, I'm aware of that announcement (though I saw it on Facebook instead). However, plans do sometimes change, and the reality on the ground is clearly different. In a comment on their post they confirmed to me that:
"the information originally shared was our intended outcome. However, we then decided to keep the slip road open due to safety reasons. All traffic heading out on A1307 Huntingdon Road is being signposted to join the A14 at the new slip road."
"Safety reasons" apparently means avoiding a risk of people trying to get to the A14 and going the wrong way down the exit slip.

This is the second time you've set the slip road as oneway - before repeating a change that someone else (me) reverted, you should check what their sources are and whether the reversion was correct. In this case my edits to 'reopen' the slip road and make the link twoway clearly state that the source was a 'survey' - that means I was actually physically present and saw that the slip road hadn't been closed. Furthermore, I happened to be there again at the exact time you made this change to mark the slip road as closed again, and I can confirm that it was definitely still open at the time. I've reverted this changeset; if you still think that the slip road is permanently closed, then please discuss this further with me.

Can you try to mention your sources explicitly? I mistakenly reverted a similar changeset recently because it gave the impression of being based on out-of-date imagery and nothing else; I put it back to an alignment that looked consistent with the most recent Maxar Premium imagery, but was based upon a misreading of that imagery (as I've since discovered in-person).

I've had another look at the both the plans and the current state of the road, and it looks like I was probably misreading the aerial imagery. Greyseal18 has put this back roughly how you put it here; apologies for my mistaken reversion. However, it still isn't clear to me how you knew the correct alignment - could you try to be more explicit about sources in the future to avoid unnecessary reversion?

Those roads look like trunk links to me - there is no way of driving along them without either coming from or going to the trunk road, and no property accesses or anything like that. Technically I think a cyclist could use those links, but since a parallel cycle route exists I don't think that should prevent it being marked as trunk_link.
I also think that the section of Leaf Lane north of Black Prince Avenue is mismapped - Mapbox and Esri World imagery both seem to show the central white line continuing round from Black Prince Avenue, implying that Leaf Lane is two-way for the stretch adjacent to numbers 87 and 89. Beyond that point I think it becomes a trunk_link too.

On what basis did you make this change? The changeset comment says that you used Bing imagery, but this provides no evidence for this alignment. More recent imagery is available from Maxar, and this was mentioned when I originally corrected the alignment of the road in changeset/71993430. I've reverted this changeset, since it contradicts the evidence in the Maxar Premium imagery, and the changeset comments suggest no firmer basis for making this change than "having the carriageways adjacent on the map looks neater".

The combination of this change and the previous change has created a new way that replaces the original way for the start of the history - this effectively hides most of the history of that way. In future, when merging ways, try to keep the one with the most informative history - especially if the other one was one you just created.
Also, I have no idea why you set part of the A1307 slip road as 'trunk' instead of 'trunk_link' - it seems obviously wrong to me.

You've made a few mistakes. You've left the old J31 slip road marked as open, and you've broken all the Citi 5 bus relations. Admittedly, I'm not 100% sure what the new outbound routing will be, but I could at least make a reasonable guess and check tomorrow. (For the eastbound changes, I had intended to just revert my previous edit to save the hassle of reediting the inbound bus routes.)
Also, I don't think I agree with editing the map 48 hours before reality (or more if plans change).

The opening of the new slip road was announced in https://www.facebook.com/A14C2H/photos/a.238494069903679/693911841028564/. Based on comments and an educated guess, I would expect the temporary slip road to use a bit of the new main carriageway as well, but since I don't yet know how much, I just drew it as leaving the existing carriageway at the latest possible moment to meet the eventual permanent slip road.

This was drawn mostly from what I saw when I visited the sight previously, along with some educated guesses, so anything derived from ariel imagery will be much better. However, with both the new WB carriageway and the first of the two exit slip roads both being constructed to the south of the original A14 route here, I don't think it is possible to deduce the alignment from the Maxar imagery, which is still relatively old at this point. I intend to revisit this area during the next week to get a better look (although I am limited in what I can safely access without a motor vehicle) - I expect combining a site visit with the Maxar imagery will give better results that using either one alone.

Are you sure? I can't find anything on Twitter to suggest it will be single carriageway, but I do find this tweet from just before your changeset which has a diagram showing a dual carriageway here.
https://twitter.com/A14C2H/status/1092403677166477312

I don't understand this edit. You claim to be using Bing as a source to improve the mapping of an underground railway - I can see how this could work for the cuttings (although you should be careful to avoid introducing paralax errors), but parts of your edits involve tunnels that wouldn't be visible in satellite imagery. Can you explain how you made these edits?
You have also made a couple of clear mistakes in this. Firstly you've added ways 654075521-654075533, which I presume you added temporarily to preserve track spacing - these should be deleted. You've also distorted some buildings by moving nodes that form part of their boundaries - you needed to split these nodes into separate nodes for the building and railway, and restore the building node to the correct location. (These nodes shouldn't have been shared by the railway and building in the first place, but you should watch out for mistakes like that when making updates.)

I've now read more of the Highways England Strategic Road Network Initial Report, and it seems that I was previously misinterpreting it. According to the report (P58-59), the highest classifications of roads will be "Smart Motorway", "Motorway", "Expressway" and "All Purpose Trunk Road", with expressways differing from smart motorways only in the typical number of lanes (2 instead of 4) and the typical designation (A*(M) instead of M*). I had previously read only P78, from which I incorrectly inferred that 'expressway' referred to only phases 1-3 in that description, whereas I now believe those are pre-expressway.
(Since I presume you've already read that document, I write this more for the benefit of anyone else reading this.)

Can you provide some evidence of this? The only documents I can find online relating to this suggest that it might become an 'expressway', which is not (initially, at least) the same thing.