fix(search): preserve Google sync diagnostics and retry transient failures

[waleedlatif1]

Summary

• Preserve Google API operation, HTTP status, and allowlisted error reasons without storing provider payloads. Keep Directory permission failures distinct from file access failures.
• Retry Gmail and Calendar server errors and structured rate-limit responses within the existing transport budget. Preserve authentication, missing-document, and incomplete-directory behavior.
• Store and report database driver codes instead of query text, bound parameters, or raw database causes in both Trigger and in-process document workers. Update Google connector troubleshooting docs.

Type of Change

• Bug fix

Testing

• 569 targeted connector, Directory, diagnostics, and document-processing tests passed, including regressions for retries, bounded error parsing, admission hooks, nested-group denials, both worker paths, and SQL redaction.
• TypeScript, lint, API-contract validation, all 46 repository audits, block-registry validation, and docs-manifest checks passed.
• Reviewed all eight cleanup passes; no client state or UI changes. Runtime diagnostics still require verification after deployment; this does not claim to resolve unclassified upstream access errors.

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.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 16, 2026 10:40pm UTC

[cubic-dev-ai]

No issues found across 24 files

Confidence score: 5/5

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

_{Re-trigger cubic}

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; the previously reported database-detail leak is fixed and no new actionable failures remain.

Summary

This PR improves Google connector retry behavior and preserves bounded, non-sensitive diagnostics across sync and document-processing paths.

• Introduces shared Google API error parsing with allowlisted reason codes and bounded transient retries.
• Distinguishes Directory membership failures from file-access failures.
• Redacts SQL, bound parameters, and raw database causes while retaining safe driver codes.
• Updates Gmail, Calendar, and Drive troubleshooting documentation and adds regression coverage.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Google[Google API] --> Parser[Bounded error parser]
  Parser --> Safe[Allowlisted operation, status, and reasons]
  Safe --> Retry{Transient or rate-limited?}
  Retry -->|Yes| Backoff[Bounded retry transport]
  Retry -->|No| Diagnostic[Connector diagnostic]
  Backoff --> Diagnostic
  Diagnostic --> Worker[Document worker]
  Worker --> Logs[Redacted logs]
  Worker --> State[Safe persisted processing error]

Loading

_{Reviews (2) · Last reviewed commit: "fix(search): sanitize in-process databas..."}

[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 25 files

Confidence score: 5/5

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

_{Re-trigger cubic}