{
  "context": "Evaluates how well the solution uses Parcel v2 dev-server features to expose HTTPS with custom host/port and HMR endpoints. Scoring rewards direct use of Parcel's serve/watch APIs or CLI flags rather than custom HTTPS implementations, plus accurate URL reporting and cleanup.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Parcel serving",
      "description": "Uses Parcel's dev server entrypoints (e.g., `parcel serve` CLI flags or `new Parcel({ entries, serveOptions }).watch()`) to host the entry asset instead of rolling a manual HTTPS server.",
      "max_score": 25
    },
    {
      "name": "HTTPS config",
      "description": "Passes HTTPS settings through Parcel (`serveOptions.https` with cert/key or `--https --cert --key`) so the listener uses TLS and reports an https URL.",
      "max_score": 20
    },
    {
      "name": "Host/port binding",
      "description": "Sets `serveOptions.host`/`serveOptions.port` or `--host`/`--port` to honor requested bindings, supports `port: 0` selection, and surfaces the actual bound port in `serverUrl`.",
      "max_score": 20
    },
    {
      "name": "HMR endpoint",
      "description": "Configures Parcel's HMR endpoint (`hmrOptions.host`/`hmrOptions.port` or `--hmr-host`/`--hmr-port`) and returns an `hmrUrl` reflecting the effective host, port, and secure websocket scheme.",
      "max_score": 20
    },
    {
      "name": "Cleanup",
      "description": "Implements shutdown via Parcel's handles (e.g., `subscription.unsubscribe()`, `server.close()`, or `parcel.dispose()`) to close both the dev server and HMR sockets without lingering processes.",
      "max_score": 15
    }
  ]
}