{
  "context": "Evaluates whether the implementation relies on pygsheets for Drive permissions and file controls. Checks use of built-in sharing/removal helpers, permission retrieval, Drive move via the client, and export tooling to meet the spec's behaviors.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Grant via share",
      "description": "grant_access delegates to pygsheets Spreadsheet.share with the provided email, role, and recipient type (e.g., typ='user'), optionally passing sendNotificationEmail, instead of manual HTTP calls.",
      "max_score": 25
    },
    {
      "name": "Revoke via API",
      "description": "revoke_access uses Spreadsheet.remove_permission for the email and handles CannotRemoveOwnerError appropriately rather than bypassing pygsheets permission helpers.",
      "max_score": 20
    },
    {
      "name": "Permission summary",
      "description": "Permission data returned from grant/revoke is sourced from Spreadsheet.permissions (or equivalent pygsheets permission fetch) and mapped to the spec's PermissionEntry fields without inventing custom caches.",
      "max_score": 15
    },
    {
      "name": "Move with Drive",
      "description": "move_to_folder leverages the pygsheets Client.drive (Drive files API) to update parents (e.g., files().update with addParents/removeParents) and returns the resulting file webViewLink/parents rather than constructing URLs manually.",
      "max_score": 20
    },
    {
      "name": "Export via export",
      "description": "export_spreadsheet calls Spreadsheet.export with file_format=ExportType.PDF (or matching MIME) and path/filename options to write the output_path, avoiding ad-hoc download logic.",
      "max_score": 20
    }
  ]
}