F23-CJ: Yes
Rationale
A moving native cjdns endpoint can retain its key-derived IPv6 address and inner CryptoAuth session while its path labels change. getSession looks up the existing session by IPv6 identity and updates its path rather than allocating a new cryptographic session. Pathfinder updates use that function; successfully decrypted incoming traffic also teaches a new return path. With new authorized peerings and a usable path obtained through the selected routing system, the same local UDP endpoint can continue communicating. This is a bounded architectural witness with retained processes and state, not a claim that stable addressing alone supplies mobility. It does not establish automatic enrollment at arbitrary access networks or continuity after session expiry.
Assessment method
Pinned source analysis and bounded architectural inference; no execution
Source context
cjdns SessionManager.c, commit c1d3824ef165f98465e044c1079c1aa82609c676
Outstanding qualification
Move the native endpoint between configured UDP peerings while preserving its process, key, TUN and application socket. Observe pathfinder/route-server updates, new labels and the same inner session/handles before timeout. Check both directions, stale labels, loss and CryptoAuth reset behavior. Pin a complete executable build; source inspection alone does not qualify deployment or seamless handover.