fix(search): isolate unavailable Calendar accounts

[waleedlatif1]

Summary

• Treat Calendar's explicit notACalendarUser response as a known per-account listing failure so unavailable accounts do not trigger the crawl-wide unknown-error pause.
• Keep deferred retries and reconciliation safeguards, with unchanged handling for incomplete, unknown, authentication, scope, and quota errors.

Type of Change

• Bug fix

Testing

• Reproduced the classification failure and healthy-account starvation before the fix; both regression tests pass after it.
• 157 focused Calendar, Google Workspace, and scheduler tests pass, including deferred-account recovery and mixed-error guards.
• App type-check, lint, all 46 repository audits (including API boundary validation), block registry, and docs manifest checks pass.

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 18, 2026 7:02am UTC

[cubic-dev-ai]

No issues found across 3 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 new classification is narrowly gated and preserves the scheduler’s retry and reconciliation safeguards.

Summary

This PR extends Calendar’s existing per-account failure isolation to recognize explicit notACalendarUser responses.

• Restricts isolation to complete HTTP 403 failures from calendar.events.list.
• Preserves propagation for incomplete, mixed, authentication, scope, quota, and unrelated failures.
• Adds crawl-level and scheduler-level regression coverage for healthy-account progress, deferred retries, and reconciliation safety.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Calendar events list error] --> B{403 with complete non-empty reasons?}
    B -- No --> C[Propagate error]
    B -- Yes --> D{Every reason is forbidden or notACalendarUser?}
    D -- No --> C
    D -- Yes --> E[Record per-account listing failure]
    E --> F[Continue crawling healthy accounts]
    E --> G[Mark reconciliation unsafe]
    E --> H[Retry unavailable account later]

Loading

_{Reviews (1) · Last reviewed commit: "fix(search): isolate unavailable Calenda..."}