feat(registry): add Google Drive plugin

[Finley-Agent-Zhuazhua]

Summary

Adds the googleDrive FastGPT community toolset as a pinned submodule.

• Plugin source: https://github.com/Finley-Agent-Zhuazhua/fastgpt-plugin-googleDrive
• Plugin commit: 975b387bbc14b2c3af3c1e432e75856181e53dd2
• Registry branch commit: 944318145fe631c8a7e60f21d5c379f0e43eeaeb
• Tool IDs: searchFiles, uploadFile, downloadFile, createSharePermission

Tool coverage

• Search Google Drive files by raw Drive query, name text, MIME type, parent folder, pagination token, and trashed-file option.
• Upload text or base64 content with metadata and optional parent folder.
• Download binary Drive files as base64, or export Google Workspace files with exportMimeType; optionally decode UTF-8 text.
• Create sharing permissions for user, group, domain, or anyone targets.

Endpoint safety: the plugin never accepts endpoint overrides. It uses fixed Google Drive API hosts (https://www.googleapis.com/drive/v3 and https://www.googleapis.com/upload/drive/v3) and sends the OAuth access token only as an Authorization header.

Verification

Plugin repo (fastgpt-plugin-googleDrive):

• pnpm install --ignore-workspace ✅
• pnpm run type-check ✅
• pnpm test ✅ — 2 files / 13 tests passed
• pnpm build ✅
• pnpm check ✅
• pnpm run pack ✅ — produced fastgpt-plugin-googleDrive.pkg

Registry repo:

• pnpm validate ✅ ({ "ok": true })
• pnpm test ✅ — 8 files / 34 tests passed
• pnpm type-check ✅
• git submodule status --recursive ✅ — includes packages/tools/googleDrive at 975b387bbc14b2c3af3c1e432e75856181e53dd2

Remote dev debug

Skipped in this scheduled agent run because it requires a live FastGPT remote-debug connection key plus a real Google OAuth access token. Local build, CLI check, package, and mocked Google Drive API tests all passed.

[FinleyGe]

Plugin Review: googleDrive@0.1.0

Verdict: pass
Source: https://github.com/Finley-Agent-Zhuazhua/fastgpt-plugin-googleDrive.git@975b387bbc14b2c3af3c1e432e75856181e53dd2
Plugin root: packages/tools/googleDrive/.

Findings

• None blocking.

Evidence

• registry/submodule: initial review of head 944318145fe631c8a7e60f21d5c379f0e43eeaeb passed pnpm run validate -- --base origin/main --head HEAD with changedPluginIds: ["googleDrive"]; registry entry matches gitlink commit 975b387bbc14b2c3af3c1e432e75856181e53dd2.
• install/build/check/pack: pnpm install --frozen-lockfile --ignore-workspace passed; plugin test files passed with explicit review config (2 files, 13 tests); pnpm run type-check, pnpm run build, pnpm run check, and pnpm run pack passed. After metadata remediation, the same plugin gates were rerun and passed.
• policy scan: MIT license present; plugin-local pnpm-lock.yaml present; no catalog: or workspace: dependency specifiers; no child_process, filesystem write/delete, process.env, eval, private key, or hardcoded secret pattern found. Expected network access uses fixed Google Drive API hosts (www.googleapis.com and upload host) with bearer auth from FastGPT secret input.
• package sha256: 7c3d1109685e44ec595e00dbceb5c519266cde06506625d72a9e9097ddfdc243 googleDrive.pkg

Publish Decision

Proceed

Scheduled Merge Gate

Merged by scheduled run 20260708T140000Z with squash merge locked to remediation head 9f5674d8482fa977fca420caba543023a8c246d3. The automation resolved the mechanical .gitmodules conflict by preserving both the googleDrive and already-merged weaviateVectorStore submodule entries, then reran root validation and plugin gates. GitHub checks were complete and successful, the PR was not draft, no blocking labels/comments/reviews were present, and branch protection allowed normal merge.