evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
{
"context": "Evaluates whether the solution relies on portfinder to locate free Unix socket or Windows pipe endpoints as specified. Also checks that package options drive path configuration, collision handling, and cross-platform behavior.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Socket lookup API",
"description": "Uses portfinder.getSocket or portfinder.getSocketPromise as the mechanism to produce the available IPC path instead of manual filesystem probing.",
"max_score": 30
},
{
"name": "Base path config",
"description": "Configures the search start via basePath (or setBasePath) so default temp path and caller-provided paths are honored before lookup runs.",
"max_score": 20
},
{
"name": "Collision search",
"description": "Relies on portfinder's incremental socket search (nextSocket behavior) to skip occupied paths and pick the next available candidate rather than ad-hoc suffix logic.",
"max_score": 20
},
{
"name": "Windows pipes",
"description": "Passes Windows pipe names through portfinder.getSocket/getSocketPromise so pipe prefixes stay intact and collision resolution is handled for pipe endpoints.",
"max_score": 15
},
{
"name": "Parent directories",
"description": "Allows portfinder to create missing parent directories for the socket path during lookup instead of requiring manual directory setup.",
"max_score": 15
}
]
}