Record the calendar migration as complete and deployed #16

2026-09-06T21:53:01Z

Paddy commented

2026-09-06 21:53:01 +00:00

Every step is live as of 2026-09-06. The status header said "awaiting deploy",
which is exactly the kind of staleness that nearly caused a bad deploy earlier
in this project - the step 4 checklist was written because "done" had been read
as "in production".

Also records the one surprise from the deploy: a cached pre-cutover bundle
looked signed in and showed every event's status as "Error", because the
legacy checkSessionValid route still answered between steps 4 and 5 while the
events call went out without a cookie and came back without a status field.
That route is gone now, so a stale bundle fails honestly instead.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com

Every step is live as of 2026-09-06. The status header said "awaiting deploy", which is exactly the kind of staleness that nearly caused a bad deploy earlier in this project - the step 4 checklist was written because "done" had been read as "in production". Also records the one surprise from the deploy: a cached pre-cutover bundle looked signed in and showed every event's status as "Error", because the legacy checkSessionValid route still answered between steps 4 and 5 while the events call went out without a cookie and came back without a status field. That route is gone now, so a stale bundle fails honestly instead. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Paddy added 1 commit 2026-09-06 21:53:02 +00:00

Record the calendar migration as complete and deployed 69c1e4926c

Every step is live as of 2026-09-06. The status header said "awaiting deploy",
which is exactly the kind of staleness that nearly caused a bad deploy earlier
in this project - the step 4 checklist was written because "done" had been read
as "in production".

Also records the one surprise from the deploy: a cached pre-cutover bundle
looked signed in and showed every event's status as "Error", because the
legacy checkSessionValid route still answered between steps 4 and 5 while the
events call went out without a cookie and came back without a status field.
That route is gone now, so a stale bundle fails honestly instead.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Paddy merged commit 3fc6894070 into master

2026-09-06 21:53:12 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Nachklang/API#16