What
Looking up another session or agent by name used to look identical whether the search was complete or cut short. Listings and refusals now say so explicitly, so "no agent by that name" no longer implies the peer does not exist.
Details
- Listings append "(session list too long to fetch completely — sessions beyond the first pages are missing from this listing)".
- Not-found refusals append "Your session list was too long to check completely, so a session by that name may exist beyond what was searched."
- Ambiguous matches append "your session list was too long to check completely", and same-name warnings append "; your session list was too long to check completely, so a same-named session beyond what was searched would not have been seen".
- A truncation flag (
searchTruncated) is carried from the cloud and bridge session caches through name resolution; a pinned send target is no longer reported as stale when truncation could explain the miss, andsend_message_prefix_matchtelemetry gainssearch_truncated. - A cloud session list that times out is now reported as
"timeout"rather than a generic fetch failure.
Evidence
; your session list was too long to check completely, so a same-named session beyond what was searched would not have been seen, searchTruncated, your session list was too long to check completely, Your session list was too long to check completely, so a session by that name may exist beyond what was searched., session list too long to fetch completely
Strings lifted out of the shipped bundle, so the claim above can be checked against them.