Add production rollout tooling and semantic index ops docs

Capture the production plugin rollout workflow and Qdrant validation steps so operations stay repeatable. Also harden redMCP stdio/schema compatibility to keep diverse MCP clients and validators working.

docs/semantic_index_deployment_runbook.md

@@ -53,6 +53,23 @@ docker run -p 6333:6333 -p 6334:6334 \
 Before destructive maintenance, create a Qdrant snapshot or preserve the Docker
 volume.
 
+## WireGuard Topology
+
+Current WireGuard endpoints:
+
+- production server: `10.11.0.100`
+- LAN server: `10.11.0.105`
+
+When Qdrant is hosted on the LAN server, keep it reachable on the WireGuard
+address and point production semantic-index traffic at:
+
+```sh
+QDRANT_URL=http://10.11.0.105:6333
+```
+
+Do not bind production-hosted Qdrant to `10.11.0.105`; that address belongs to
+the LAN host.
+
 ## Environment
 
 For a production-style install, use:
@@ -68,7 +85,7 @@ target host:
 
 ```sh
 OPENAI_API_KEY=
-QDRANT_URL=http://qdrant-host:6333
+QDRANT_URL=http://10.11.0.105:6333
 QDRANT_API_KEY=
 QDRANT_COLLECTION=redmine_semantic_sample
 REDMINE_URL=http://redmine-host