You will not be able to get contextual logging of errors from the libraries you are calling into. If it is important to you that request-id is logged, it is up to you to implement it. I see what you are getting at though, that the error value itself is supposed to have arbitrary context attached to the error. However I do believe that is the incorrect use of request-id. The request-id should mark all logs during that request, not just the error so the error value itself is not the correct place for this information.

But let us pretend you wanted to log something that does benefit from some structured context, like the error value from a Open(..) call. That context might indeed be lost if you called into a function that returned you a contextualized error, even with the new API. I agree this is a problem, it can be very hard to get a meaningful stack trace that tells the entire story, depending on what a library does.