Fixed Meetings

Meetings and appointments keep their time on the night the clocks go back

A meeting, appointment or To-do reminder between 1:00 and 2:00 AM on the night the clocks go back keeps the time it was booked for, and the two 1:30s are two different times.

On the night the clocks go back, 1:00 to 1:59 AM happens twice. Magpie stored a time in that hour without saying which one it was, so a meeting booked for the second 1:30 showed and sent reminders an hour early, a 30-minute meeting starting at the first 1:30 was saved an hour longer, and the second 1:00 and 1:30 were never offered on an Appointments booking page.

Now every meeting, appointment and To-do reminder also stores its time in UTC, so both 1:30s can be booked, each keeps its own time in emails, calendar invitations, Zoom, reminders and the app, and booking one does not block the other. Times already booked in that hour keep the first 1:30, as before.

Internal: migration 11001 adds nullable UTC columns beside bookings.startTime/endTime, the four appointments times and todo_reminders.remindAt (additive; dev sites apply it). ZeroORM models declare the pairs in INSTANTS; MeetingTimezone::fromStorage reads the UTC column when it agrees with the wall-clock column and the wall-clock column otherwise, so rows from an older release read as before. SQL filters stay on the wall-clock columns, widened by an hour where they decide something. bin/backfill-utc-instants.php fills older rows. Plan: docs/plans/UTC_INSTANTS.md.