docs: update google repair/import websocket documentation

[cursor]

Summary

• Updated docs/features/google-sync-and-websocket-flow.md with the latest repair UX behavior and websocket payload contract.
• Updated docs/development/troubleshoot.md with a focused runbook for Google repair failures.

What changed

• Documented IMPORT_GCAL_END payload shape with explicit operation: "REPAIR" | "INCREMENTAL" and status-specific fields.
• Added operation-aware handling semantics for the web client (useGcalSync, sync slice, useConnectGoogle) including repair-specific spinner state and toast de-dup behavior.
• Added verified repair failure message semantics for quota/rate-limit vs generic repair errors.
• Clarified revoked-token behavior during repair (invalid_grant => prune + GOOGLE_REVOKED), including the absence of an IMPORT_GCAL_END errored payload in that path.
• Added troubleshooting steps for quota-limited repairs and revoked-token repairs.

Codepaths covered

• packages/core/src/types/websocket.types.ts
• packages/backend/src/user/services/user.service.ts
• packages/backend/src/sync/services/sync.service.ts
• packages/backend/src/common/services/gcal/gcal.utils.ts
• packages/backend/src/common/errors/integration/gcal/gcal.errors.ts
• packages/web/src/socket/hooks/useGcalSync.ts
• packages/web/src/auth/hooks/oauth/useConnectGoogle.ts
• packages/web/src/ducks/events/slices/sync.slice.ts

Why

PR #1580 changed repair UX and the sync completion contract; existing docs did not clearly explain operation-specific websocket payloads, repair error semantics, or expected operator troubleshooting paths.

  

---

Note

Low Risk
Documentation-only changes that clarify websocket payloads and operational repair failure modes; no production code behavior is modified.

Overview
Updates Google sync documentation to define the new IMPORT_GCAL_END payload contract (adds operation: "REPAIR" | "INCREMENTAL" and status-specific fields) and to spell out operation-aware client handling semantics for completion, refetching, and repair-specific toasts/spinner state.

Adds a troubleshooting runbook for Google Calendar repair failures, including guidance for quota/rate-limit errors vs revoked-token (invalid_grant) behavior, and notes that revoked-token repair exits via GOOGLE_REVOKED without an IMPORT_GCAL_END errored payload.

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