F23-MT: Yes
Rationale
The selected radio endpoint can change relay neighborhoods while keeping its node identity and confirmed public key. Directed-message routing learns a next hop but falls back to managed flooding when that route stops working. The pinned NextHopRouter retransmission path clears the next-hop preference and resends the retained packet through FloodingRouter on its final attempt. Thus an in-flight message can reach the same endpoint through its new neighborhood without a new peer relationship. This covers radio mobility inside a reachable mesh with compatible radio/channel settings, not continuous media, unlimited retry or delivery through a prolonged partition.
Assessment method
Primary documentation and bounded selected-profile inference; no execution
Source context
Meshtastic mesh algorithm and pinned next-hop retransmission implementation
Outstanding qualification
Move the pinned Alpha radio endpoint out of range of its learned next hop while a direct message awaits acknowledgement. Verify the same message ID, destination and verified key through flood fallback. Measure airtime, duplicates and delivery before retry exhaustion; no production or scale qualification is inferred.