{
  "context": "Evaluates how the solution leverages update-electron-app to assemble update feed URLs and request headers for the host application. Checks focus on using the library's updateSource options for public and static feeds and ensuring the package-derived User-Agent is applied. General code quality is not assessed.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Library entry point",
      "description": "Delegates feed setup to update-electron-app by calling updateElectronApp (or its exported setup) instead of manually configuring autoUpdater.",
      "max_score": 20
    },
    {
      "name": "Public source config",
      "description": "Uses updateSource with type UpdateSourceType.ElectronPublicUpdateService, providing host (defaulting to https://update.electronjs.org) and repo values so the library builds <host>/<owner>/<repo>/<platform>-<arch>/<version>.",
      "max_score": 20
    },
    {
      "name": "Static source config",
      "description": "Configures static feeds via updateSource type UpdateSourceType.StaticStorage with an HTTPS baseUrl and relies on the library to append /RELEASES.json with serverType 'json' on macOS while using the base URL unchanged elsewhere.",
      "max_score": 20
    },
    {
      "name": "User-Agent header",
      "description": "Allows the library's User-Agent header (<package-name>/<package-version> (<platform>: <arch>)) to flow into autoUpdater.setFeedURL headers without overriding it with a custom string.",
      "max_score": 25
    },
    {
      "name": "Metadata defaults",
      "description": "Relies on the package's repo and package.json discovery (guessRepo/userAgent generation) when repo or app name/version are not manually provided, rather than reimplementing those lookups.",
      "max_score": 15
    }
  ]
}