The test expected "esc" (from the status bar) after matching
"direct open seed" (the chat content). Both strings appear in
the same initial PTY render but their relative byte order
depends on whether async title generation completes before the
first frame: sometimes the seed text is in the title bar
(before the status bar) and sometimes it is in the content area
(after). ExpectMatchContext consumes all output up to its match,
so the second expect could never see text that appeared earlier
in the stream.

Remove the separate "esc" expect. The seed text alone proves we
are in the chat view, and pressing esc + expecting "enter: open"
confirms navigation back to the list.