{
  "context": "Evaluates how well the solution uses furl to manipulate fragment path and query pieces for the specified URL-building helpers. Scoring checks reliance on fragment-aware APIs, ordered multivalue query handling, separator control, and serialization through furl rather than manual string work.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Path setting",
      "description": "Fragment paths are built via `furl(url).fragment.path` (or `.fragment.path.segments`) so segments replace the existing fragment path with percent-encoding handled by furl rather than manual string concatenation.",
      "max_score": 25
    },
    {
      "name": "Query merge",
      "description": "New fragment parameters are added with `fragment.query.add`/`set` semantics (or omdict-style assignment) so list values expand to repeated keys and existing keys keep their order instead of manual parsing/joining.",
      "max_score": 25
    },
    {
      "name": "Removal API",
      "description": "Fragment query removal uses furl helpers such as `fragment.query.remove`/`fragment.remove` to drop keys while leaving fragment paths untouched, avoiding ad-hoc string slicing.",
      "max_score": 20
    },
    {
      "name": "Separator toggle",
      "description": "Implements the separatorless variant by flipping `fragment.separator` (or equivalent) to omit the '?' between fragment path and query when requested, while keeping the default separator for other calls.",
      "max_score": 20
    },
    {
      "name": "Serialization",
      "description": "Final URLs are produced through furl's serialization (`f.url`, `tostr()`, or `str(f)`) to preserve encoding/order instead of manual string formatting.",
      "max_score": 10
    }
  ]
}