fix: use got_initial_pkt instead of new_conn for send_reset decision
new_conn is only true for the first INIT after server restart.
Subsequent INITs from same peer (recovery loop) see new_conn=0
and revert to old logic, sending 0x05 (no reset) and overwriting
the first 0x03 response.
got_initial_pkt stays 0 until client actually sends seq=1, so
server keeps sending 0x03 across all INIT retries until client
resets and starts from seq=1.
send_reset=1;// Client explicitly requested reset, or new session, or new server-side connection
send_reset=1;// Client explicitly requested reset, or new session, or server waiting for first packet
DEBUG_TRACE(DEBUG_CATEGORY_CONNECTION,"do reinit (code=%02x session was %08x now %08x new_conn=%d)",code,conn->session_id,session_id,new_conn);
DEBUG_TRACE(DEBUG_CATEGORY_CONNECTION,"do reinit (code=%02x session was %08x now %08x got_init=%d)",code,conn->session_id,session_id,conn->got_initial_pkt);
DEBUG_TRACE(DEBUG_CATEGORY_CONNECTION,"do reinit for new link (code=%02x session was %08x now %08x new_conn=%d)",code,conn->session_id,session_id,new_conn);
DEBUG_TRACE(DEBUG_CATEGORY_CONNECTION,"do reinit for new link (code=%02x session was %08x now %08x got_init=%d)",code,conn->session_id,session_id,conn->got_initial_pkt);