{# TRAIL: one session, read top to bottom as a story a newcomer can follow. Three sections, in the order the IBM "rogue agent" framing names them: What it was asked (INPUTS) -> the request + what the agent knew What it did (DECISIONS) -> replay / trace / turn timing / replay tree How it ended (OUTCOME) -> verdict, quality score, git, spend The wrapper id MUST stay `page-trail` (template stem = tab id, #5476). Renderers are REUSED, not copied: static/js/trail.js re-parents the existing #transcript-viewer / #trace-detail / #ta-detail nodes into the hosts below while this page is open and puts them back on leave, so the transcript replay, span waterfall and turn waterfall are the very same code paths the Sessions / Tracing / Turn anatomy tabs run. #}
Opening the trail…
1

What it was asked

The request that started this session, and what the agent knew going in.
The request
Loading...
What the agent knew
Loading...
2

What it did

Every step, in order. Replay the conversation, or open the timing and trace views.
3

How it ended

Did the result match the request, and what did it cost.
Verdict
Loading...
Quality score
Loading...
Spend and time
Loading...
Code it produced
Loading...