a wire protocol for named context patches: you'd do better not writing your own wire serialization format, and instead adopting an existing transport: websockets, stomp, and MQTT all strike me as sufficiently stupid simple & end to end enough, or anything from thrift to zmq to flume for transport would be slightly more inter-linkable than your "length/json-payload" ad-hocracy.

it's JS but you might enjoy node-webworker, which uses websockets to implement inter-Node.js message passing: your specific case is debugger being an outbound messaging port, emitting context programmatically.