[docs] correct Nostur onboarding to working wss endpoint (#180)

docs/operator-comms-onboarding.md

@@ -21,14 +21,16 @@ Today:
 - Telegram is still the legacy human command surface
 - Matrix/Conduit is not yet deployed
 
-Verified live relay:
-- relay host: `167.99.126.228`
-- relay URL: `ws://167.99.126.228:2929`
-- probe result: HTTP root returns `Timmy Foundation NIP-29 Relay. Use a Nostr client to connect.`
+Verified live relay path:
+- relay backend host: `167.99.126.228:2929`
+- operator relay URL: `wss://alexanderwhitestone.com/relay/`
+- websocket probe result: `wss://alexanderwhitestone.com/relay/` CONNECTED
+- backend HTTP probe on `http://167.99.126.228:2929/` returns `Timmy Foundation NIP-29 Relay. Use a Nostr client to connect.`
 
 Non-target relays:
 - `167.99.126.228:7777` is not the current operator onboarding target
 - `167.99.126.228:3334` is not the live relay to use for Nostur onboarding right now
+- raw `ws://167.99.126.228:2929` is backend truth, not the preferred operator-facing URL when `wss://alexanderwhitestone.com/relay/` is working
 
 ## What to use right now
 
@@ -41,7 +43,7 @@ Use Nostur for:
 - sovereign mobile access
 
 Add this relay in Nostur:
-- `ws://167.99.126.228:2929`
+- `wss://alexanderwhitestone.com/relay/`
 
 Working rule:
 - Nostur gets you into the system
@@ -69,10 +71,11 @@ Do not treat it as the destination architecture.
 
 1. Open Nostur
 2. Add relay:
-   - `ws://167.99.126.228:2929`
+   - `wss://alexanderwhitestone.com/relay/`
 3. Confirm the relay connects successfully
-4. Use Nostur as your sovereign mobile edge for operator ingress
-5. When work is actionable, make sure it is mirrored into Gitea
+4. Verify your logged-in key matches your operator npub
+5. Use Nostur as your sovereign mobile edge for operator ingress
+6. When work is actionable, make sure it is mirrored into Gitea
 
 ## Channel authority, simplified