In the `on_response` hook, `update_ai_client_span(span, response)` is called on line 71 before `span.__exit__(None, None, None)` on line 72. If `update_ai_client_span` raises an exception (e.g., due to malformed response data or an internal error in `_set_usage_data`), the span that was opened via `span.__enter__()` in `on_request` will never be closed. This could lead to span leaks and incorrect tracing data. The `on_error` handler correctly wraps its `span.__exit__` call in `capture_internal_exceptions()`, but `on_response` doesn't follow this defensive pattern.

The condition `if not metadata:` on lines 115 and 164 treats empty dictionaries `{}` as falsy and overwrites them. This is inconsistent with the `patched_init` in `__init__.py` which uses `if metadata is None`. If a user explicitly passes `metadata={}`, it will be unexpectedly replaced with `{"_sentry_span": None}`, potentially losing the shared reference intended by `patched_init`.

The condition `if not metadata:` on lines 115 and 164 treats empty dictionaries `{}` as falsy and overwrites them. This is inconsistent with the `patched_init` in `__init__.py` which uses `if metadata is None`. If a user explicitly passes `metadata={}`, it will be unexpectedly replaced with `{"_sentry_span": None}`, potentially losing the shared reference intended by `patched_init`.