feat: node workflow redesign — wizard auto-config, reset, MusicBrainz contact

Wizard (Electron):
- Auto-provisions node config (hub URL + username) from logged-in user
- node:start handles both cold start and restart of misconfigured daemon
- Waits for daemon to reach 'running', auto-links node key on hub
- probeNode accepts intermediate states for wizard progress feedback

Reset (meshbay-node reset):
- Unlinks node key from hub (DELETE /me/node_key, best-effort)
- Stops and disables daemon (systemctl --user disable --now)
- Erases ~/.config/meshbay, ~/.local/share/meshbay, ~/.local/state/meshbay

MusicBrainz contact:
- Resolved from owner's hub email instead of per-node roster config
- Removed musicbrainz_contact UI and WebRTC handshake field
- Removed set_musicbrainz_contact/musicbrainz_contact from roster

Node pairing:
- Added operator pairing banner on NodePage
- Added operator_paired flag to list_groups

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

1 files changed, 2 insertions, 19 deletions

diff --git a/packages/meshbay-node/src/meshbay_node/roster.py b/packages/meshbay-node/src/meshbay_node/roster.py
index d6dc769..ff5282d 100644
--- a/packages/meshbay-node/src/meshbay_node/roster.py
+++ b/packages/meshbay-node/src/meshbay_node/roster.py
@@ -705,25 +705,8 @@ class Roster:
         await self.set_setting(group_id, self.SETTING_TMDB_ENABLED,
                                "1" if enabled else "0", set_by)
 
-    # The Music app's MusicBrainz contact string (docs/musicbay.md §3.2) —
-    # node-wide, under the same group_id="" sentinel as the TMDB token/
-    # language above, for the identical reason: one operator's User-Agent
-    # identity, not a per-group concern. Unlike TMDB there is no secret to
-    # store — this is the contact MusicBrainz's usage policy asks a client
-    # to identify itself with, not a credential. Unset means "no contact
-    # configured", which musicbrainz.py treats as "make no calls at all"
-    # (docs/musicbay.md §3.1) rather than sending an unidentified client.
-    SETTING_MUSICBRAINZ_CONTACT = "musicbrainz_contact"
-
-    async def musicbrainz_contact(self) -> str | None:
-        return await self.get_setting(
-            self.NODE_WIDE_GROUP_ID, self.SETTING_MUSICBRAINZ_CONTACT) or None
-
-    async def set_musicbrainz_contact(self, contact: str | None = None, set_by: str = "") -> None:
-        """`contact=""` clears it; `contact=None` leaves it unchanged (tmdb_config's shape)."""
-        if contact is not None:
-            await self.set_setting(self.NODE_WIDE_GROUP_ID, self.SETTING_MUSICBRAINZ_CONTACT,
-                                   contact, set_by)
+    # MusicBrainz contact is now the node owner's hub email, resolved at
+    # login (musicbrainz.py) — no roster setting needed.
 
     # Whether MusicBrainz lookups run for this group at all — per-group from
     # the start (unlike tmdb_enabled, which started node-wide and moved