Pin llm-connect to :8088 in CUST-WP-0045 cutover runbook

llm-connect's CLI default port (:8080) collides with the dev stack's
temporal-ui container. Hit during the 2026-06-01 cutover attempt with
OSError: Address already in use. Update Steps 3, 5, and 6 to use :8088
and note the conflict reason inline so the next operator does not
rediscover this the slow way.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

workplans/CUST-WP-0045-cutover-runbook.md

@@ -78,7 +78,7 @@ export ACTCORE_DB_URL=postgresql+asyncpg://actcore:actcore@localhost:5433/actcor
 export TEMPORAL_HOST=localhost:7233
 export TEMPORAL_NAMESPACE=default
 export STATE_HUB_URL=http://127.0.0.1:8000
-export LLM_CONNECT_URL=http://127.0.0.1:8080
+export LLM_CONNECT_URL=http://127.0.0.1:8088   # NOT :8080 — taken by temporal-ui
 export ISSUE_SINK_TYPE=null   # canary must not spawn real tasks
 
 uv run python -m activity_core.worker
@@ -103,9 +103,13 @@ uv run uvicorn activity_core.api:app --host 127.0.0.1 --port 8010
 cd /home/worsch/llm-connect
 export LLM_CONNECT_CLAUDE_CLI_PATH=/home/worsch/.local/bin/claude
 
-uv run python -m llm_connect.server --host 127.0.0.1 --port 8080 --provider claude-code
+uv run python -m llm_connect.server --host 127.0.0.1 --port 8088 --provider claude-code
 ```
 
+Port `:8088` is chosen because the dev stack already binds `:8080` for the
+Temporal UI (`temporal-ui` container). llm-connect's CLI default is `:8080`
+and will `OSError: [Errno 98] Address already in use` if you accept it.
+
 The explicit `LLM_CONNECT_CLAUDE_CLI_PATH` is belt-and-suspenders against the
 2026-05-21 failure (the adapter resolved `/usr/bin/claude` and got the literal
 string `Execution error`).
@@ -113,7 +117,7 @@ string `Execution error`).
 ## Step 6 — Smoke probe llm-connect before risking the full canary
 
 ```bash
-curl -sS -X POST http://127.0.0.1:8080/execute \
+curl -sS -X POST http://127.0.0.1:8088/execute \
   -H "Content-Type: application/json" \
   -d '{
     "prompt": "Return ONLY JSON: {\"ok\": true}",