hadron-server#751 (merged fe88ffb) added the Google Drive surface — the CLI must cover it per the feature-completeness rule (parity umbrella: #134).
New server surface to cover:
- Queries:
driveFiles(connectionRef, folderId?, query?, nameContains?, mimeType?, modifiedAfter?, top?, pageToken?) → DriveFilePage; driveFile(connectionRef, fileId); driveFileExport(connectionRef, fileId, format: MARKDOWN|TEXT|HTML) — suggested commands: hadron drive ls / find / get / export.
- Mutation:
exportNodeToGoogleDoc(nodeRef, connectionRef, folderId?, title?) → DriveFile — suggested: hadron node export-gdoc <nodeRef> --connection <ref> (or a --to gdoc mode on the existing node export command).
- Connections ride the existing ExchangeConnection surface (
provider: 'google-drive') — whatever the CLI already does for gmail/google-cal connection listing applies; the connect flow itself is browser-based (/auth/google-drive).
- Notes:
DriveFile.size is Float (bytes; null for native docs/folders); driveFileExport.content is untrusted external text; grant scope for App-key callers is drive.read (create/export-node is owner-only).
Server context: plan hadron-server#749; tool repo hadron-memory/hadrontool-google-drive. Deploy is pending, so this is not urgent until the tool goes live on alpha — but the surface is final.
hadron-server#751 (merged fe88ffb) added the Google Drive surface — the CLI must cover it per the feature-completeness rule (parity umbrella: #134).
New server surface to cover:
driveFiles(connectionRef, folderId?, query?, nameContains?, mimeType?, modifiedAfter?, top?, pageToken?)→DriveFilePage;driveFile(connectionRef, fileId);driveFileExport(connectionRef, fileId, format: MARKDOWN|TEXT|HTML)— suggested commands:hadron drive ls / find / get / export.exportNodeToGoogleDoc(nodeRef, connectionRef, folderId?, title?)→DriveFile— suggested:hadron node export-gdoc <nodeRef> --connection <ref>(or a--to gdocmode on the existing node export command).provider: 'google-drive') — whatever the CLI already does for gmail/google-cal connection listing applies; the connect flow itself is browser-based (/auth/google-drive).DriveFile.sizeis Float (bytes; null for native docs/folders);driveFileExport.contentis untrusted external text; grant scope for App-key callers isdrive.read(create/export-node is owner-only).Server context: plan hadron-server#749; tool repo hadron-memory/hadrontool-google-drive. Deploy is pending, so this is not urgent until the tool goes live on alpha — but the surface is final.