feat(android): back the calendars up as an iCalendar file

A Calendar section sends every calendar the person can edit, as a dated .ics,
into <folder>/<account>-calendar once a day when it changed.

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

1 files changed, 6 insertions, 4 deletions

diff --git a/packages/meshbay-hub/src/meshbay_hub/static/phone-sync.js b/packages/meshbay-hub/src/meshbay_hub/static/phone-sync.js
index 2c34af0..4e9245a 100644
--- a/packages/meshbay-hub/src/meshbay_hub/static/phone-sync.js
+++ b/packages/meshbay-hub/src/meshbay_hub/static/phone-sync.js
@@ -1,7 +1,8 @@
-// Contacts and messages backup: a copy of this phone's address book, and the
-// text messages added since the last copy, sent to `<folder>/<account>-contacts`
-// and `-messages` of the destination every backup shares (sync-destination.js),
-// once a day when there is something new (docs/MESHBAY_DESIGN.md §9.13).
+// Contacts, calendar and messages backup: a copy of this phone's address book
+// and calendars, and the text messages added since the last copy, sent to
+// `<folder>/<account>-contacts`, `-calendar` and `-messages` of the destination
+// every backup shares (sync-destination.js), once a day when there is
+// something new (docs/MESHBAY_DESIGN.md §9.13).
 //
 // The same split as photos (photo-sync.js): the phone writes what is new into
 // one file and remembers what the node took; this module decides when a run
@@ -30,6 +31,7 @@ const RETRY_MS = 15 * 60 * 1000;
  */
 export const KINDS = {
   contacts: { sync: platform.contactSync, heading: 'contactsync.heading', suffix: 'contacts' },
+  calendar: { sync: platform.calendarSync, heading: 'calendarsync.heading', suffix: 'calendar' },
   messages: { sync: platform.messageSync, heading: 'messagesync.heading', suffix: 'messages' },
 };