feat(drive): add drive.replyToComment and drive.resolveComment tools

[matheusrmorgado]

Summary

Fixes #343 by adding the two write-side Drive comment tools, complementing the existing read-only drive.getComments:

• drive.replyToComment(fileId, commentId, content) — posts a reply to an existing comment via replies.create
• drive.resolveComment(fileId, commentId, content?) — marks a comment resolved via replies.create with action: "resolve", optionally posting a closing message

This closes the common agent loop of "read the comments on this doc, address them, reply and resolve" — today the read half exists but the write half requires leaving the extension.

Design notes

• Both tools live in the drive.write feature group and reuse its existing drive OAuth scope — the consent surface is unchanged.
• File IDs accept full URLs (same extractDocumentId normalization as the other Drive tools).
• fields masks limit responses to id/content/author/createdTime (+ action for resolve), matching the getComments field style.

What's included

• Service methods in DriveService following the existing logging/handleError conventions
• Tool registration with Zod schemas (content is min(1) on reply; optional on resolve)
• 6 Jest tests: request shapes for both tools, URL extraction, optional closing message, error paths
• docs/index.md entries

Verification

npm run test && npm run lint && npm run format:check && npx tsc --noEmit --project workspace-server

All passing: 29 suites, 625 tests (619 existing + 6 new), eslint/prettier/tsc clean.

Made with Cursor

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gemini-code-assist]

Code Review

This pull request adds two new tools, drive.replyToComment and drive.resolveComment, along with their respective tests and documentation. The feedback recommends adding the supportsAllDrives: true parameter to the Google Drive API calls to ensure support for Shared Drives, and omitting the content field from the request body in resolveComment when it is not provided. Corresponding test updates are also suggested.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.