{
  "context": "This criteria evaluates how well an engineer uses the webrtc-adapter package to implement track-specific statistics retrieval for RTP senders and receivers. The focus is on properly utilizing the getStats() methods that webrtc-adapter provides on RTCRtpSender and RTCRtpReceiver prototypes, which enable cross-browser access to track-specific metrics.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Sender getStats usage",
      "description": "Uses RTCRtpSender.prototype.getStats() method to retrieve statistics for senders. This method is provided by webrtc-adapter and returns a Promise that resolves to an RTCStatsReport containing sender-specific metrics.",
      "max_score": 40
    },
    {
      "name": "Receiver getStats usage",
      "description": "Uses RTCRtpReceiver.prototype.getStats() method to retrieve statistics for receivers. This method is provided by webrtc-adapter and returns a Promise that resolves to an RTCStatsReport containing receiver-specific metrics.",
      "max_score": 40
    },
    {
      "name": "Empty state handling",
      "description": "Properly handles the case where a sender has no active track, which should result in an empty stats report being returned. This demonstrates understanding of how webrtc-adapter's stats implementation behaves when tracks are absent.",
      "max_score": 20
    }
  ]
}