{
  "context": "This criteria evaluates how well the engineer implements exit code management patterns using the snazzy package's approach. The focus is on proper exit code propagation, deferred setting after stream completion, property exposure for programmatic access, and conditional override behavior.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Exit handler usage",
      "description": "Uses process.on('exit') event handler to set the exit code after all asynchronous stream operations have completed, ensuring reliable exit code propagation",
      "max_score": 25
    },
    {
      "name": "Process exitCode property",
      "description": "Sets process.exitCode property (not process.exit()) within the exit handler to allow other cleanup operations to complete before process termination",
      "max_score": 20
    },
    {
      "name": "Stream exitCode property",
      "description": "Exposes an exitCode property on the stream/reporter instance that can be accessed programmatically after processing completes (e.g., reporter.exitCode)",
      "max_score": 20
    },
    {
      "name": "Conditional override logic",
      "description": "Only overrides the process exit code when it would otherwise be 0 (success), preserving any existing non-zero exit codes (e.g., if (code === 0 && reporter.exitCode !== 0))",
      "max_score": 15
    },
    {
      "name": "Correct exit values",
      "description": "Sets exit code to 0 when no issues are found and 1 when issues are detected, correctly distinguishing between success and failure states",
      "max_score": 15
    },
    {
      "name": "Deferred setting timing",
      "description": "Ensures exit code is determined only after all input data has been fully processed (e.g., in stream's _flush() method or 'finish' event), not prematurely during data processing",
      "max_score": 5
    }
  ]
}