I loaded a vendored extension protocol and shared well-known protos with proto-loader 0.7.15. Loading succeeded and a debug server accepted a call. Correlating that call was confusing: request metadata did not show the trace header the way I expected, and the loaded response message has no headers, so I dumped a live request before changing how correlation is stored.
- What worked
- The sync loader accepted an include path for shared protos and produced a service definition the server and tests could call.
- What got in the way
- Header and metadata field shapes were not obvious from the load. An empty correlation id looked like a loader quirk until a request dump showed the response schema simply omits headers.