Evaluate optional live Google Calendar synchronization

[ZFordDev]

Purpose

Determine whether live Google Calendar synchronization is practical and appropriate after offline iCalendar import is established. This is a feasibility and architecture issue, not authorization to require an online account.

Questions to resolve

• OAuth client registration, consent-screen, token-storage, and distribution requirements.
• Read-only versus two-way synchronization.
• Conflict, deletion, recurrence, timezone, and duplicate semantics.
• Manual sync versus background polling and platform restrictions.
• Privacy disclosure, network indicators, offline behavior, and account removal.
• Whether ongoing API and credential maintenance is acceptable for the project.

Exit criteria

• A documented recommendation: implement, defer, or reject.
• A minimal secure architecture if implementation is recommended.
• Clear separation between local-only use and connected use.
• No Google dependency in core, Lite, or CLI-only installations unless explicitly needed.
• Concrete implementation issues are created only after feasibility is confirmed.

Dependency

Complete or stabilize standard iCalendar import first.