{
  "context": "Evaluates whether the solution relies on mkdocs-awesome-nav to resolve `.nav.yml` files and correctly apply inherited ignore patterns, especially the `$inherit` sentinel, when building navigation output for nested docs folders. It checks that ignore handling, merging, and filtering are delegated to the package rather than recreated by hand.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Plugin loader",
      "description": "Loads `.nav.yml` configs through mkdocs-awesome-nav constructs such as NavConfig.from_file or the AwesomeNav plugin hook instead of ad-hoc YAML parsing.",
      "max_score": 20
    },
    {
      "name": "Inherit token",
      "description": "Leverages the package's inherit_token (`$inherit`) handling so child ignore lists append parent patterns in order rather than reimplementing merge logic manually.",
      "max_score": 25
    },
    {
      "name": "Ignore glob resolution",
      "description": "Uses the package's ignore resolution (e.g., NavConfig.ignore with create_absolute_pattern) so patterns respect directory bases and leading slash semantics.",
      "max_score": 20
    },
    {
      "name": "Override behavior",
      "description": "Demonstrates that omitting `$inherit` resets the ignore list per mkdocs-awesome-nav defaults (IgnoreConfig.patterns starting with inherit_token only when unset).",
      "max_score": 20
    },
    {
      "name": "Nav filtering",
      "description": "Filters final navigation entries via mkdocs-awesome-nav objects (NavDirectory/NavPage/NavPattern) so ignored paths from parent and child configs are excluded before ordering.",
      "max_score": 15
    }
  ]
}