docs(bindings-roadmap): use wss:// to satisfy Semgrep insecure-websocket rule

The bindings-roadmap mentioned `ws://` as the URI scheme for a WebSocket
binding entry. Semgrep's `javascript.lang.security.detect-insecure-websocket`
rule scans prose + table cells and flagged this as a CI failure on PR#410.

Per estate-wide secure-protocols-in-docs policy (2026-05-28), all
transport schemes in authored content must default to the encrypted
variant. Updated the wording from "raw `ws://`" to "encrypted `wss://`".

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: hyperpolymath

docs/bindings-roadmap.adoc

@@ -135,7 +135,7 @@ Surface that other estate repos are actively wanting.
 |`http-capability-gateway` shipped Zig server (PR#23); AffineScript-side server bindings would let `.affine` programs serve HTTP without Zig.
 
 |14
-|*WebSocket client + server* (raw `ws://`, separate from Phoenix)
+|*WebSocket client + server* (encrypted `wss://`, separate from Phoenix)
 |`○`
 |`affinescript-websocket`
 |Generalisation of #6; multiplayer + dev-tooling.