Feature 16: Google Calendar Sync (#130)

Co-authored-by: orchestrator-agent <20+orchestrator-agent@code.cubecraftcreations.com>

migrations/0015_google_reconnect_required.sql

@@ -0,0 +1,31 @@
+-- 0015_google_reconnect_required: when Google refuses the stored grant
+-- (invalid_grant on refresh, or HTTP 401 from the Calendar API) the
+-- connection is kept as reconnect required: its refresh token is cleared
+-- and last_sync_error says why. SQLite cannot drop a NOT NULL constraint,
+-- so the table is rebuilt with refresh_token_ct nullable. A row without a
+-- refresh token always carries the reason. No table references
+-- integrations_google.
+
+CREATE TABLE integrations_google_new (
+	id               INTEGER PRIMARY KEY CHECK (id = 1),
+	refresh_token_ct BLOB,
+	calendar_id      TEXT,
+	calendar_name    TEXT,
+	connected_at     TEXT    NOT NULL,
+	last_sync_error  TEXT,
+	created_at       TEXT    NOT NULL,
+	updated_at       TEXT    NOT NULL,
+	CHECK (refresh_token_ct IS NOT NULL OR last_sync_error IS NOT NULL)
+);
+
+INSERT INTO integrations_google_new (
+	id, refresh_token_ct, calendar_id, calendar_name, connected_at,
+	last_sync_error, created_at, updated_at
+)
+SELECT id, refresh_token_ct, calendar_id, calendar_name, connected_at,
+	last_sync_error, created_at, updated_at
+FROM integrations_google;
+
+DROP TABLE integrations_google;
+
+ALTER TABLE integrations_google_new RENAME TO integrations_google;

migrations/queries/plans.sql

@@ -7,7 +7,7 @@ WHERE week_start = ?;
 -- name: ListPlanDays :many
 -- The days of plan plan_id with their dinners, Monday first. A day with
 -- no dinner is left out.
-SELECT plan_days.date, plan_days.is_new, sqlc.embed(dinners)
+SELECT plan_days.date, plan_days.is_new, plan_days.calendar_event_id, sqlc.embed(dinners)
 FROM plan_days
 JOIN dinners ON dinners.id = plan_days.dinner_id
 WHERE plan_days.plan_id = ?
@@ -25,20 +25,59 @@ SET status = ?, ai_note = ?, revision = revision + 1, updated_at = ?
 WHERE id = ?;
 
 -- name: PutPlanDay :exec
--- Plans dinner_id on date of plan_id, keeping the day's calendar event id
--- when the day exists.
+-- Plans dinner_id on date of plan_id. An existing day keeps its calendar
+-- event id while its dinner stays the same; a new dinner clears it, since
+-- Calendar no longer shows the day as planned.
 INSERT INTO plan_days (id, plan_id, date, dinner_id, is_new, created_at, updated_at)
 VALUES (?, ?, ?, ?, ?, ?, ?)
 ON CONFLICT (plan_id, date) DO UPDATE
-SET dinner_id = excluded.dinner_id, is_new = excluded.is_new, updated_at = excluded.updated_at;
+SET dinner_id = excluded.dinner_id, is_new = excluded.is_new,
+	calendar_event_id = CASE WHEN plan_days.dinner_id IS excluded.dinner_id THEN plan_days.calendar_event_id END,
+	updated_at = excluded.updated_at;
 
 -- name: SwapPlanDay :execrows
--- Plans dinner_id on an existing day of plan_id; a date the plan does not
--- have is left as it is (0 rows).
+-- Plans dinner_id on an existing day of plan_id, clearing its calendar
+-- event id since Calendar no longer shows the day as planned; a date the
+-- plan does not have is left as it is (0 rows).
 UPDATE plan_days
-SET dinner_id = ?, is_new = ?, updated_at = ?
+SET dinner_id = ?, is_new = ?, calendar_event_id = NULL, updated_at = ?
 WHERE plan_id = ? AND date = ?;
 
+-- name: SetPlanDayCalendarEvent :execrows
+-- Records that the event calendar_event_id on Calendar shows date of
+-- plan_id as planned.
+UPDATE plan_days
+SET calendar_event_id = ?, updated_at = ?
+WHERE plan_id = ? AND date = ?;
+
+-- name: MarkWeekPlanSynced :execrows
+-- Records a Push to Calendar of plan id as it was at revision: the plan
+-- becomes synced. A plan edited since (another revision) is left as it is
+-- (0 rows).
+UPDATE week_plans
+SET status = 'synced', calendar_synced_at = ?, updated_at = ?
+WHERE id = ? AND revision = ?;
+
+-- name: MarkCalendarPlansEdited :exec
+-- Records that Calendar no longer shows the days with a calendar event id
+-- as planned, since another calendar or none is chosen: every plan with
+-- such a day is edited as MarkWeekPlanEdited does, so a synced plan becomes
+-- changed and a push that read it before is refused.
+UPDATE week_plans
+SET status = CASE WHEN status = 'synced' THEN 'changed' ELSE status END,
+	revision = revision + 1,
+	updated_at = ?
+WHERE EXISTS (
+	SELECT 1 FROM plan_days
+	WHERE plan_days.plan_id = week_plans.id AND plan_days.calendar_event_id IS NOT NULL
+);
+
+-- name: ClearCalendarEvents :exec
+-- Clears every day's calendar event id: none is on the chosen calendar.
+UPDATE plan_days
+SET calendar_event_id = NULL, updated_at = ?
+WHERE calendar_event_id IS NOT NULL;
+
 -- name: MarkWeekPlanEdited :exec
 -- Records an edit of plan id, raising its revision: a synced plan becomes
 -- changed, any other keeps its status.

migrations/queries/settings.sql

@@ -106,6 +106,24 @@ ON CONFLICT (id) DO UPDATE SET
 	updated_at = excluded.updated_at
 RETURNING *;
 
+-- name: SetIntegrationsGoogleCalendar :execrows
+-- Sets the chosen calendar; affects no row when nothing is connected.
+UPDATE integrations_google
+SET calendar_id = ?, calendar_name = ?, updated_at = ?
+WHERE id = 1;
+
+-- name: ClearIntegrationsGoogleToken :execrows
+-- Records that Google refuses the stored grant: clears the refresh token and
+-- sets last_sync_error, keeping the chosen calendar. Affects no row when
+-- nothing is connected.
+UPDATE integrations_google
+SET refresh_token_ct = NULL, last_sync_error = ?, updated_at = ?
+WHERE id = 1;
+
+-- name: DeleteIntegrationsGoogle :exec
+DELETE FROM integrations_google
+WHERE id = 1;
+
 -- name: GetChatSettings :one
 -- Returns sql.ErrNoRows until the row exists.
 SELECT * FROM chat_settings