{
  "context": "Evaluates how well the solution leverages @fluidframework/container-loader to manage container connectivity and synchronization, especially around reconnection flows. Scoring rewards correct use of the loader's connection state, events, and catch-up helper to gate work execution. Emphasis is on package APIs, not general architecture or style.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Connect events",
      "description": "Listens to container connectivity via package events (e.g., container.on(\"connected\"/\"disconnected\")) to trigger queue flushes and state updates instead of custom polling.",
      "max_score": 25
    },
    {
      "name": "Catch-up helper",
      "description": "Uses the package-provided waitContainerToCatchUp (or equivalent exported helper) to block work until the container processes pending ops after connect/reconnect, handling its boolean result or rejection explicitly.",
      "max_score": 30
    },
    {
      "name": "State tracking",
      "description": "Derives reported state from the container's connectivity indicators (connectionState/connected) and updates lastSyncSuccessful only after waitContainerToCatchUp resolves, rather than ad hoc flags.",
      "max_score": 20
    },
    {
      "name": "Queue flushing",
      "description": "Queues work while disconnected and flushes in submission order immediately after a successful waitContainerToCatchUp on reconnect, using container-loader signals rather than timers or manual delays.",
      "max_score": 15
    },
    {
      "name": "Cleanup",
      "description": "Cleans up package event handlers on dispose (using off/removeListener or equivalent) and prevents further waitContainerToCatchUp calls once disposed.",
      "max_score": 10
    }
  ]
}