{
  "context": "Evaluates how the solution uses pygsheets to operate inside a shared drive: authorizing the client, turning on shared-drive support, creating spreadsheets in shared-drive folders, moving them between folders, and listing them with shared-drive scoping. Checks that the implementation leans on pygsheets' Drive helpers instead of custom HTTP calls.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Authorize client",
      "description": "Initializes the pygsheets Client via `pygsheets.authorize(...)` (or equivalent pygsheets helper) instead of constructing Drive/Sheets HTTP calls manually.",
      "max_score": 20
    },
    {
      "name": "Enable drive",
      "description": "Calls `client.drive.enable_team_drive(shared_drive_id)` (or sets `client.teamDriveId`) before performing shared-drive operations so Drive requests include the shared-drive context.",
      "max_score": 20
    },
    {
      "name": "Create in folder",
      "description": "Creates the spreadsheet using `Client.create(...)` with the `folder` or `folder_name` argument pointing to the shared-drive folder, relying on pygsheets instead of manual Drive requests.",
      "max_score": 20
    },
    {
      "name": "Move file",
      "description": "Uses `client.drive.move_file(file_id, old_folder=..., new_folder=...)` (or pygsheets' `move_file` equivalent) to relocate a spreadsheet between shared-drive folders rather than recreating it.",
      "max_score": 20
    },
    {
      "name": "List scoped",
      "description": "Lists spreadsheets with pygsheets APIs such as `client.spreadsheet_titles(...)` or `client.drive.spreadsheet_metadata(...)` after enabling the shared drive, ensuring results come from the shared drive (e.g., by using drive-specific query/corpora flags and not personal-drive defaults).",
      "max_score": 20
    }
  ]
}