- Shipped
- September 2, 2026 at 7:29 AM UTC
- Author
- Kamo
- Commit
- 44e8458
Saving an event told nobody. The guest list was materialized and the audience stored, and the people on it heard nothing until a reminder fired — which reaches a member in-app and reaches an outside address never. So a member could invite a client to a meeting, watch the name appear on the guest list, and the client would simply never be told. Nor could a guest see the meeting. Visibility was decided by the owning calendar alone, so an event on the organiser's calendar was invisible to everyone invited to it. **************** has had a switch in Calendar Preferences and a column behind it since that screen shipped, and nothing has ever read it. The event carries the choice — whether to invite, and by email, chat, or both — because an edit six weeks later that adds a guest has to know whether this is a meeting that invites people. The guest row carries when it was last told and at which SEQUENCE, which is what makes "a guest added later gets an invitation to the same meeting" correct across any number of edits: deriving it from whichever rows a save inserted is right exactly once. Visibility gains an invited-guest branch through an explicit LEFT JOIN, gated on that preference via a member id nothing can match. One row rather than a copy per guest: one RSVP, and an organiser moving the meeting moves it for everybody. The LEFT JOINs are load-bearing — the organisation calendar has no owning member, so an implicit path expression drops every shared-company event, the trap findBusyForMember already documents.