{
  "context": "Evaluates how well the solution uses @tailwindcss/node's Instrumentation utilities to build the hierarchical profiler described in the spec. Focuses on timers, counters, reporting, and debug-driven disposal rather than custom implementations.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Instrumentation setup",
      "description": "Creates and reuses a single @tailwindcss/node Instrumentation instance (optionally with a default flush) instead of custom timing logic.",
      "max_score": 20
    },
    {
      "name": "Nested timers",
      "description": "Uses Instrumentation.start(label)/end(label) pairs to model the root and nested sections, respecting stack order and merging repeated labels rather than manual timestamp math.",
      "max_score": 20
    },
    {
      "name": "Async timing",
      "description": "Wraps async callbacks by starting before awaiting and ending after resolution using Instrumentation timers, ensuring durations come from the package rather than manual Date calculations.",
      "max_score": 20
    },
    {
      "name": "Hit counters",
      "description": "Tracks occurrences with Instrumentation.hit(label) (e.g., cache-miss counts) instead of ad-hoc counters, and integrates those counts into the report output.",
      "max_score": 15
    },
    {
      "name": "Reporting & disposal",
      "description": "Generates the textual report via Instrumentation.report() with optional custom flush and leverages Instrumentation[Symbol.dispose]() to auto-flush when DEBUG is enabled.",
      "max_score": 15
    },
    {
      "name": "Reset behavior",
      "description": "Clears prior measurements between runs using Instrumentation.reset() to avoid cross-test contamination.",
      "max_score": 10
    }
  ]
}