[prod] HTTPS browser can dial terminal agent #3

[Suji2007hub]

README.md: added a single end-to-end hosted HTTPS production runbook (tunnel/public WSS path) and clarified local vs production multiaddr usage.
p2p-X/web/src/lib/p2p.js: improved HTTPS connectToAgent / convertMultiaddrForSecureContext error handling to make WebRTC/HTTPS failures actionable (localhost/127.0.0.1 reachability, insecure ws/mixed content, NAT/STUN/TURN).
p2p-X/web/src/lib/components/PeerConnect.svelte: updated the agent multiaddr help text to clearly distinguish local HTTP /ws vs hosted HTTPS requirements.
p2p-X/web/app/index.js: terminal agent now prints a hosted-UI copy/paste dial multiaddr at startup via AGENT_PUBLIC_MULTIADDR (or an AGENT_PUBLIC_WS_HOST + AGENT_PUBLIC_WS_PORT candidate hint), so the deployed https:// UI can dial a reachable address.

[Nkovaturient]

@Suji2007hub : great, could you demo it and present a snapshot of logs?

Start the agent and copy the multiaddr that uses a reachable public IP/hostname and **WSS**.: once test and inspect browser logs to see if this agent's multiaddr could be connected here https://llmesh.vercel.app/

Expected: 1. Follow runbook (tunnel or public listen).
2. Vercel UI → MESH SYNCED → chat + window.testExtension('alien-x-llm', 'chat', ['hi']) OK.