v0.5.42

Highlights

A model call inside a retrieval span is part of that retrieval, not the agent's answer. In the OpenTelemetry GenAI conventions a retrieval span is a retrieval pipeline; a model call the pipeline makes (for example rewriting the user's question into a search query) is its child. Studio now reads that structure, for any target.

Rules and judges

• Model calls nested in a retrieval span are auxiliary: answer rules and the semantic agentic judge's conversation turns never take them as the reply. Before, a query rewrite could be read as an answer (for example a rewrite that returned "No").

Trajectory timeline

• The model call is shown inside its retrieval step, tagged + model call: its input and output first, then the retrieval query and documents, so the step reads in the order it ran. Before, the retrieval row came first and the rewrite looked like a reply.
• Finding and judge links to the model call open that retrieval step.

Verified with a traced RAG target (Helsedirektoratet RAG API emitting invoke_workflow › retrieval › chat) across an 8-scenario audit.