{
  "context": "Evaluates whether the solution leans on numpydoc's parsing, signature inference, and templating features to render docstrings per the spec. Emphasizes using the library's built-in signature reconstruction and template override mechanisms instead of custom parsing.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Doc parser",
      "description": "Parses targets via numpydoc docstring loaders (e.g., docscrape.get_doc_object or docscrape_sphinx.get_doc_object) rather than manual string handling.",
      "max_score": 20
    },
    {
      "name": "Inference fallback",
      "description": "Uses numpydoc's FunctionDoc/SphinxFunctionDoc signature inference or the mangle_signature hook to synthesize call signatures when inspect.signature data is missing.",
      "max_score": 30
    },
    {
      "name": "Text signature cleanup",
      "description": "Relies on numpydoc's signature cleaning (such as mangle_signature processing of __text_signature__) to remove positional-only markers or duplicate module prefixes instead of custom string munging.",
      "max_score": 20
    },
    {
      "name": "Template override",
      "description": "Supplies a custom docstring template path through numpydoc rendering (config['docstring_template'] or SphinxDocString template override) so output reflects the provided template marker.",
      "max_score": 30
    }
  ]
}