node:http Agent socket pooling — getName works, real pool absent (#2129 followup)

[proggeramlug]

Summary

PR #2XXX (#2129) shipped http.Agent / https.Agent as a constructible class with a real getName(options) and chainable no-op methods. That unblocks the basic agent-getname test family.

What Perry's Agent does NOT do today:

• Socket pooling — http.request({ agent }) opens a fresh reqwest connection every call, ignoring the agent. keepAlive/maxSockets/maxFreeSockets/maxTotalSockets are stored as state but not enforced.
• agent.sockets / agent.freeSockets / agent.requests accessors — return undefined (no pool state to expose).
• agent.createConnection / agent.createSocket overrides — tests like test-http-agent-close.js rewrite these to inject error paths; Perry stores the assignment but never calls back into it.
• Argument validation — new http.Agent({ maxTotalSockets: -1 }) doesn't throw ERR_OUT_OF_RANGE (matches test-http-agent-maxtotalsockets.js's assert.throws expectations); see also stdlib doesn't throw Node arg-validation errors (ERR_INVALID_ARG_TYPE/EBADF/...) on bad input — ~85 tests across fs/buffer/net/http/crypto/zlib/process #2013 for the broader arg-validation gap.

Scope

These all require a real connection pool wired into the request path (js_http_request / js_https_request). That's a much larger change than the constructor + metadata work in #2129's first PR.

Related

• node:http: 57 method-surface gaps (Agent/ClientRequest/IncomingMessage/Server.listen) #2129 (umbrella)
• stdlib doesn't throw Node arg-validation errors (ERR_INVALID_ARG_TYPE/EBADF/...) on bad input — ~85 tests across fs/buffer/net/http/crypto/zlib/process #2013 (Node-style arg validation)

[proggeramlug]

PR #2264 shipped the majority of this issue:

• ✅ Argument validation — new Agent({ maxSockets: -1 }) etc. now throw RangeError [ERR_OUT_OF_RANGE].
• ✅ sockets/freeSockets/requests accessors — return {} instead of undefined.
• ✅ Per-agent reqwest::Client — options.agent = new Agent({...}) routes through a per-agent client whose pool honors keepAlive/maxFreeSockets/keepAliveMsecs. Wired through both perry-ext-http and perry-stdlib's parallel http path.
• ✅ Tunable property setters with same validation.
• ✅ agent.destroy() flips the destroyed flag + drops the cached client.
• ⏳ createConnection / createSocket setter storage — pointer stored + GC-rooted so reads round-trip, but invocation on the request path (Node's net.Socket injection semantics) is deferred. That needs net.Socket-shaped JS objects http.ClientRequest can write to, which is a much larger socket-bridging effort.

Leaving open for the createConnection invocation follow-up.