{
  "context": "Evaluates how the solution uses Parcel's watch mode to select watcher backends, apply ignore lists, and scope the watch root while reporting rebuilds. Focuses on correct use of Parcel CLI flags and core APIs tied to watcher configuration.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Parcel watch API",
      "description": "Starts watch mode via Parcel (e.g., `new Parcel({...}).watch()` or `parcel watch`) and uses the returned `unsubscribe`/process handle to implement the stop function rather than a custom file watcher.",
      "max_score": 20
    },
    {
      "name": "Backend selection",
      "description": "Passes the requested backend into Parcel using the official `--watch-backend` CLI flag or the `watchBackend` option on the Parcel constructor, accepting valid values like `watchman`, `fs-events`, `inotify`, `windows`, or `brute-force`, and surfacing an error when an unsupported backend is provided.",
      "max_score": 25
    },
    {
      "name": "Ignore globs",
      "description": "Configures ignore patterns through Parcel's `--watch-ignore` flag or `watchIgnore` option so ignored paths do not trigger rebuilds, instead of filtering changes manually after events fire.",
      "max_score": 25
    },
    {
      "name": "Watch root",
      "description": "Scopes file watching to the intended directory by setting Parcel's `--watch-dir` flag or `watchDir` option, ensuring changes outside that root are automatically ignored.",
      "max_score": 15
    },
    {
      "name": "Rebuild reporting",
      "description": "Uses Parcel watch event data (e.g., the callback parameters from `parcel.watch` including `event.changedAssets` or CLI output) to emit the changed file path when a non-ignored rebuild occurs, rather than synthesizing messages without Parcel event data.",
      "max_score": 15
    }
  ]
}