Repeating meetings that say when the clocks move

A booking form for Weekly coaching seen from New York: four Mondays at 3:00 AM, the last one marked 1 hour later at 4:00 AM, and a line under them: From Mon, Oct 26 it’s 1 hour later for you, as the clocks change.

A weekly meeting stays at its host’s time. When the clocks change where the host is on one date and where you are on another, one of the meetings lands an hour off for you: 3:00 AM for three weeks, then 4:00 AM. Nothing said so, and it was easy to miss.

Now the booking form marks the meeting that moves, and says from when and by how much. The confirmation, the manage page and every email that lists the meetings say it too, and so does what Tempi tells AI assistants.

Improvements

AI assistants get each meeting of a series in the invitee’s time, not only in UTC.
Every field of every tool AI assistants call says what it is. An id says which kind and which tool lists it, so an assistant no longer passes a slug where an id belongs.
When nobody can book a collective event type because its hosts’ hours never overlap, the dashboard says so, with a link to the event type.
A request’s page tells the host whether it was declined, withdrawn by the invitee, or lapsed.
A series’ confirmation lists one short line per meeting, with the time zone once below, so it fits a phone.
A confirmation’s cover keeps some light for a booking at night, in every page style.
On a phone, team members’ roles and Remove sit under their names.

Fixes

Collective event types offer times when their hosts’ hours start a different amount apart than the meeting’s length, such as 9:00 in Berlin and 9:00 in São Paulo for 45 minutes. Before, they offered none.