Merge branch 'DOC-1901-document-feature-adp-execution-logs-ui-package-1' into adp-pkg1

# Conflicts:
#	modules/ROOT/nav.adoc

Author: paulohtb6

modules/ROOT/nav.adoc

@@ -93,7 +93,11 @@
 **** xref:ai-agents:mcp/local/configuration.adoc[Configure]
 ** xref:ai-agents:observability/index.adoc[Transcripts]
 *** xref:ai-agents:observability/concepts.adoc[Concepts]
-** xref:ai-agents:agents/index.adoc[Agents]
+*** xref:ai-agents:observability/view-transcripts.adoc[View Transcripts]
+*** xref:ai-agents:observability/ingest-custom-traces.adoc[Ingest Traces from Custom Agents] 
+
+* xref:develop:connect/about.adoc[Redpanda Connect]
+** xref:develop:connect/connect-quickstart.adoc[Quickstart]
 ** xref:develop:connect/configuration/about.adoc[]
 *** xref:develop:connect/configuration/batching.adoc[]
 *** xref:develop:connect/configuration/windowed_processing.adoc[]

modules/ai-agents/pages/observability/concepts.adoc

@@ -316,7 +316,7 @@ The `events` array captures what happened and when. Use `timeUnixNano` to see ex
 [[opentelemetry-traces-topic]]
 == How Redpanda stores trace data
 
-The `redpanda.otel_traces` topic stores OpenTelemetry spans using Redpanda's Schema Registry wire format with a custom Protobuf schema named `redpanda.otel_traces-value` that closely follows the https://opentelemetry.io/docs/specs/otel/protocol/[OpenTelemetry Protocol (OTLP)^] specification. This schema is automatically registered in the Schema Registry with the topic, enabling clients to deserialize trace data correctly.
+The `redpanda.otel_traces` topic stores OpenTelemetry spans using Redpanda's Schema Registry wire format, with a custom Protobuf schema named `redpanda.otel_traces-value` that follows the https://opentelemetry.io/docs/specs/otel/protocol/[OpenTelemetry Protocol (OTLP)^] specification. Spans include attributes following OpenTelemetry https://opentelemetry.io/docs/specs/semconv/gen-ai/[semantic conventions for generative AI^], such as `gen_ai.operation.name` and `gen_ai.conversation.id`. The schema is automatically registered in the Schema Registry with the topic, so Kafka clients can consume and deserialize trace data correctly.
 
 Redpanda manages both the `redpanda.otel_traces` topic and its schema automatically. If you delete either the topic or the schema, they are recreated automatically. However, deleting the topic permanently deletes all trace data, and the topic comes back empty. Do not produce your own data to this topic. It is reserved for OpenTelemetry traces.