{
  "context": "Evaluates how the solution uses azure-cognitiveservices-search-nspkg and its dependency azure-cognitiveservices-nspkg to wire the azure.cognitiveservices search namespace. Confirms that legacy azure==0.x conflicts are blocked and that child imports flow through the namespace package rather than custom path hacks.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Import nspkg",
      "description": "Imports azure.cognitiveservices.nspkg so the dependency's pkgutil.extend_path hook wires the parent namespace instead of manually altering sys.path.",
      "max_score": 25
    },
    {
      "name": "Search namespace",
      "description": "Imports azure.cognitiveservices.search (from azure-cognitiveservices-search-nspkg) and reads its __path__ entries to drive namespace status rather than fabricating paths.",
      "max_score": 20
    },
    {
      "name": "Extend path usage",
      "description": "Relies on pkgutil.extend_path executed by the nspkg modules to build namespace_paths, avoiding custom path concatenation or direct filesystem probing.",
      "max_score": 20
    },
    {
      "name": "Legacy block",
      "description": "Detects installed azure==0.x distributions and raises the prescribed RuntimeError specifically because they conflict with azure-cognitiveservices-nspkg wiring.",
      "max_score": 20
    },
    {
      "name": "Child import",
      "description": "Uses importlib.import_module via the azure.cognitiveservices.search.<child> namespace (benefiting from nspkg wiring) to load or report on child modules, without bypassing the namespace package.",
      "max_score": 15
    }
  ]
}