{
  "context": "Evaluates how well the solution uses Vedro's deferred cleanup queues and temporary path helpers to manage ephemeral workspaces and artifacts for the cleanup workflow. Checks that resource lifecycles are tied to the framework rather than manual filesystem handling.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Temp dir helper",
      "description": "Workspace creation relies on Vedro's create_tmp_dir helper (not manual tempfile/os calls) to provision the scenario workspace.",
      "max_score": 20
    },
    {
      "name": "Scenario defers",
      "description": "Scenario-scoped cleanup uses vedro.defer to enqueue removal of staged files and the workspace after verification, keeping resources available during the test.",
      "max_score": 25
    },
    {
      "name": "Temp file helper",
      "description": "Artifact files inside the workspace are produced with Vedro's create_tmp_file helper (with provided content) instead of ad-hoc file creation.",
      "max_score": 20
    },
    {
      "name": "Global defer",
      "description": "Run-level teardown is registered with vedro.defer_global so suite-wide resources (e.g., background process, workspace artifacts) clean up once after all scenarios.",
      "max_score": 20
    },
    {
      "name": "Cleanup order",
      "description": "Queued callbacks preserve insertion order by how vedro.defer/vedro.defer_global are invoked, ensuring child artifacts are scheduled before parent workspace teardown.",
      "max_score": 15
    }
  ]
}