Push plan to Google Calendar (Feature 16) #127

Merged

approver_agent merged 3 commits from task/push-plan-calendar_5885d2b1-cf06-44ff-abf3-242d7763c3c9 into feature/c53328cb-577c-4aea-b4b2-817acfc3dfeb-google-calendar-sync 2026-10-07 23:27:47 -04:00

Conversation 3 Commits 3 Files Changed 20

+2227 -90

3 Commits

Author	SHA1	Message	Date
dev_agentandClaude Opus 5.5	fb7d8ddff8	Forget pushed event ids when Google Calendar is disconnected (Feature 16) ... Disconnect deleted the connection but left every pushed plan synced with its stored event ids, though no calendar was chosen any more. It now deletes the connection and runs the same invalidation as choosing another calendar (forgetEvents: MarkCalendarPlansEdited, ClearCalendarEvents) in one transaction, under the account lock. A refused revoke still changes nothing. Tests push three weeks, disconnect, and check each is changed with no event id; then connect again, choose a calendar and push the whole week to it. Also: a refused revoke keeps every week synced, and a disconnect during a push waits for its record and then forgets it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-07 23:07:36 -04:00
dev_agentandClaude Opus 5.5	26fde27f54	Forget pushed event ids when another calendar is chosen (Feature 16) ... Choosing a calendar other than the stored one now clears every plan day's calendar_event_id and edits each plan that had one (revision raised, synced -> changed) in the same transaction as the choice, so a stored event id is always on the chosen calendar and the next push writes the whole week there. PushEvents now runs the push's record under the same account-lock hold as its event writes, so the chosen calendar cannot change between the writes and the sync bookkeeping; a push that read a plan before the choice is refused by its revision check (ErrPlanChanged). Fixes review finding F-01 on task 5885d2b1-cf06-44ff-abf3-242d7763c3c9. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-07 22:40:14 -04:00
dev_agentandClaude Opus 5.5	691c1ff34a	Push the week's plan to Google Calendar (Feature 16) ... POST /api/v1/plans/{weekStart}/push-calendar writes one event per plan day to the chosen calendar: "Dinner: {name}" from the household dinner time for 60 minutes in the household zone, with the dinner name, "Start by {time}" for crock-pot dinners and the {MEALQUEST_PUBLIC_URL}/dinner/{id} link. Event ids are the lowercase base32hex SHA-256 of "mealquest|{weekStart}|{date}"; each event is inserted, and a 409 updates it instead. gcal.Service.PushEvents does the Calendar writes under the account lock, with the same redaction as listing. plan.Service.Push records a push only when every event was written: the plan becomes synced with calendar_synced_at and each day stores its event id. A partial failure records nothing; a plan edited mid-push is 409 plan_changed. A swap, or a redraft to another dinner, clears the day's calendar_event_id, so the next push writes just those days; a push with none pending writes every day again. No calendar chosen is 409 no_calendar; a deleted or read-only chosen calendar is 409 calendar_unavailable; a refused grant is 502 reconnect_required, leaving the connection as it is. Maestro task 5885d2b1-cf06-44ff-abf3-242d7763c3c9. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-07 22:12:44 -04:00