2.14.0

Repeating events now export as repeating events.

• "Download iCal" and "Add to Google Calendar" on a repeating event hand over the series rather than the single night that was clicked, so a weekly night is saved once instead of every week.
• The series is described from the night being viewed forward, never from the series start: no past dates are written into anyone's calendar, and DTSTART is a real instance of the rule as RFC 5545 requires.
• Events with a recurrence rule are described from that rule. Events imported from another calendar carry no rule — their dates came from the source system rather than from a pattern — so the pattern is recovered from the dates themselves: weekly and every-N-weekly, monthly on a date, and monthly on the nth weekday, with skipped nights carried through as exceptions.
• Where no pattern fits, the .ics lists the dates outright rather than inventing a rule, and the Google Calendar link stays a single date. A wrong rule would put nights in a visitor's calendar the venue is not open for.
• The Google Calendar link carries the rule but not the exceptions: its format allows one line and a URL cannot hold a line break, so the .ics is the faithful export of the two.
• A series is identified by the event rather than by the night it was saved from, so saving the same weekly from two different rows updates one entry instead of duplicating every night. Single dates are unchanged.