{
  "context": "Evaluates whether the solution builds URLs using furl's Path helpers for decoded segments, absolute vs relative handling, and directory/file hints rather than manual string munging. Checks center on proper use of furl.furl parsing plus Path properties that enforce encoding, absoluteness, and trailing slash semantics.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Parse base",
      "description": "Uses `furl.furl` (or `furl()` constructor) to parse the base URL and work with its `path` object instead of manual string concatenation.",
      "max_score": 20
    },
    {
      "name": "Decoded segments",
      "description": "Populates path parts via `Path.segments` or `Path.add` so percent-encoded pieces stay decoded internally and are re-encoded on output (e.g., `%2F` remains a single segment).",
      "max_score": 20
    },
    {
      "name": "Append vs replace",
      "description": "Merges incoming parts with the base path using `Path.add`, `/=` operator, or direct `segments` replacement to control whether leading separators replace the base path versus append to it, relying on Path normalization to collapse duplicate slashes.",
      "max_score": 20
    },
    {
      "name": "Absoluteness",
      "description": "Sets or respects `Path.isabsolute`/`absolute` so that paths become absolute when the base has a netloc or when the caller requests it, and can emit relative paths when explicitly asked for one.",
      "max_score": 20
    },
    {
      "name": "Directory hint",
      "description": "Uses `Path.isdir`/`isfile` (or `set(isdir=...)`) to enforce trailing slash semantics for directory vs file targets rather than trimming or appending slashes manually.",
      "max_score": 20
    }
  ]
}