{
  "context": "Evaluates whether the solution leverages josepy's JOSE Base64 helpers to encode and decode payloads as described in the spec. Emphasis is on correct use of josepy.b64encode/b64decode for URL-safe, unpadded data and proper handling of invalid inputs.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Encode helper",
      "description": "Uses josepy.b64encode to produce URL-safe Base64 output without padding for bytes payloads instead of manual base64 handling, matching the encode_compact contract.",
      "max_score": 30
    },
    {
      "name": "Decode helper",
      "description": "Uses josepy.b64decode to convert JOSE Base64 strings to bytes, relying on its padding normalization and invalid-character detection rather than custom logic.",
      "max_score": 30
    },
    {
      "name": "Round trip",
      "description": "Encoding followed by decoding via josepy helpers returns the original bytes for valid inputs, demonstrating correct parameter choices (e.g., urlsafe variant, no extra padding).",
      "max_score": 15
    },
    {
      "name": "Input checks",
      "description": "Validates inputs with josepy expectations: rejects non-bytes or non-ASCII text before encoding and surfaces josepy's ValueError for malformed Base64 on decode.",
      "max_score": 15
    },
    {
      "name": "Padding rules",
      "description": "Maintains josepy's no-padding policy on encode and relies on josepy's padding normalization on decode (no manual stripping or incorrect padding reconstruction).",
      "max_score": 10
    }
  ]
}