docs
evals
scenario-1
scenario-10
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
{
"context": "This criteria evaluates how effectively the engineer uses pnpm's configuration system to implement minimum release age enforcement. The focus is on correctly utilizing pnpm's `pnpm config set` command and the `minimum-release-age` configuration setting to solve the problem.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses pnpm config",
"description": "Implementation uses pnpm's configuration system (e.g., `pnpm config set` or equivalent programmatic API) rather than manually editing configuration files or using other package managers",
"max_score": 30
},
{
"name": "Sets minimum-release-age",
"description": "Implementation specifically sets the `minimum-release-age` configuration setting with the correct value format (number representing days or duration)",
"max_score": 35
},
{
"name": "Scopes configuration",
"description": "Configuration is properly scoped to the target project directory using pnpm's directory-specific configuration mechanism (e.g., using `--dir` flag or working directory context)",
"max_score": 20
},
{
"name": "Validates configuration",
"description": "Implementation verifies that the configuration was successfully applied, potentially by reading back the configuration value using `pnpm config get` or equivalent",
"max_score": 15
}
]
}