{
  "context": "Tests whether the agent avoids thread pool bottlenecks by using dns.resolve*() instead of dns.lookup(), configures UV_THREADPOOL_SIZE correctly before Node.js startup, implements DNS result caching, and adds thread pool saturation monitoring.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "dns.resolve* used",
      "description": "The service code uses 'dns.resolve4()', 'dns.resolve6()', 'dns.promises.resolve4()', or another 'dns.resolve*()' variant — NOT 'dns.lookup()' or 'dns.promises.lookup()' — for hostname resolution",
      "max_score": 20
    },
    {
      "name": "No dns.lookup",
      "description": "The service code does NOT call 'dns.lookup()' or 'dns.promises.lookup()' anywhere in the resolution path",
      "max_score": 10
    },
    {
      "name": "UV_THREADPOOL_SIZE via env",
      "description": "UV_THREADPOOL_SIZE is configured via an environment variable set BEFORE Node.js starts — either in a package.json 'scripts' entry (e.g., 'UV_THREADPOOL_SIZE=16 node service.js'), a shell startup script, or a README/startup-instructions.txt — NOT by assigning 'process.env.UV_THREADPOOL_SIZE' inside the running script",
      "max_score": 20
    },
    {
      "name": "No process.env assignment",
      "description": "The service code does NOT contain 'process.env.UV_THREADPOOL_SIZE =' (assigning UV_THREADPOOL_SIZE inside the running process)",
      "max_score": 10
    },
    {
      "name": "DNS result caching",
      "description": "Resolved addresses are stored in a cache (Map, object, or library) and reused for subsequent lookups to the same hostname, avoiding repeated thread pool or c-ares calls",
      "max_score": 15
    },
    {
      "name": "Cache expiry",
      "description": "Cached DNS entries are expired or refreshed after a time interval (e.g., via setTimeout, TTL tracking, or similar mechanism)",
      "max_score": 10
    },
    {
      "name": "Thread pool monitoring",
      "description": "The code includes monitoring for thread pool saturation — either a DNS-lookup-based latency canary ('dns.lookup' timing), async hooks tracking thread-pool async types, or 'monitorEventLoopDelay' from perf_hooks with a warning threshold",
      "max_score": 15
    }
  ]
}