Documents recreate connections to nodes that no longer have that port

[tobyspark]

Save a document with a node with a connected port. Change the node interface to remove that port, rebuild, launch. Document shows the node still having the port, because the document load “reconnected” it. This is really only a dev issue, but it should not happen.

Now we can throw, we should probably do that here (recoverable).

[vade]

yea, this is an issue with tension between how we serialize graphs and what owns ground truth on the plugin.

i feel like the node registry setup should be revisited - and the serialization / port / param UUID wiring needs re - looking at. This is hinted at in #67

[tobyspark]

I have a proper write-up of this incoming, having just done a surface-level fix and realised its symptom not cause.

[vade]

Request human language synopsis not LLM formatted super verbose write up hah :D

[tobyspark]

I now realised this is a duplicate of #67, but as that’s just been closed we’ll continue here.