{
  "context": "Evaluates how well the solution uses @fluidframework/container-loader to compose loader services and resolve container requests with pending-state recovery. Focus stays on correct Loader construction, resolution calls, and surfacing dependency-provided services described in the spec.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Loader wiring",
      "description": "Creates exactly one @fluidframework/container-loader Loader with urlResolver, documentServiceFactory, and codeLoader from config plus logger/options/protocolHandlerBuilder/scope, storing the instance for reuse instead of recreating it per request.",
      "max_score": 35
    },
    {
      "name": "Resolve requests",
      "description": "Uses Loader.resolve(request, pendingState?) to open containers (not custom fetch logic) and derives the returned resolved URL from the Loader result (e.g., container.resolvedUrl.url or equivalent) rather than echoing the input request URL.",
      "max_score": 25
    },
    {
      "name": "Pending state",
      "description": "Forwards provided pending state strings into Loader.resolve so pending local ops are applied before returning the container, instead of ignoring or reimplementing that behavior.",
      "max_score": 15
    },
    {
      "name": "Expose services",
      "description": "Surfaces loader services (urlResolver, documentServiceFactory, codeLoader, options/logger/protocolHandlerBuilder) and the Loader instance in the gateway output using Loader.services rather than hand-maintained duplicates.",
      "max_score": 15
    },
    {
      "name": "Telemetry/options flow",
      "description": "Ensures logger and loader options are passed through to the Loader (including use of subLogger when applicable) so dependency-provided telemetry and behaviors are leveraged instead of ad hoc replacements.",
      "max_score": 10
    }
  ]
}