MCP helper processes declaring a newer protocol are parked on restore, awaiting a v2 runtime.
Saved MCP task sidecars tagged with a newer 'sep2663' protocol are skipped by the current restore path with a log saying they need a v2 runtime that isn't the one restoring them.
What's wrong with this entry?
Restoring MCP task helper processes from a saved session now checks which protocol each one declared. Entries on the newer sep2663 protocol are skipped by the older restore path with a log saying they need the v2 runtime.
- Any protocol value that is not recognised is parked with an error-level log rather than restored blindly.
- Both restore paths in the bundle carry the guard.
sep2663
Strings lifted out of the shipped bundle, so the claim above can be checked against them.