{
  "context": "Evaluates whether the diagnostics helper leans on Parcel's built-in watch-mode profiling and heap snapshot capabilities. Checks that watch builds are started through Parcel, profiling is enabled via the documented flag, and the interactive shortcuts for CPU profiles and heap dumps are correctly surfaced and reported.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Watch mode",
      "description": "Starts watch builds through Parcel (`parcel watch` CLI or `Parcel.watch()`) for the provided entry, avoiding custom file-watching or manual bundling.",
      "max_score": 25
    },
    {
      "name": "Profiling flag",
      "description": "Enables Parcel's CPU profiling support (e.g., passing `--profile` or setting `defaultOptions.profile = true`) so the watch run can emit a profile when toggled.",
      "max_score": 25
    },
    {
      "name": "Heap shortcut",
      "description": "Keeps Parcel's interactive key bindings active and forwards input so the `Ctrl+Y` heap snapshot shortcut writes a dump to the `.parcel-debug` diagnostics directory.",
      "max_score": 20
    },
    {
      "name": "Profile toggle",
      "description": "Surfaces Parcel's `Ctrl+E` CPU profile toggle during watch (or equivalent programmatic trigger) and ensures the resulting profile artifact from Parcel is captured from `.parcel-debug` rather than a custom profiler.",
      "max_score": 15
    },
    {
      "name": "Path reporting",
      "description": "Reads the profile and heap snapshot locations from Parcel's own outputs (diagnostic log lines or `.parcel-debug` filenames) and logs those absolute paths back to the user.",
      "max_score": 15
    }
  ]
}