Clarify WebSocket usage in docs

Author: BleedingXiko

docs/app/content/docs/framework/realtime.md

@@ -8,6 +8,8 @@ order: 16
 
 SPRAG's realtime layer connects server events to browser handlers over WebSockets. The design follows a simple principle: **signal then refetch**.
 
+The built-in bridge uses the browser's native `WebSocket` API and SPRAG's server-side websocket endpoint. Socket.IO is not part of SPRAG's realtime runtime.
+
 ## Prerequisites
 
 WebSocket server mode requires `gevent-websocket`. If you installed SPRAG with `pip install spragkit`, install it manually:

docs/app/content/docs/guides/deployment.md

@@ -114,7 +114,7 @@ app = App(
 )
 ```
 
-This starts a Socket.IO server alongside the WSGI app. The browser loads the Socket.IO client automatically.
+This serves SPRAG's native websocket endpoint alongside the WSGI app. Browser Modules that use `on_socket(...)`, `emit_socket(...)`, `join_topic(...)`, or `refetch_on_socket(...)` connect through SPRAG's shared runtime bridge.
 
 ## Environment variables
 

docs/app/content/docs/ragot/modules.md

@@ -111,6 +111,8 @@ For advanced ownership patterns, `adopt_component(...)` is also real on the unde
 
 ## Sockets
 
+These methods use SPRAG's shared realtime bridge when the page runs in websocket mode. They do not require a Socket.IO client.
+
 ```python
 def on_start(self):
     # Listen for socket events

docs/app/content/docs/ragot/overview.md

@@ -16,7 +16,7 @@ Under the hood, your compiled code uses:
 - **Keyed list reconciliation** (`renderList`) for `ui.For()` loops
 - **Grid layout engine** (`renderGrid`) for `ui.Grid()` layouts
 - **Lazy loading** (`createLazyLoader`) for `ui.LazyImage()` images
-- **Socket.IO client** for real-time communication
+- **Lifecycle-safe socket binding** for real-time clients supplied by SPRAG or your own browser code
 - **Animation helpers** (`animateIn`/`animateOut`) for CSS transitions
 - **Virtual scrolling** for large lists
 
@@ -26,6 +26,14 @@ You don't interact with any of these directly. They're the compilation targets f
 
 Occasionally you need a browser-only escape hatch. SPRAG exposes those through Python authoring stubs:
 
+### Socket clients
+
+Ragot does not bundle Socket.IO or open a socket connection on its own. Its socket helpers bind handlers to a client object and clean those handlers up with the Module lifecycle.
+
+In normal SPRAG apps, `Module.on_socket(...)`, `Module.off_socket(...)`, `Module.emit_socket(...)`, and topics use SPRAG's shared realtime bridge. That bridge is documented in [Realtime](/docs/framework/realtime/) and uses the browser's native `WebSocket` API.
+
+If you are writing browser-only Ragot code outside SPRAG's bridge, pass a client object with `on`, `off`, and `emit` methods to Ragot's socket helpers. A Socket.IO browser client can fit that shape, but it is an app-level dependency, not a Ragot or SPRAG runtime dependency.
+
 ### Module imports
 
 Declare JS dependencies on the page manifest and use them in your Module: