Problem

Diagnostics already has the right ingredients for slow-run analysis, especially per-tool latency and context pressure. The layout still reads as separate boxes rather than one slow-path explanation.

Current screenshot:

Expected direction

• Add a clear slow-run summary at the top.
• Put slow tool ranking and long-gap evidence above less urgent sections.
• Show which signal most likely explains the slowdown: tool latency, hanging gap, retry loop, large params, or context pressure.
• Consider a simple timeline or ordered "slow path" list.

Validation notes

Captured from a real local run, not demo data.