[TechNomadCode]

Slice 26 of the plan: the second half of the README video's motion (slice 25 was the first).

• Words: a reply's words come in one after another, each rising 4px from a slight blur as it fades in, also when a reply arrives whole, as on staging. Each paragraph, list or table spaces its own words, at most 53ms apart and closer when there are many, so it settles within about half a second; a list's bullets arrive with their first words. Once the words are in, the text is plain again, one text node per run, so tests and screen readers read it as before.
• The fold: when a second search joins, the plain lines draw together and blur out while "Used 2 searches" settles in, growing slightly. The count rolls as before; the triangle turns with the lines' slide, on the shared in-out curve.
• The pop-over: it grows from the name that was clicked, from 92% with a fade on the pop-over spring, and closes the same way; each time it opens, the quote's highlight sweeps across the words. Without overlay (Firefox, Safari) it closes at once; without @starting-style it also opens at once.
• Fixed on the way (on main too): clicking another name while the pop-over was open showed that quote in a pop-over still placed by the first name. It now reopens by the name clicked.

Reduced motion turns all of it off.

Checks (local, Chromium)

• npm run verify: format, lint, typecheck, 587 unit tests, production build
• npm run test:e2e: 83 passed; the new motion tests passed five more runs each
• The scenario tour recorded three times on a production build and read frame by frame: no long animation frames during the tour, including its 840-word answer

Not checked: Safari and Firefox, a phone's real hardware, staging's real model.

src/server and src/lib

No changes, so nothing the model receives changes.