{
  "context": "Evaluates how the solution uses nock lifecycle controls to stage HTTP expectations, verify they were exercised, report any remaining mocks, and fully reset between runs.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Mock setup",
      "description": "Builds nock scopes with the constructor base URL and programs each expectation (method/path/status/body/headers) using nock interceptors rather than manual stubs.",
      "max_score": 20
    },
    {
      "name": "Completion check",
      "description": "Implements assertComplete using nock's completion APIs (e.g., scope.done() or nock.isDone()) and surfaces outstanding method/path details when expectations were missed.",
      "max_score": 25
    },
    {
      "name": "Pending reporting",
      "description": "pending() returns information derived from nock.pendingMocks() or equivalent per-scope pending lists, updating as requests are matched.",
      "max_score": 20
    },
    {
      "name": "Lifecycle reset",
      "description": "reset() invokes nock.abortPendingRequests() (or similar) and nock.cleanAll() to cancel inflight mocks and remove interceptors so later runs start clean.",
      "max_score": 20
    },
    {
      "name": "Run flow",
      "description": "runWithMocks plans expectations before invoking the callback, ensures responses come from the programmed nock scopes, and performs completion/cleanup using nock lifecycle controls.",
      "max_score": 15
    }
  ]
}