node:net Socket/Server: connection lifecycle hangs + server.address()/listen/on gaps (75 radar runtime-fails, 24% parity)

[proggeramlug]

Summary

Now that node:net links (#1842), it's the biggest measurable weak API: 24% parity, 75 runtime-fails. Clustered from the #800 --auto-optimize sweep (perry 0.5.1029):

Clusters

• 19 timeout/hang — net servers/sockets hang instead of completing (connection lifecycle: server.listen callback never fires, or sockets never connect/close). The single biggest cluster.
• 11 value() missing — net Socket/Server methods resolve to non-callable stubs.
• 7 undefined.address — server.address() returns undefined.
• 4 undefined.listen — net.createServer().listen missing/undefined in some shapes.
• 3 undefined.on — Socket/Server not wired as EventEmitters in some paths.
• 9 behavioral diff, 5 uncaught exceptions.

Priority

The hang cluster (19) is highest-impact and most concerning — it means the net connection lifecycle (listen→connection→data→close) isn't completing, which blocks most real net usage and cascades into http/https (which build on net). server.address() and EventEmitter wiring are the next concrete items.

Companion to #1779/#1780. Context: #800 --auto-optimize sweep (net 8%→24% once linkable). http is 64% by comparison, so the net-layer gaps are the ceiling for further http/https gains too.