Connectivity test: peers never form direct link post aggregator

[sanity]

Summary

test_three_node_network_connectivity fails to form a full mesh after the event-log aggregator refactor. Gateway links come up, but peer↔peer links never appear, so the test times out.

Steps to Reproduce

1. Checkout feat/event-log-aggregator (current PR branch).
2. Run cargo test --test connectivity test_three_node_network_connectivity -- --nocapture.
3. Observe that the gateway reports two peers, while each peer only lists the gateway. After ~60s the test fails.

Expected Behavior

After both peers join the gateway they should discover each other and form a direct connection, satisfying the full-mesh assertion.

Actual Behavior

• ConnectedPeers shows each peer connected only to the gateway.
• Event logs contain only gateway↔peer Connect events.
• connection_maintenance never acquires additional peers (live transaction tracker stays empty).

Notes & Hypotheses

• The aggressive bootstrap loop exits without seeding the first peer↔peer link. Skip lists or router cache may prevent forwarding recommendations beyond the gateway.
• Extending wait times or force-adding gateways did not resolve the issue; instead bootstrap stalled.

Suggested Next Steps

• Instrument connection_maintenance / forward_conn to see why the gateway doesn't suggest other peers once multiple peers are attached.
• Verify whether the router cache excludes the gateway when searching for candidates.
• After fixing discovery, restore a strict assertion in the integration test so CI keeps the mesh requirement enforced.

/cc @freenet-networking

[github-actions]

🤖 Auto-labeled

Applied labels:

• T-bug (95% confidence)
• P-medium (75% confidence)
• A-networking (90% confidence)
• S-needs-reproduction (85% confidence)

Reasoning: The title describes a connectivity test where peers never form a direct link after an aggregator, which reads like a bug in networking or the connectivity test itself. Priority set to P-medium as this likely affects some tests/users but there's no indication it's release-blocking. Effort estimated as medium since network test/debugging can require setting up scenarios and investigating async peer behavior. Areas: A-networking because this concerns peer connections/topology, and A-developer-xp because it appears tied to a test. The issue body lacks reproduction steps or details, so S-needs-reproduction is appropriate.

Previous labels: none

If these labels are incorrect, please update them. This helps improve the auto-labeling system.

[iduartgomez]

Fixed in #2041 apparently