fix(search): resume Google crawls around unavailable accounts

[waleedlatif1]

Summary

• Persist crawl and permission progress in a shared connector-partition store so slow or unavailable Google accounts do not block healthy users. Provider adapters validate bounded context; retries, cadence, and permission filtering are preserved.
• Bound Google token retries, retain safe error diagnostics, avoid unnecessary OCR on Git LFS pointers, and reduce lifecycle lock contention during document recovery.
• Update the Google Search guides and add PostgreSQL regression coverage to CI.
• Apply the additive migration before deploying updated sync workers. New workers adopt existing provider checkpoints. Older workers safely restart new-format crawls on rollback, so mixed-version takeovers do not preserve progress.

Type of Change

• Bug fix

Testing

• 1,383 targeted unit tests passed; one database-gated test skipped.
• 63 disposable PostgreSQL integration tests passed, including checkpoint replay, permission safety, locking, recovery, and atomic embedding writes.
• Verified the actual migration against the previous schema, including old-code CRUD compatibility, metadata bounds, and forward/rollback checkpoint handling for all three Google providers.
• Cleanup, typecheck, lint, 46 repository audits, API boundary validation, docs manifest, and migration safety checks passed.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Sep 17, 2026 7:37pm UTC

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; all previous findings are resolved and the latest changes introduce no new actionable issues.

Summary

This PR makes Google Workspace central crawls durable on a per-user basis so unavailable accounts no longer block healthy users or cause unread data to be reconciled as absent.

• Persists partitioned content and permission progress with bounded retry scheduling and legacy-checkpoint adoption.
• Preserves permission safety during refreshes and document recovery.
• Bounds delegated-token retries and propagates cancellation through token exchange.
• Adds migration, PostgreSQL integration coverage, CI execution, and updated Google Search documentation.
• The latest changes add the previously missing interface TSDoc and strengthen regression coverage for rejected ACL writes and stale permission evidence.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  S[Google company crawl scheduler] --> D[Discover Workspace users]
  D --> P[(Connector partition store)]
  P --> U[Select eligible user work]
  U --> T[Obtain delegated token]
  T --> L[List content or permissions]
  L --> C[Atomically save cursor and status]
  C -->|More work| P
  C -->|Temporary or account-specific failure| R[Persist bounded retry time]
  R --> P
  C -->|Partition complete| E[Continue healthy users]
  E --> F[Complete generation and reconcile safe absence]

Loading

_{Reviews (4) · Last reviewed commit: "fix(search): clear unverifiable placehol..."}

[cubic-dev-ai]

All reported issues were addressed across 49 files

<sub>Tip: instead of fixing issues one by one fix them all with cubic

Re-trigger cubic</sub>

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 49 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.

Re-trigger cubic</sub>

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

All reported issues were addressed across 51 files

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 51 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}