rpcserver: fix stats undercount in GetNetworkInfo

[elnosh]

I was seeing dubious numbers from getnetworkinfo command which did not match at all to the graph from describegraph.

Seems the issue is that it is returning early instead of continuing in the loop in GetNetworkInfo so it ended up under counting the stats.

Finding the issue in the code was LLM-assisted

[github-actions]

🔴 PR Severity: CRITICAL

Explicit rule match | 1 file | 7 lines changed

🔴 Critical (1 file)

• rpcserver.go - Core server coordination file, explicitly listed as a CRITICAL path (RPC entry point / core server logic)

Analysis

The only file changed is rpcserver.go, which is explicitly named in the CRITICAL tier as a core server coordination file. The change itself is small (3 additions, 4 deletions) and fixes a control-flow bug in GetNetworkInfo where the loop was returning early instead of continuing, causing undercounted network stats. While the fix is narrowly scoped and low-risk in nature, the file itself warrants expert review per the classification rules, and the size of the diff does not qualify for a severity bump (only 7 lines changed, well under the 500-line/20-file thresholds) nor does it warrant a downgrade — file-based classification takes precedence.

---

_{To override, add a severity-override-{critical,high,medium,low} label.}