nx_connect_lds_reconnect_lib.nx

nx_connect_lds_reconnect_lib.nx -- the MEMBER <-> MISSIONARY RECONNECTION model, extracted as a shared library so the verifying gate (nx_connect_lds_reconnect) and the LIVE app (nx_connect_serve) bind ONE implementation of the law instead of two that can drift. This is the split the gate's own DRY note named: "the small primitives are re-stated to keep the gate self-contained; production extracts them to a shared library organ". No main, no syscalls, no allocation -- records are caller-supplied buffers -- so any consumer can import it, including one that never pulls in the syscall layer. THE LAW (unchanged, integer-only, no floats): two people could have KNOWN each other only if they were in the SAME MISSION, share an AREA, and their time windows OVERLAP. All three are NECESSARY, so a later missionary in the same area does not surface (time is load-bearing) and a same-mission person in a different area does not surface (area is load-bearing). A mutually-confirmed "I remember you" edge outranks inferred overlap. Discovery is CONSENT-GATED both ways (GDPR Art.9-style): a member who has not opted in is never surfaced, however real the overlap. The DATE lane is UNREACHABLE when a minor is involved, in both directions -- a returned missionary and a youth they taught are community, never romance. RECORD LAYOUT (8 slots): p[0]=age_band p[1]=mission p[2]=areas-bitmask p[3]=start_month p[4]=end_month p[5]=reconnect_optin p[6]=self_token p[7]=confirmed_tokens license_tier: ORIGINAL