{
  "context": "This checklist evaluates how well the solution captures and replays pending Fluid container operations using the container-loader pending local state APIs, ensuring recovery paths prefer the package utilities over custom logic. Scoring prioritizes correct use of capture, storage, recovery, and cleanup helpers from the package.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Capture pending",
      "description": "Uses the container alpha surface (asLegacyAlpha().getPendingLocalState()) to serialize pending local ops before shutdown when unsent changes exist.",
      "max_score": 25
    },
    {
      "name": "Store handling",
      "description": "Persists and clears the serialized blob via PendingLocalStateStore (or equivalent store instance from the package) keyed by session id instead of ad-hoc storage.",
      "max_score": 20
    },
    {
      "name": "Resume from blob",
      "description": "When a stored blob exists, loads a frozen container via loadFrozenContainerFromPendingState (or matching pending-load helper) rather than normal load, and returns the resumed container.",
      "max_score": 25
    },
    {
      "name": "Fresh fallback",
      "description": "If no pending blob is found, performs a standard Loader-based load/resolve path (e.g., Loader.resolve or loadExistingContainer) without invoking pending recovery APIs.",
      "max_score": 10
    },
    {
      "name": "Catch-up gate",
      "description": "After a pending-state load, waits for the container to connect and uses waitContainerToCatchUp (or equivalent ordering-service catch-up helper) before considering recovery complete.",
      "max_score": 10
    },
    {
      "name": "Post-recovery cleanup",
      "description": "Clears the PendingLocalStateStore entry once recovery and catch-up succeed so subsequent loads do not replay stale operations.",
      "max_score": 10
    }
  ]
}