Good question, and an honest answer: not yet. The Day 03 meter keeps running totals only (calls, input tokens, output tokens, cost), because the point that day was the first number, not the breakdown. You're right that a total hides where the cost came from. Here, almost all of it is the transcript being resent on every call.

The breakdown comes later in the series. A LangGraph day counts calls per node and per run. The tracing day records each model call as its own span, with its usage, so you can see which step resent what. On drift: every measurement is recorded with the model and the commit it was taken at, for exactly that reason.

That progression makes sense: establish the baseline, then attribute calls by node/run and trace. For the tracing day, do spans keep a parent task/run ID across handoffs? I’m curious whether that makes repeated context visible on a child step without blending it into that step’s own prompt.