feat(android): back text messages up, in a build Play does not get

A Messages section sends the SMS added since the last copy, as restorable
<smses> XML, into <folder>/<account>-messages/YYYY. A play flavor has neither
READ_SMS nor the code that reads messages; full is the default.

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

1 files changed, 5 insertions, 3 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 b9db9f7..2c34af0 100644
--- a/packages/meshbay-hub/src/meshbay_hub/static/phone-sync.js
+++ b/packages/meshbay-hub/src/meshbay_hub/static/phone-sync.js
@@ -1,6 +1,7 @@
-// Contacts backup: a copy of this phone's address book sent to
-// `<folder>/<account>-contacts` of the destination every backup shares
-// (sync-destination.js), once a day when it changed (docs/MESHBAY_DESIGN.md §9.13).
+// 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).
 //
 // 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
@@ -29,6 +30,7 @@ const RETRY_MS = 15 * 60 * 1000;
  */
 export const KINDS = {
   contacts: { sync: platform.contactSync, heading: 'contactsync.heading', suffix: 'contacts' },
+  messages: { sync: platform.messageSync, heading: 'messagesync.heading', suffix: 'messages' },
 };
 
 // Refusals that will hold at the next run too: said once (a notification,