j|%SrSSKJr SSKJr SSKJrJrJr SSK J r \"SSS9r S \ S'Sq S \ S 'SS jrSS jrg)aZThe LangSmith tracer the playground's agents share. The extraction agents are classes and each holds its own `LangSmithTracer`. The playground's agents are module-level functions with no instance to hold one, so this module owns the single tracer they all open runs on. Most call sites wrap one pydantic-ai `Agent.run` or `Agent.run_stream` the way the extraction agents do: open the run with the prompt as messages, set the assistant message and usage on exit. The ranker in `ranking.py` opens one run per pass around many TypeSafe calls and records their combined outputs. Document identity is not an argument the answer functions take, so the route that knows it sets `document_key` for the request and each run copies it into its metadata. Same no-op contract as the extraction tracer: with `TRACE_TO_LANGSMITH` unset nothing here reaches the network. ) annotations) ContextVar)AnyDictOptional)LangSmithTracer document_keyN)defaultzContextVar[Optional[str]]zOptional[LangSmithTracer]_tracerc.[c [SS9q[$)zBThe process-wide tracer, built on first use so settings are final.zquber-playground)run_name)r r6/home/mande/repo/quber/src/quber/playground/tracing.pytracerrs!+=> NrcD[R5nU(aSU0$0$)z6The document key of the request in flight, or nothing.doc_key)r get)docs r run_metadatar's"    C"Is **r)returnr)rzDict[str, Any])__doc__ __future__r contextvarsrtypingrrrquber.agents.langsmith_tracerrr __annotations__r rrrrrrsD #"&&9+5^T*R 'R%) ")+r