A performance trace is most useful when it begins with a specific complaint. In this recording, a settings panel takes long enough to respond that the click feels uncertain. The network is idle. The delay lives on the main thread.
The session starts with a fresh recording, marks the input event, and follows the resulting task into application code. After splitting one synchronous calculation, the trace shows a paint between chunks and the control responds sooner.
The video source is temporary Phase 1 data. The page copy and chapters are here to test the complete video entry shape without treating the video as a bare embed.