fix peer connection after force_to_close

Author: Jolah1

src/lib.rs

@@ -1842,9 +1842,15 @@ impl Node {
 			}
 
 			// Check if this was the last open channel, if so, forget the peer.
-			if open_channels.len() == 1 {
+			//For force-closes we keep the peer
+            // in the store so the background reconnection task can fire and
+            // complete the channel_reestablish recovery flow. This is especially
+            // important for LND peers
+			// The peer will be removed by the ChannelClosed event handler once
+            // the counterparty reconnects and confirms closure.
+			if open_channels.len() == 1 && !force {
 				self.peer_store.remove_peer(&counterparty_node_id)?;
-			}
+		}
 		}
 
 		Ok(())

tests/integration_tests_rust.rs

@@ -3019,7 +3019,7 @@ async fn test_peer_removed_on_counterparty_force_close() {
 }
 
 #[tokio::test(flavor = "multi_thread", worker_threads = 1)]
-async fn test_peer_not_persisted_on_local_force_close() {
+async fn test_peer_retained_on_local_force_close() {
 	// When WE force-close, keep the peer in the store so we can reconnect
 	// and complete channel_reestablish recovery. This matters especially
 	// for LND counterparties that may not handle force-closure error
@@ -3071,8 +3071,8 @@ async fn test_peer_not_persisted_on_local_force_close() {
 
 	// A should STILL have B in peer store — kept for channel_reestablish.
 	assert!(
-		!node_a.list_peers().iter().any(|p| p.node_id == node_b_id && p.is_persisted),
-		"node_b should not be persisted in node_a peer store after locally-initiated force-close"
+		node_a.list_peers().iter().any(|p| p.node_id == node_b_id && p.is_persisted),
+		"node_b should remain persisted in node_a peer store after locally-initiated force-close"
 	);
 
 	node_a.stop().unwrap();