fix: Change org-gcal to use Google Calendar as authoritative source

Changed from bidirectional "org" mode to "gcal" mode to avoid sync conflicts.
This prevents HTTP 412 errors on recurring events and HTTP 400 errors on
modified events.

Google Calendar is now authoritative:
- org-gcal-managed-newly-fetched-mode: "gcal" (was "org")
- org-gcal-managed-update-existing-mode: "gcal" (was "org")

Benefits:
- No more version conflicts on recurring events
- Cleaner sync without errors
- Google Calendar changes always win

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

1 files changed, 3 insertions, 3 deletions

diff --git a/modules/org-gcal-config.el b/modules/org-gcal-config.el
index db7b1ec7..dc083efe 100644
--- a/modules/org-gcal-config.el
+++ b/modules/org-gcal-config.el
@@ -104,9 +104,9 @@ enabling bidirectional sync so changes push back to Google Calendar."
   (setq org-gcal-remove-api-cancelled-events t)        ;; auto-remove cancelled events
   (setq  org-gcal-update-cancelled-events-with-todo t) ;; todo cancelled events for visibility
 
-  ;; Enable bidirectional sync - treat events as Org-managed so changes push back
-  (setq org-gcal-managed-newly-fetched-mode "org")     ;; New events from GCal are Org-managed
-  (setq org-gcal-managed-update-existing-mode "org")   ;; Existing events become Org-managed
+  ;; Google Calendar is authoritative - avoids sync conflicts
+  (setq org-gcal-managed-newly-fetched-mode "gcal")    ;; New events from GCal stay GCal-managed
+  (setq org-gcal-managed-update-existing-mode "gcal")  ;; GCal wins on conflicts
 
   :config
   ;; Enable plstore passphrase caching after org-gcal loads