{
  "context": "Evaluates how well the solution uses pygsheets authentication and client configuration to build the requested SheetsSession, including scope management, retries/validation knobs, and fetching metadata to prove access. Scoring ignores general code style and focuses only on concrete pygsheets API usage tied to the spec.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Service auth",
      "description": "Calls pygsheets.authorize with service_account_file or service_account_env_var/service_account_json to create a Client and includes the spreadsheets scope by default, merging any custom scopes passed through the API.",
      "max_score": 30
    },
    {
      "name": "Drive scope toggle",
      "description": "Adds the Drive scope (e.g., https://www.googleapis.com/auth/drive or pygsheets.DRIVE) to the authorize call only when enable_drive is True and surfaces drive access through the resulting client.drive helper.",
      "max_score": 25
    },
    {
      "name": "Retry and check",
      "description": "Forwards retries and validation settings to pygsheets.authorize (using retries and check parameters) so that retries are honored and eager quota checks are skipped when validate is False.",
      "max_score": 15
    },
    {
      "name": "Access verification",
      "description": "Uses the pygsheets Client to open the spreadsheet by key (client.open_by_key/open) to retrieve Spreadsheet.title and count worksheets for sheet_count, deferring this call until verify_access runs when validate is False.",
      "max_score": 20
    },
    {
      "name": "Drive status signal",
      "description": "Implements drive_available using the presence/availability of client.drive or client.drive.enabled rather than custom flags, returning False when the Drive scope was not added.",
      "max_score": 10
    }
  ]
}