fix(ui): single module script + mutable THREE — OrbitControls validated

Browser validation against the previous commit caught two stacked issues:

1. `import * as THREE from 'three'` returns a frozen Module Namespace
   Object — assignment `THREE.OrbitControls = OrbitControls` silently
   no-ops, so the global never gets the OrbitControls reference.

2. Two separate `<script type="module">` blocks (one installing the
   THREE global, one consuming it via Scene) are independently
   async-resolved. The second can finish dependency loading first and
   call `new THREE.OrbitControls(...)` before the first script has run.

Fixed by spreading the namespace into a plain mutable object and merging
all initialization into a single module script with `await import()` for
component modules. Order is now strictly: import THREE → install
window.THREE → import components → run init().

Validated via agent-browser: page logs `[VIZ] Initialization complete`,
WebSocket targets the correct `ws://127.0.0.1:3001/ws/sensing` endpoint
(derived from buildSensingWsUrl), toast lazy-init confirmed via eval.

Co-Authored-By: claude-flow <ruv@ruv.net>

ui/services/websocket-client.js

@@ -1,9 +1,19 @@
 // WebSocket Client for Three.js Visualization - WiFi DensePose
-// Connects to ws://localhost:8000/ws/pose and manages real-time data flow
+// Default endpoint is `/ws/sensing` on the same host the page was served from.
+// Callers (e.g. viz.html) usually pass an explicit `url` derived from
+// `buildSensingWsUrl()` so HTTP/WS port pairings are handled centrally.
+
+function _defaultWsUrl() {
+  if (typeof window === 'undefined' || !window.location) {
+    return 'ws://localhost:8765/ws/sensing';
+  }
+  const protocol = window.location.protocol === 'https:' ? 'wss:' : 'ws:';
+  return `${protocol}//${window.location.host}/ws/sensing`;
+}
 
 export class WebSocketClient {
   constructor(options = {}) {
-    this.url = options.url || 'ws://localhost:8000/ws/pose';
+    this.url = options.url || _defaultWsUrl();
     this.ws = null;
     this.state = 'disconnected'; // disconnected, connecting, connected, error
     this.isRealData = false;

ui/utils/toast.js

@@ -27,6 +27,8 @@ export class ToastManager {
       action = null
     } = options;
 
+    if (!this.container) this.init();
+
     const id = ++this.idCounter;
     const toast = document.createElement('div');
     toast.className = `toast toast-${type}`;

ui/viz.html

@@ -84,22 +84,41 @@
     <div id="stats-container"></div>
   </div>
 
-  <!-- Three.js and OrbitControls from CDN -->
-  <script src="https://unpkg.com/three@0.160.0/build/three.min.js"></script>
-  <script src="https://unpkg.com/three@0.160.0/examples/js/controls/OrbitControls.js"></script>
+  <!-- Three.js r160 dropped examples/js/ UMD builds. Load via importmap and
+       expose THREE + OrbitControls as a mutable global so the existing
+       component modules (scene.js, body-model.js, …) keep working without
+       a wider refactor. Note: `import * as THREE` returns a frozen Module
+       Namespace Object — spread it into a plain object before attaching
+       OrbitControls, otherwise the assignment silently no-ops. -->
+  <script type="importmap">
+  {
+    "imports": {
+      "three": "https://unpkg.com/three@0.160.0/build/three.module.js",
+      "three/addons/": "https://unpkg.com/three@0.160.0/examples/jsm/"
+    }
+  }
+  </script>
   <!-- Stats.js for performance monitoring -->
   <script src="https://unpkg.com/stats.js@0.17.0/build/stats.min.js"></script>
 
-  <!-- Application modules loaded as ES modules via importmap workaround -->
+  <!-- All app code lives in one module so global THREE is installed before
+       the component modules run. Two separate module scripts would race
+       since each is independently async-resolved. -->
   <script type="module">
-    // Import all modules
-    import { Scene } from './components/scene.js';
-    import { BodyModel, BodyModelManager } from './components/body-model.js';
-    import { SignalVisualization } from './components/signal-viz.js';
-    import { Environment } from './components/environment.js';
-    import { DashboardHUD } from './components/dashboard-hud.js';
-    import { WebSocketClient } from './services/websocket-client.js';
-    import { DataProcessor } from './services/data-processor.js';
+    import * as ThreeNS from 'three';
+    import { OrbitControls } from 'three/addons/controls/OrbitControls.js';
+    const THREE = { ...ThreeNS, OrbitControls };
+    window.THREE = THREE;
+
+    // Component modules use `THREE.*` as a global — must be installed first.
+    const { Scene } = await import('./components/scene.js');
+    const { BodyModel, BodyModelManager } = await import('./components/body-model.js');
+    const { SignalVisualization } = await import('./components/signal-viz.js');
+    const { Environment } = await import('./components/environment.js');
+    const { DashboardHUD } = await import('./components/dashboard-hud.js');
+    const { WebSocketClient } = await import('./services/websocket-client.js');
+    const { DataProcessor } = await import('./services/data-processor.js');
+    const { buildSensingWsUrl } = await import('./services/sensing.service.js');
 
     // -- Application State --
     const state = {
@@ -175,9 +194,12 @@
         state.stats = initStats();
         setLoadingProgress(85, 'Connecting to server...');
 
-        // 8. WebSocket client
+        // 8. WebSocket client — derive URL from window.location so the page
+        //    works on both default (HTTP 8080 / WS 8765) and Docker (3000/3001)
+        //    port pairings. `?ws=…` query overrides for advanced setups.
+        const wsOverride = new URLSearchParams(window.location.search).get('ws');
         state.wsClient = new WebSocketClient({
-          url: 'ws://localhost:8000/ws/pose',
+          url: wsOverride || buildSensingWsUrl(),
           onMessage: (msg) => handleWebSocketMessage(msg),
           onStateChange: (newState, oldState) => handleConnectionStateChange(newState, oldState),
           onError: (err) => console.error('[VIZ] WebSocket error:', err)