Fix Google Docs metadata scope for rename and archive

[mohammedahmed18]

Summary

• Request writable Google Drive metadata scope for Google Docs OAuth in the broker, runtime profile, registry, docs, and verification manifest.
• Keep Google Docs precondition checks from blocking title metadata updates when only the Drive numeric version counter changed.
• Update connector, daemon, CLI, and broker tests for the new scope contract.

Test Plan

• cargo fmt --check
• git diff --check
• npm --prefix apps/oauth-service run typecheck
• npm --prefix apps/oauth-service test -- app.test.ts
• cargo test -p locality-google-docs
• cargo test -p locality-auth-core oauth
• cargo test -p localityd --test connector_manifest google_docs_oauth_verification_scope_manifest_matches_runtime_profile -- --exact
• cargo test -p localityd --test source_descriptor resolving_expired_google_docs_credential_refreshes_with_broker_handle -- --exact
• cargo test -p loc-cli --test connect connect_google_docs_broker_oauth_accepts_google_identity_scope_aliases -- --exact

Live Verification

• Created a scratch Google Doc through mounted Markdown with the refreshed Google Docs connection.
• Pushed a frontmatter title rename successfully.
• Verified the refreshed token can trash the scratch Doc through Drive metadata update.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
locality	Ready	Preview	Aug 18, 2026 11:31am