Merge branch 'refactor-node' into refactor-node-next

Forward-merge the promote-failure warning target pin. The peer-action
executor diverges between the two lines (IK vs XX establish arms), so the
pin was applied to this line's own two promote-Err warns during the merge
resolution: outbound "Failed to promote connection" and inbound "Failed to
promote inbound connection" now emit under fips::node::handlers::handshake,
matching the sibling max-peers reject log already pinned to that target.

src/node/dataplane/peer_actions.rs

@@ -316,6 +316,7 @@ impl Node {
                             // and leaves the `pending_outbound` entry for the stale-
                             // connection reaper.
                             warn!(
+                                target: "fips::node::handlers::handshake",
                                 link_id = %promote_link,
                                 error = %e,
                                 "Failed to promote connection"
@@ -342,6 +343,7 @@ impl Node {
                                 );
                             } else {
                                 warn!(
+                                    target: "fips::node::handlers::handshake",
                                     link_id = %promote_link,
                                     error = %e,
                                     "Failed to promote inbound connection"