feat(hub): photo backup moves to its own Android Sync page

A Phone section of the side menu leads to it, on the Android application
only; Settings no longer holds it.

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

1 files changed, 4 insertions, 3 deletions

diff --git a/packages/meshbay-hub/tests/harness/photo_sync_probe.py b/packages/meshbay-hub/tests/harness/photo_sync_probe.py
index 48d9270..08c21b9 100644
--- a/packages/meshbay-hub/tests/harness/photo_sync_probe.py
+++ b/packages/meshbay-hub/tests/harness/photo_sync_probe.py
@@ -1,7 +1,8 @@
 #!/usr/bin/env python3
 """
 The phone's photo backup section (photo-sync-settings.js), rendered in Chrome
-at phone widths with names nobody would choose for a fixture.
+on its page (android-sync-page.js) at phone widths with names nobody would
+choose for a fixture.
 
 Only the Android application has this section, and its engine is Chromium, so
 one engine is the whole of it. The bridge is a stand-in that answers the way
@@ -89,12 +90,12 @@ window.meshbay = {
 import { html, render } from './vendor/htm-preact.js';
 import { initLocale } from './i18n.js';
 import { startPhotoSync } from './photo-sync.js';
-import { PhotoSyncSection } from './photo-sync-settings.js';
+import { AndroidSyncPage } from './android-sync-page.js';
 await initLocale();
 startPhotoSync({ hub: '', getUser: () => ({ username: 'bob', token: 't' }),
                  getBundleKey: async () => '' });
 const groups = [{ id: 'g1', name: '__GROUP__', owner_username: '__OWNER__' }];
-render(html`<${PhotoSyncSection} user=${{ username: 'bob', token: 't' }} groups=${groups} />`,
+render(html`<${AndroidSyncPage} user=${{ username: 'bob', token: 't' }} groups=${groups} />`,
        document.getElementById('root'));
 setTimeout(() => {
   if (MODE === 'configured') return;