Skip to content

Calendar overlay provider push (1.5.0) — Production Readiness Audit ​

FieldValue
Date2026-10-05
Re-verified2026-10-05 — Pest CalendarEventProviderPushTest (8) + Playwright test:e2e:calendar (6) green
StatusGo for production
ScopeOne-way EloSync → Google/Outlook push extended to Meeting / Task / Lead overlays; catalog calendar 1.4.0 → 1.5.0
CompanionCalendar deployment · Overview · Developer guide · CHANGELOG

Executive summary ​

Calendar 1.4.0 already pushed manual events via PushCalendarEventToProviderJob. 1.5.0 opens the same soft-fail path for calendar projections sourced from Meetings, Tasks, and Leads (CalendarEventSourceEnum::shouldPushToProvider()). When an overlay is created, updated, or cleared (soft-delete / cancel), the organizer’s connected providers receive create / update / cancel. Project, Contact, and Company overlays remain deferred. Two-way inbound sync remains deferred.

Known limitation (unchanged from 1.4.0): calendar_events.external_provider / external_event_id store a single provider mapping. Dual-connect (Google + Microsoft) update/cancel only reliably targets the last-written mapping.

GateResult
Platform freezePass (no shell/auth redesign)
Push gate: manual + meeting + task + lead onlyPass (enum + subscriber)
Project / Contact / Company never queuedPass (Pest)
Soft-fail; broken provider never blocks writesPass (existing 1.4.0 path)
Horizon calendar-sync queuePass (unchanged)
Catalog migrate-only 1.5.0 + CatalogSeederPass
SPA Sync copy + Playwright one-sessionPass (calendar-overlay-sync.spec.ts + integrations)
Live Google/Microsoft overlay pushPost-deploy QA

Upgrade & staging smoke ​

  1. php artisan migrate --force — catalog → 1.5.0 (do not db:seed).
  2. Confirm Horizon workers process calendar-sync.
  3. Admin → Calendar → Sync → copy mentions Meeting/Task/Lead overlays.
  4. With OAuth connected: Task with due_at / Lead follow-up / Meeting → provider calendar; clear due or cancel meeting → provider cancel.

Rollback ​

Roll back catalog bump (down → 1.4.0) with matching code. Overlay rows and provider mappings from 1.4.0 remain; after rollback, only manual events push again.

Official documentation for the EloSync SaaS Platform.