Auto-create Google Calendar event after scheduling a poll

[zhiganov]

Goal

When the creator clicks "Schedule" on a poll, also insert a Google Calendar event into a shared calendar of their choice — picked from a dropdown of their writable calendars in the scheduling toolbar.

This is the missing piece for community workflows where the shared calendar is the source of truth (e.g., sensemakingscenius@gmail.com, where every member is subscribed). Today the creator has to manually copy the time/title/description over after scheduling.

Spec & plan

• Spec: docs/superpowers/specs/2026-05-06-google-calendar-event-creation-design.md
• Plan: docs/superpowers/plans/2026-05-06-google-calendar-event-creation.md

The plan is fully decomposed into 5 tasks with exact code blocks and commands. Execute it with the superpowers:subagent-driven-development skill (one fresh subagent per task) or superpowers:executing-plans (inline batched).

Scope

v1 — in scope:

• Creator picks one of their own writable Google Calendars at schedule time. Inherits write access through their existing membership on the shared calendar — no service account.
• Choice remembered per-creator in localStorage.
• Scope upgrade from calendar.readonly to calendar.events via incremental GIS consent.
• Calendar insert runs after finalizePoll succeeds; calendar failure never rolls back the schedule.

Out of scope (deferred):

• Service-account flow.
• Per-community calendar pre-config — filed as Citizen-Infra/community-admin#12.
• Adding participants as event attendees.
• Auto-cancel/update of the Google event when a poll is unscheduled or re-scheduled (would need lexicon change to track googleEventId).
• Adding a client-side test runner — keep avails' "no client tests, manual smoke" pattern.

Files to change

File	Change
client/src/lib/googleCalendar.js	Add scope constants, parameterise requestGoogleAccess, add listWritableCalendars and insertEvent.
client/src/components/SchedulingGrid.jsx	Add the "Add to" picker / connect link to the toolbar.
client/src/pages/PollView.jsx	Hold writable-calendars + chosen-calendar + token state; persist to localStorage; insert event after finalize; render success link / retry-able error.

No server changes. No lexicon changes. No new dependencies.

Definition of done

1. Plan tasks 1–5 executed, each with its own commit per the plan.
2. Smoke test (plan Task 5) walked end-to-end — happy path, don't-add, localStorage default, OAuth refused, retry, re-schedule orphan.
3. Pushed and deployed to Railway (avails.zhgnv.com).
4. Verified live by scheduling a real poll into the Sensemaking Scenius shared calendar.
5. This issue closed referencing the merge commit.

Follow-up after v1

When/if persisting googleEventId and googleCalendarId on the poll lexicon becomes worth doing, revisit:

• Auto-cancel orphan Google event on handleUnschedule.
• Auto-update on re-schedule.
• Per-community defaults pulled from community-admin#12.

[zhiganov]

Shipped in 13 commits, range 1920da6..b9bcc81.

v1 (6 commits) — full plan executed:

• 461fbe1 googleCalendar.js helpers
• 0aecfc7 SchedulingGrid picker
• b611d5e PollView state wiring
• a64ceb2 follow-up: drop fragile useCallback, clarify call sites
• f0fb7c8 post-finalize calendar insert + retry UI
• cf01147 follow-up: guard Retry button against double-click

v1.1 (7 commits) — pulled forward the spec's deferred work:

• 83be3bd token refresh on Retry (handles GIS 1h expiry)
• 7b86032 lexicon: googleEventId + googleCalendarId
• 2107323 server PUT /:did/:rkey/google-event route + DELETE finalize strips both fields
• 326e4bc client lib helpers
• b8c2fe7 persist event id on poll record after insert
• 32d85ac cancel Google event on unschedule (best-effort, alerts on failure)
• b9bcc81 unit tests for validateGoogleEvent

v1.1 closes the orphan-event gap. Re-schedule and unschedule now auto-cancel the Google event using the persisted ids. If the user has lost Google access between schedule and unschedule, the unschedule still succeeds and the user sees a 'please delete manually' alert — best-effort, matching the existing OpenMeet-slug pattern.

41/41 server tests passing. Closing once smoke-tested on avails.zhgnv.com against a real shared calendar.