The `on_response` hook calls `span.__exit__(None, None, None)` at line 72 without any exception handling. If the span's `__enter__()` had failed (after being stored in metadata at line 51), the `__exit__()` call would raise an `AttributeError` because `_context_manager_state` was never set. Unlike the `on_error` hook which wraps the `__exit__()` call with `capture_internal_exceptions()`, `on_response` lacks this protection. This could cause internal SDK errors to propagate to user code.

In `test_context_cleanup_on_error`, the agent is created at line 1190 (`test_agent = get_test_agent()`) BEFORE `sentry_init()` is called at lines 1198-1201. The `PydanticAIIntegration` patches `Agent.__init__` during setup, so agents created before `sentry_init()` won't have the Sentry hooks registered. This differs from other tests like `test_context_cleanup_after_run` where `sentry_init()` is correctly called first. The test may pass but won't actually test the integration's cleanup behavior.