Replace the shared getOperationName() function with per-provider method registries that map API paths to their operation name and streaming behavior. This explicitly couples the instrumented methods and necessary metadata in one place instead of having convoluted substring matching in multiple places that can be quite hard to reason about.
Note
The pull request "ref(core): Introduce instrumented method registry for AI integrations" was created by @nicohrubec but did not reference an issue. Therefore this issue was created for better visibility in external tools like Linear.
Replace the shared
getOperationName()function with per-provider method registries that map API paths to their operation name and streaming behavior. This explicitly couples the instrumented methods and necessary metadata in one place instead of having convoluted substring matching in multiple places that can be quite hard to reason about.