A failed local agent lookup is now reported as a failure, not as "no such agent".
What's wrong with this entry?
Sending a message to another agent already distinguished the cloud directory and the bridge being unreachable. A third case, the local agent registry failing to answer, is now tracked and shown in the "not sent" line, so a lookup failure is no longer reported as if no such agent existed.
- The new flag is
localUnavailable, carried through routing, suggestion suppression and the message shown to you. - Listing peers similarly gained a
cloudListFailedflag.
localUnavailable
Strings lifted out of the shipped bundle, so the claim above can be checked against them.