Route issue-core directly on railiance01

docs/issue-core-emission-boundary.md

@@ -78,23 +78,19 @@ activity-core.
   Railiance production uses `state-hub` unless an overlay explicitly sets
   `rest` for an experiment.
 
-### Known production failure (2026-07-21, reconfirmed 2026-07-21 T06) — rest path
+### Production direct path (verified 2026-08-19)
 
-`POST /issues/` returns **HTTP 503**:
+Railiance uses the private cluster-local endpoint:
 
 ```text
-Failed to connect to backend 'forgejo-inbox': Failed to connect to Gitea API
+http://issue-core.issue-core.svc.cluster.local:8765
 ```
 
-(Historical error string from the Forgejo-compatible client library — the
-deployed forge is **Forgejo**, not Gitea.)
-
-**Disposition (ACTIVITY-WP-0023-T06):** activity-core keeps global default
-`state-hub` and does **not** flip production to `rest`. Path A is owned by
-**issue-core**: rotate/fix `GITEA_BACKEND_TOKEN` (Forgejo backend PAT for the
-forgejo-inbox connector — not the activity-core `ISSUE_CORE_API_KEY`
-ingestion key). After issue-core proves `POST /issues/` → **201**, operators may
-opt in per definition / overlay only (WP-0022).
+`rapp-issue-core` verification proved authenticated create **201**, close
+**200**, dependency failure **503**, and recovery **201/200** at immutable image
+digest `sha256:a56c80ccbd1690bc0bcea384165b1967704f0fdbaf1c506ce1082f56190b92cf`.
+activity-core still keeps the global default `state-hub`; a healthy transport
+does not change the opt-in policy for external Forgejo projection.
 
 Internal scheduled automation should use **ops_run claim** (WP-0026), not wait
 on this rest path.
@@ -103,7 +99,7 @@ Smoke from worker (does not change sink env):
 
 ```bash
 kubectl -n activity-core exec deploy/actcore-worker -- python -c '
-# valid IssueCore body → expect 201 when path A is healthy, else 503 forgejo-inbox
+# valid IssueCore body → expect 201; close the controlled issue after the check
 '
 ```