fixes

Author: lmolkova

instrumentation-genai/opentelemetry-instrumentation-openai-v2/CHANGELOG.md

@@ -21,6 +21,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   ([#4325](https://github.com/open-telemetry/opentelemetry-python-contrib/pull/4325))
 - Add strongly typed Responses API extractors with validation and content
   extraction improvements
+  ([#4337](https://github.com/open-telemetry/opentelemetry-python-contrib/pull/4337))
 - Add completion hook support.
   ([#4315](https://github.com/open-telemetry/opentelemetry-python-contrib/pull/4315))
 - Fix `response_format` handling: map `json_object`/`json_schema` to `json` output type.

util/opentelemetry-util-genai/AGENTS.md

@@ -15,26 +15,7 @@ Use the appropriate semconv attribute modules — do not hardcode attribute name
 - `error.*` attributes: `opentelemetry.semconv.attributes.error_attributes`
 - Other namespaces: use the corresponding module from `opentelemetry.semconv`
 
-## 2. TelemetryHandler Initialization
-
-Construct `TelemetryHandler` once per instrumentor, passing the OTel providers and the
-completion hook. Always resolve the hook with `kwargs.get("completion_hook") or
-load_completion_hook()` so callers can inject a hook directly, and fall back to the
-entry-point-loaded hook configured via `OTEL_INSTRUMENTATION_GENAI_COMPLETION_HOOK`.
-
-```python
-from opentelemetry.util.genai.completion_hook import load_completion_hook
-from opentelemetry.util.genai.handler import TelemetryHandler
-
-handler = TelemetryHandler(
-    tracer_provider=tracer_provider,
-    meter_provider=meter_provider,
-    logger_provider=logger_provider,
-    completion_hook=kwargs.get("completion_hook") or load_completion_hook(),
-)
-```
-
-## 3. Invocation Lifecycle Pattern
+## 2. Invocation Lifecycle Pattern
 
 Every new operation type must follow this pattern:
 
@@ -67,21 +48,21 @@ Context manager equivalents (`handler.inference()`, `handler.embedding()`, `hand
 etc.) in instrumentation or production code — direct construction skips span creation and context
 propagation, so all telemetry calls become no-ops. Always use `handler.start_*()`.
 
-## 4. Exception Handling
+## 3. Exception Handling
 
 - Do not add `raise {Error}` statements to `handler.py` or `types.py` — validation belongs in
   tests and callers, not telemetry internals.
 - When catching exceptions from the underlying library to record telemetry, always re-raise
   the original exception unmodified.
 
-## 5. Documentation
+## 4. Documentation
 
 - Docstrings for invocation types and span/event helpers must include a link to the
   corresponding operation in the semconv spec.
 - When adding or changing attributes, update the docstring to describe what is set and under
   what conditions (e.g., "set only when `server_address` is provided").
 
-## 6. Tests
+## 5. Tests
 
 - Every new operation type or attribute change must have tests verifying the exact attribute
   names and values produced, checked against the semconv spec.
@@ -90,7 +71,7 @@ propagation, so all telemetry calls become no-ops. Always use `handler.start_*()
 - Tests live in `tests/` — follow existing patterns there.
 - Don't call internal API in tests when the public API is available.
 
-## 7. Python API Conventions
+## 6. Python API Conventions
 
 - Mark private modules with an underscore.
 - Objects inside of a private module should be prefixed with underscopre if they