docs(sync): align google connect flow documentation

[cursor]

Summary

• update existing Google sync/connect docs to match current post-refactor web hook paths
• document connect-later guardrail that syncs pending local IndexedDB events before POST /api/auth/google/connect
• add troubleshooting guidance for the local-events-sync failure toast/abort path

Files updated

• docs/features/google-sync-and-websocket-flow.md
• docs/frontend/frontend-runtime-flow.md
• docs/development/feature-file-map.md
• docs/development/troubleshoot.md

Codepaths covered

• web: useConnectGoogle, syncPendingLocalEvents, useGoogleAuth*, useGoogleLogin
• backend: connectGoogleToCurrentUser, restartGoogleCalendarSync / import websocket lifecycle
• runtime UX: sidebar command/status contract and Google connect troubleshooting

Notes

• docs-only change; no runtime code modifications

  

---

Note

Low Risk
Docs-only updates that don’t affect runtime behavior; risk is limited to potential developer/operator confusion if any described flow details are inaccurate.

Overview
Updates Google auth/sync documentation to match the post-refactor web hook paths (moves references from auth/hooks/oauth/* to auth/hooks/google/*) across the feature file map and frontend/runtime flow docs.

Documents the connect-Google-later guardrail: useConnectGoogle now syncs pending local IndexedDB events via syncPendingLocalEvents(dispatch) before calling POST /api/auth/google/connect, and aborts with a specific toast on failure to avoid local-only events disappearing.

Adds troubleshooting guidance for the new “local events sync error” abort path, clarifying expected backend side effects (no connectGoogleToCurrentUser call and no import restart).

^{Written by Cursor Bugbot for commit dd58bae. This will update automatically on new commits. Configure here.}