# Restart recording chapter guide

Environment for every chapter: Linux web app, Chromium, dark theme, 1440 × 1000 CSS viewport at 2× scale, identical privacy crop. Each side uses its own unmodified worktree, server and synthetic database.

Each case first shows an unfinished delegated-result delivery with the named output. The server then restarts. In the after-restart chapters, compare the repeated “Check synthetic result” notification, not the separate ordinary restart notice. The no-output row is a correct retry on both commits.

| Output before cancellation | Base before restart | Base after restart | Head before restart | Head after restart |
|---|---:|---:|---:|---:|
| answer | 0:04 | 5:04 | 0:12 | 5:52 |
| reasoning | 0:12 | 2:51 | 0:22 | 3:14 |
| dynamic_tool | 0:21 | 2:59 | 0:30 | 3:22 |
| command_execution | 0:31 | 3:06 | 0:38 | 3:30 |
| file_search | 0:38 | 3:13 | 0:48 | 3:38 |
| web_search | 0:46 | 3:19 | 0:56 | 3:46 |
| file_change | 1:07 | 4:10 | 1:15 | 4:04 |
| todo_list | 1:16 | 4:17 | 1:24 | 4:14 |
| proposed_plan | 1:25 | 4:25 | 1:32 | 4:24 |
| subagent | 1:33 | 4:33 | 1:39 | 4:33 |
| user_input_request | 1:41 | 4:39 | 1:47 | 5:02 |
| approval_request | 1:45 | 4:46 | 1:55 | 5:30 |
| noout | 1:55 | 4:55 | 2:05 | 5:42 |

The recordings run through all cases before restart, restart the server, then revisit all cases. Navigation/loading frames remain in the videos. Chapters point to rendered states. The answer case is revisited at the end.

Base: all twelve output cases repeat the same completion after restart. Head: each retains one completion. The no-output control shows its second notification on both sides because that delivery is an expected retry.