Resolve TUI session metadata and count lookups against the selected conversation row instead of grouping by bare session_id. Topic-suffixed session filenames now prefer an exact session_key match and only then fall back to the normalized bare session_id, which restores conv_id, session key, summary count, and file count for Telegram topic sessions while preserving non-topic behavior. Reuse the same resolution path for single-session conversation lookups so summaries/files/context drill-downs follow the same normalization.

Regeneration-Prompt: |
  Fix the lossless-claw TUI bug where Telegram topic session files on disk are named like <session-id>-topic-<n> but LCM stores the bare runtime session_id and the topic identity separately in session_key. Keep the patch tight in tui/data.go and related tests. Preserve existing behavior for non-topic sessions. Resolve each visible session entry to a concrete conversation row first, preferring an exact session_key match for topic-suffixed filenames and otherwise falling back to the normalized bare session_id, then load summary/file counts by conversation_id so multiple topic rows sharing one bare session_id do not collapse together. Add regression coverage showing a topic session file now gets the right session key, conv_id, summary count, file count, and single-session lookup behavior.