docs
evals
scenario-1
scenario-10
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
{
"context": "Evaluates whether the solution correctly uses the punycode library to decode xn-- labels in domains and email addresses. Checks that Unicode conversion, ASCII passthrough, and error signaling are handled through the library rather than manual logic.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Domain decoding",
"description": "Uses punycode.toUnicode (or punycode.decode per label) to convert xn-- domain labels to Unicode while leaving ASCII labels intact in mixed domains.",
"max_score": 30
},
{
"name": "Email domain",
"description": "Applies punycode.toUnicode only to the domain portion after splitting on '@', preserving the local part unchanged when decoding email inputs.",
"max_score": 25
},
{
"name": "ASCII passthrough",
"description": "Relies on punycode.toUnicode idempotency to return unchanged output for inputs without xn-- labels rather than re-encoding or altering ASCII text.",
"max_score": 15
},
{
"name": "Error propagation",
"description": "Ensures malformed xn-- labels surface a RangeError from punycode.toUnicode or punycode.decode instead of being silently swallowed or coerced to fallback output.",
"max_score": 15
},
{
"name": "Prefix handling",
"description": "Detects xn-- prefix when selecting labels to decode and avoids applying punycode.toUnicode/punycode.decode to labels that lack the prefix, keeping non-encoded segments untouched.",
"max_score": 15
}
]
}