tento-google

tento-google contains Google API clients, OAuth credentials, generated-ish type models, and the optional Google Calendar connector surface used by Lona integrations.

Public surface

• api::Client creates typed service clients from an access token or valid OAuth handle.
• types::{calendar, calendar_list, event, event_time, notification, watch} own Google Calendar request and response shapes.
• gmail::GmailApi owns Gmail-specific calls.
• types::gemini contains Gemini request/response models used by tento-ai.
• oauth::{GoogleOAuthCredentials, GoogleOAuthApp} owns Google credential handling.
• scopes::{GoogleScope, GoogleScopes} centralizes scope parsing and validation.
• connector is available behind features = ["connector"] and maps Google Calendar event rowkeys onto tento-lona-connector.

Boundaries

The default crate is a Google SDK. It should not depend on Lona host data, lona-sync, or application row stores. Calendar sync tokens, event mapping, and persistence stay host-side today; the connector delegates those operations through GoogleBackendDeps.

Application code should prefer typed service clients and scope constants over raw endpoint paths, raw OAuth scope strings, or untyped JSON payloads. When a Google workflow becomes shared, add a typed client method or model here instead of duplicating Google API details in callers.