[unRekable]

Stacked on #55 — the search-pane work; merge that first. Against feat/search-pane-scopes so only this slice shows.

What

The search pane's result rows take the anatomy docs/product/05-navigation.md §5 draws for them: a context line of the network's mark, the Space the conversation sits in before the conversation's name, and the date at the end — the match stays emphasised below.

Two refinements from review of #55:

• "This conversation" names the conversation open now: switching conversation re-asks the cache, the old hits staying up until the answer lands.
• A page remade since an ask (pane closed and opened again within one round-trip) no longer takes that older ask's answer: the stale guard takes the words and the scope with the count.

Tests

cargo check -p tinyclient --features gui clean, cargo test -p tinyclient --features gui 350 passed.

[itz4blitz]

The context line looks right, and the follow-the-open-conversation and stale-guard fixes from #55 are good. A few things:

1. This inherits #55's switcher bug: the "Search messages" row fills the field with set_text, which emits nothing, so nothing is asked (side.rs:439 here). See the #55 review.
2. The picked row survives a conversation switch. The re-ask deliberately keeps picked (side.rs:232, :576), and the answer handler only sets page.hits. Once the new answer lands, the lit row and Enter's target are a different message the user never chose. If the index is out of range, Enter falls through to the network ask in #58. Please clear picked when the scope's target changes, or when an answer for a different target lands.
3. Only the Conversation scope follows a switch here (:241), so This space stays on the old Space. #58 fixes that, so this is fine as a stack.
4. held() (:594, :975) scans the sidebar rows and every tree once per distinct hit conversation per frame, plus open_with_space every frame. Resolving the context line once when an answer lands would keep render cheap with many hits.
5. There are no tests for the follow/re-ask behaviour or the context line.