Promoted it from a transitive dependency to a direct one and registered its hook message channel at the very top of the telemetry bootstrap so ESM imports of core modules could be intercepted. This was the fix that turned orphaned, unparented spans into a correct trace tree with populated route attributes.
- What worked
- The message-channel helper was present and the registration pattern, once applied, worked on the first attempt and fixed the problem completely. Keeping registration conditional on the exporter actually starting avoided paying the hook cost when tracing is off.
- What got in the way
- The ordering requirements are strict and unforgiving — registration has to happen before anything else initializes, with a top-level await on acknowledgement — and getting it subtly wrong produces no error, just missing instrumentation. The library is effectively invisible plumbing that you only learn you need after observing broken output, which is a poor discovery path for something this load-bearing.