Summary
test_parity_net is still listed as a module-inventory known failure on current origin/main, but the broad generated fixture now mostly probes deterministic value shapes for node:net: IP classifiers, default auto-select-family settings, BlockList, SocketAddress, and unconnected Server / Socket instance surfaces.
Proposed focused scope
Stabilize and/or implement the remaining deterministic node:net inventory tail so test_parity_net can become an exact Node/Perry parity probe instead of a skip-listed module-inventory gap.
Candidate surfaces:
net.isIP, isIPv4, isIPv6 output and validation shape
- default auto-select-family getters/setters
BlockList rule add/check/toJSON/rules/isBlockList behavior
SocketAddress constructor/parse/accessors
- unconnected
Server and Socket constructor/property/method shape
- stale known-failure, parity-threshold, and matrix-baseline entries if the probe passes after fixes
Non-goals
No live network server/client behavior, no external sockets, no IPC endpoint tests, no TLS/HTTP behavior, and no broad stream lifecycle rewrites. Live connection semantics should stay in focused net/socket issues.
Summary
test_parity_netis still listed as a module-inventory known failure on currentorigin/main, but the broad generated fixture now mostly probes deterministic value shapes fornode:net: IP classifiers, default auto-select-family settings,BlockList,SocketAddress, and unconnectedServer/Socketinstance surfaces.Proposed focused scope
Stabilize and/or implement the remaining deterministic
node:netinventory tail sotest_parity_netcan become an exact Node/Perry parity probe instead of a skip-listed module-inventory gap.Candidate surfaces:
net.isIP,isIPv4,isIPv6output and validation shapeBlockListrule add/check/toJSON/rules/isBlockList behaviorSocketAddressconstructor/parse/accessorsServerandSocketconstructor/property/method shapeNon-goals
No live network server/client behavior, no external sockets, no IPC endpoint tests, no TLS/HTTP behavior, and no broad stream lifecycle rewrites. Live connection semantics should stay in focused net/socket issues.