{# 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. #}