{
  "context": "Evaluates whether the solution uses update-electron-app to normalize legacy repo/host options into the current updateSource format before initialization. Checks that modern configurations are preferred when present and that validation and shared options are routed through updateElectronApp.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Initializer use",
      "description": "Invokes update-electron-app's updateElectronApp (or equivalent exported initializer) to configure updates rather than reimplementing the updater flow.",
      "max_score": 25
    },
    {
      "name": "Legacy parsing",
      "description": "Splits legacy repo strings into owner and repo parts and builds an updateSource object with type 'github' when only legacy repo/host inputs are provided.",
      "max_score": 25
    },
    {
      "name": "Host migration",
      "description": "Maps a provided legacy host into the updateSource host field only when it is HTTPS, rejecting or adjusting non-HTTPS hosts before calling updateElectronApp.",
      "max_score": 15
    },
    {
      "name": "Modern precedence",
      "description": "When a modern updateSource object is supplied alongside legacy fields, uses the provided updateSource unchanged and still routes it through updateElectronApp.",
      "max_score": 20
    },
    {
      "name": "Option passthrough",
      "description": "Passes through shared options like logger and notifyUser to updateElectronApp alongside the derived updateSource configuration.",
      "max_score": 15
    }
  ]
}