Stack tool-call rows, hard-swap to a streaming brief, then autoscroll as sections fill in

What the source does

White app view with the user's short question as a small bubble top-right and a presenter PiP beneath it. Under 'Worked for 12s' an activity log grows one row every 2-3 frames (local 0 to 13): alternating dark task lines and small grey 'searched...' sub-rows. At ~14 (master 410) the whole log is replaced by the answer: a 30 px heading fades in, a grey 'Top line' callout and a 'Sources reviewed' table follow, and the table's five rows arrive at ~3-frame intervals (18-30). 'Do today' with three numbered items lands around 32-37, then from ~38 (master 434) the page scrolls up by about 420 px while a 'Meetings' table appears; a second scroll around 60-76 brings later meeting rows into view.

Two-stage response arrival: a log list populates row by row, is swapped in one frame for the formatted answer, and the answer streams section by section while the container autoscrolls to keep the newest rows in view.

Phase notes

1. Frame 0 — Activity log rows stacking
2. Frame 14 — Log replaced by heading
3. Frame 18 — Sources table rows stream in
4. Frame 32 — Do today list
5. Frame 38 — First autoscroll, Meetings table
6. Frame 60 — Second autoscroll, later meeting rows

Use this example

1. Watch the source and draft at normal speed. Compare the order of actions, the held states, and the transition into the result.
2. Download the project and read its README before changing inputs. The package includes its implementation and declared dependencies.
3. Replace the sample content through the package's documented input or content builder. Keep source footage in the research comparison.
4. Render your adaptation and inspect text fit, framing, intermediate states, and entry and exit frames.

Recorded limits

• Visual fidelity is an authored draft judgement from sampled source frames; no independent blind review or native Resolve execution.

Inspect the original verification record ↗