{
  "context": "Evaluates how the solution composes DNS UPDATE requests using dnspython's message builders, EDNS options, and TSIG signing to match the spec. Checks focus on using dnspython APIs to build add/delete operations, attach EDNS client subnet, sign the packet, and return wire bytes with metadata reflecting the composed message.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Dynamic update build",
      "description": "Uses dnspython's dynamic update helpers (e.g., dns.update.Update / UpdateMessage) with .add()/.delete() and dns.rdata.from_text to encode the specified additions and deletions so the resulting message has the UPDATE opcode, proper zone section, and correct record data/TTLs for both add and delete cases.",
      "max_score": 30
    },
    {
      "name": "EDNS payload/option",
      "description": "Attaches EDNS(0) via message.use_edns or equivalent with payload size 1232 and encodes the client-subnet option using dns.edns.ECSOption('203.0.113.5', 24) so the OPT record carries code 8 data; omits OPT when EDNS inputs are absent.",
      "max_score": 25
    },
    {
      "name": "TSIG signing",
      "description": "Builds a TSIG keyring (e.g., dns.tsigkeyring.from_text) and signs the message with use_tsig using key name update-key.example.com., the provided base64 secret, algorithm hmac-sha256 (dns.tsig.HMAC_SHA256), and fudge 300 so the additional section contains a verifiable TSIG record.",
      "max_score": 25
    },
    {
      "name": "Wire output & metadata",
      "description": "Serializes the composed message to bytes with to_wire (or dns.message.to_wire) and returns metadata fields derived from message.id, message.opcode().name, and section_count() values that match the actual message layout (zone/prereq/update/additional).",
      "max_score": 20
    }
  ]
}