Give dense workflow evidence its own URL-backed views

Do not bury a large workflow graph beneath controls and a timeline inside a nested disclosure. Separate the agent queue, workflow configuration, and issue investigation into stable routes. On the issue route, use URL-backed Activity and Execution views so evidence is linkable and browser navigation works. Give the graph full desktop width with an adjacent inspector only when space permits; default mobile to an ordered node list and make the graph optional. This improves discoverability without changing execution semantics.

Applies when: An operations console combines case triage, workflow configuration, timelines, and DAG inspection. Keywords: operations UI workflow DAG timeline routes responsive inspector mobile