Retire CoulombCore references; correct the 16443 diagnosis

CoulombCore is being retired, so the docs stop using it as the reference host:
state-hub-coulombcore examples become state-hub-railiance01, and the reuse-surface
playbook no longer attributes bao.coulomb.social to it — that resolves to
92.205.62.239, which is railiance01. The openrouter lane keeps its factual note
about ESO on the CoulombCore cluster, with a retirement flag for its owner.

Also corrects this session's own error. The WP-0031 evidence blamed the
Unauthorized on a local-port collision between k3s-api-coulombcore and
k3s-api-haskelseed. That was wrong: the haskelseed tunnel is a reverse forward,
where local_port is a destination rather than a listener, so they never competed.
16443 was simply CoulombCore's k3s — a different cluster whose client CA does not
know that cert. The wrong reason had already gone to flex-auth, so it is
corrected in the file rather than quietly dropped.

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

wiki/playbooks/openrouter-llm-connect.md

@@ -54,6 +54,10 @@ the Secret in cluster. The earlier manually created bootstrap Secret has been
 taken over by ESO on the CoulombCore cluster; the railiance01 k3s llm-connect
 instance still uses its bootstrap Secret (separate migration, not this lane).
 
+**Retirement note (2026-08-19):** CoulombCore is being retired, so the ESO-backed
+side of this lane needs to move to railiance01 rather than being the reference
+implementation. Owner is railiance-platform; ops-warden only routes here.
+
 ---
 
 ## Worker checklist