{
  "context": "Evaluates how well the solution leverages @fluidframework/container-loader lifecycle signals to mirror container dirty state, closure semantics, and readonly/connection transitions. Scoring checks event subscriptions and teardown logic rather than general coding style. Engineers familiar with IContainer events should satisfy these quickly.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Dirty hooks",
      "description": "Subscribes to IContainer.on(\"dirty\") and IContainer.on(\"saved\") (and/or reads container.isDirty) to flip the adapter's dirty flag and invoke dirty/saved callbacks directly from those events.",
      "max_score": 25
    },
    {
      "name": "Close vs dispose",
      "description": "Listens to IContainer.on(\"closed\") separately from IContainer.on(\"disposed\") and passes the correct disposed flag plus any error/reason payload from those events to close callbacks.",
      "max_score": 25
    },
    {
      "name": "Readonly capture",
      "description": "Uses IContainer.on(\"readonly\") to detect readonly transitions (including forced readonly) and records the readonly state/reason instead of inferring it from connection alone.",
      "max_score": 20
    },
    {
      "name": "Connection tracking",
      "description": "Attaches to IContainer.on(\"connected\") and IContainer.on(\"disconnected\") to keep callbacks informed about live connectivity and to annotate readonly events that occur while disconnected.",
      "max_score": 15
    },
    {
      "name": "Subscription cleanup",
      "description": "Implements teardown by removing IContainer listeners (off/removeListener) so no callbacks fire after stop is invoked.",
      "max_score": 15
    }
  ]
}