Complete ISSUE-WP-0007 railiance01 cutover

workplans/ISSUE-WP-0007-rapp-issue-core-railiance01-migration.md

@@ -4,7 +4,7 @@ type: workplan
 title: "rapp-issue-core: move the runtime off CoulombCore onto railiance01"
 domain: infotech
 repo: issue-core
-status: active
+status: finished
 owner: codex
 lane: yellow
 topic_slug: issue-core
@@ -176,7 +176,7 @@ UV_CACHE_DIR=/tmp/issue-core-rmgr-cache uv run --directory ../repo-manager \
 
 ```task
 id: ISSUE-WP-0007-T02
-status: progress
+status: done
 priority: high
 state_hub_task_id: "e0427de0-dfac-4848-ba2d-1421167eb704"
 ```
@@ -193,7 +193,7 @@ records by hand.
 
 ```task
 id: ISSUE-WP-0007-T03
-status: todo
+status: done
 priority: high
 state_hub_task_id: "d6e5e2ac-7f42-412f-8143-91531f5155e8"
 ```
@@ -214,7 +214,7 @@ handoff. Two active sources of deployment truth are not allowed.
 
 ```task
 id: ISSUE-WP-0007-T04
-status: todo
+status: done
 priority: high
 state_hub_task_id: "21974fbd-4962-4732-b407-c531bb2ebfe6"
 ```
@@ -240,7 +240,7 @@ That is the condition being retired.
 
 ```task
 id: ISSUE-WP-0007-T05
-status: todo
+status: done
 priority: high
 state_hub_task_id: "3fdbd9ab-3e3f-4ac0-8763-77278a1cc6e6"
 ```
@@ -263,7 +263,7 @@ still pointed at `127.0.0.1:18765`.
 
 ```task
 id: ISSUE-WP-0007-T06
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "668e37dc-8ebe-46cc-9a27-905440b1240c"
 ```
@@ -291,3 +291,24 @@ Remaining CoulombCore services after this: `core-hub-staging` and `inter-hub`.
   kubeconfig any more — its `k3s-api` tunnel was removed on 2026-08-19, so
   inspecting the *current* deployment needs that tunnel restored first.
 - Reviewed 2026-08-19 in issue-core and promoted from `proposed` to `ready`.
+
+## Completion evidence — 2026-08-19
+
+- Created, registered, validated, and published private repo
+  `coulomb/rapp-issue-core`; wrapper commit `3003c92`, State Hub workstream
+  `b4c39759-6073-4558-a70c-2f869a31cfca`.
+- Fixed the Forgejo lifecycle identifier contract in issue-core commit
+  `3523a7d`; published and deployed immutable digest
+  `sha256:a56c80ccbd1690bc0bcea384165b1967704f0fdbaf1c506ce1082f56190b92cf`.
+- Full wrapper evidence passed: health 200, unauthenticated 401, authenticated
+  create 201 + close 200, bounded dependency 503, recovery 201 + close 200,
+  ExternalSecret ready with two keys, both NetworkPolicies present, previous
+  digest rollback health 200, and restored-digest re-verification.
+- activity-core commit `213e810` now uses
+  `http://issue-core.issue-core.svc.cluster.local:8765` directly while keeping
+  `ISSUE_SINK_TYPE=state-hub`; a controlled worker-side request returned
+  create 201 and close 200.
+- Deleted the legacy activity-core bridge resources, stopped and removed both
+  port-18765 ops-bridge entries, and confirmed the local listener was gone.
+- Retired this repo's duplicate `k8s/railiance/` source and obsolete ArgoCD
+  runbook after the wrapper was pushed and its evidence retained.