Keep run, session and agent IDs in traces on newer FastAPI

FastAPI 0.142.0 starts its own OpenTelemetry tracing once a global tracer provider exists, and AgentOS(tracing=True) installs one. Each run became a child of the request span, and the stored trace took its name from the first span to finish, FastAPI's dependency span, with its run, session and agent IDs left empty. A stored trace from an earlier release read name='fastapi.dependencies' run_id=None session_id=None agent_id=None.

No. Those stored traces keep the old name and empty context. Traces recorded after the upgrade carry the name and identifiers of the Agno run.

A span you create inside a tool during a run stays in the trace. A top-level span outside any Agno run is dropped from the Agno database once setup_tracing() filters the provider.

AgentOS opts out only on the app it builds, with tracing=True, on a FastAPI version that accepts telemetry, and when Agno installed the tracer provider. An app without tracing=True or with its own provider keeps FastAPI request spans, and a custom base_app keeps them too while the Agno filter holds them out of the Agno database.