{
  "context": "Evaluates whether the agent correctly implements PubNub wildcard subscription patterns with proper dot-delimited hierarchy and understands the specific constraints on wildcard placement and depth. Tests PubNub-specific wildcard rules that differ from typical glob patterns.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Dot hierarchy delimiter",
      "description": "Channel names use dots (periods) as the hierarchy delimiter for wildcard-eligible channels (e.g., 'sensors.building1.temperature')",
      "max_score": 25
    },
    {
      "name": "Asterisk at end only",
      "description": "All wildcard subscribe patterns place the asterisk (*) only at the end of the pattern, never at the beginning or middle",
      "max_score": 25
    },
    {
      "name": "Max two dots",
      "description": "Channel hierarchy uses at most two dots (three levels), not exceeding the maximum depth allowed for wildcard subscriptions",
      "max_score": 20
    },
    {
      "name": "Stream Controller noted",
      "description": "The solution mentions or acknowledges that wildcard subscriptions require the Stream Controller add-on to be enabled",
      "max_score": 15
    },
    {
      "name": "Correct subscribe syntax",
      "description": "The wildcard subscribe call uses the correct PubNub syntax: pubnub.subscribe({ channels: ['prefix.*'] })",
      "max_score": 15
    }
  ]
}