RAPPS-WP-0019 stage C: consumers on forge-http; remove compatibility alias

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 276069@bnt-lap001
Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c

WORK-RECORDS.md

@@ -56,6 +56,6 @@
 | task | RAPPS-WP-0018-T01 | wait | — | workplans/RAPPS-WP-0018-wave2-resource-right-sizing.md |
 | task | RAPPS-WP-0019-T01 | done | — | workplans/RAPPS-WP-0019-product-neutral-forge-object-names.md |
 | task | RAPPS-WP-0019-T02 | done | — | workplans/RAPPS-WP-0019-product-neutral-forge-object-names.md |
-| task | RAPPS-WP-0019-T03 | todo | — | workplans/RAPPS-WP-0019-product-neutral-forge-object-names.md |
+| task | RAPPS-WP-0019-T03 | done | — | workplans/RAPPS-WP-0019-product-neutral-forge-object-names.md |
 | task | RAPPS-WP-0019-T04 | todo | — | workplans/RAPPS-WP-0019-product-neutral-forge-object-names.md |
 | task | RAPPS-WP-0019-T05 | todo | — | workplans/RAPPS-WP-0019-product-neutral-forge-object-names.md |

manifests/forgejo-compat-http-service.yaml

@@ -1,23 +0,0 @@
-# TEMPORARY compatibility alias (RAPPS-WP-0019, stage B -> C).
-# The forge Helm objects were renamed from forgejo-gitea-* to forge-*. In-cluster
-# consumers still call http://forgejo-gitea-http.forgejo.svc:3000 until they move to
-# forge-http (stage C). Delete this Service once no consumer uses the old name.
-apiVersion: v1
-kind: Service
-metadata:
-  name: forgejo-gitea-http
-  namespace: forgejo
-  labels:
-    app.kubernetes.io/instance: forgejo
-    app.kubernetes.io/part-of: railiance-apps
-    railiance.io/compat-alias-for: forge-http
-spec:
-  clusterIP: None
-  selector:
-    app.kubernetes.io/instance: forgejo
-    app.kubernetes.io/name: forge
-  ports:
-    - name: http
-      port: 3000
-      targetPort: 3000
-      protocol: TCP

workplans/RAPPS-WP-0019-product-neutral-forge-object-names.md

@@ -10,6 +10,7 @@ owner: railiance-apps
 created: "2026-10-21"
 updated: "2026-10-21"
 related: [FORGE-WP-0011, CUST-WP-0071]
+state_hub_workstream_id: "b0cc4018-0cf3-53a3-83d6-f76d377d763a"
 ---
 
 # Product-neutral forge object names
@@ -41,6 +42,7 @@ are not live. They are listed for cleanup in T05.
 id: RAPPS-WP-0019-T01
 status: done
 priority: high
+state_hub_task_id: "a6bd310d-34f5-5642-a1cb-e682a72892c9"
 ```
 
 core-hub, issue-core and sbom-nexus allow egress to the forge by selecting
@@ -65,6 +67,7 @@ id: RAPPS-WP-0019-T02
 status: done
 priority: high
 depends_on: [RAPPS-WP-0019-T01]
+state_hub_task_id: "14c47d3d-24e9-539c-ad3e-45741e1e339f"
 ```
 
 Source: `helm/forgejo-values.yaml` (`fullnameOverride: forge`, `nameOverride: forge`,
@@ -99,9 +102,10 @@ Rollback:
 
 ```task
 id: RAPPS-WP-0019-T03
-status: todo
+status: done
 priority: medium
 depends_on: [RAPPS-WP-0019-T02]
+state_hub_task_id: "e8cf80bc-3f1a-5990-b39d-4ed20cb1ba7f"
 ```
 
 Change the in-cluster URLs `forgejo-gitea-http.forgejo.svc` to `forge-http.forgejo.svc`:
@@ -119,6 +123,7 @@ id: RAPPS-WP-0019-T04
 status: todo
 priority: low
 depends_on: [RAPPS-WP-0019-T02]
+state_hub_task_id: "0be013cc-6bc1-5e0e-8f06-e2deef0c919c"
 ```
 
 railiance-forge `Makefile` (`GITEA_HTTP_SERVICE`) and
@@ -131,6 +136,7 @@ name `forgejo-gitea`. Prefer "forge" wherever the concrete product is not meant.
 id: RAPPS-WP-0019-T05
 status: todo
 priority: low
+state_hub_task_id: "169aeda8-2f4a-5bef-9343-8ad367dde71a"
 ```
 
 Review and remove or archive the non-live Gitea-era manifests named above, once
@@ -157,3 +163,19 @@ The founder ran the attended cutover script. It checked the node, waited until t
 - Downtime was about 3 minutes.
 
 Rollback reference: scale `forge` to 0, then `helm rollback forgejo 10`, then the previous Ingress and NodePort manifests from git.
+
+## Stage C applied — 2026-10-21
+
+In-cluster URLs now use `forge-http.forgejo.svc`:
+- core-hub: rapp-core-hub f2a9ded, Helm revision 33; publisher rolled.
+- sbom-nexus: rapp-sbom-nexus cc4db99, server-side apply; rolled.
+- issue-core: rapp-issue-core 805e124 with a `railiance.io/backends-revision` pod
+  annotation, so that the ConfigMap-based setting rolls the pod. Pinned in
+  railiance-platform 51d5247, root app hard-refreshed and synced, issue-core synced:
+  Synced/Healthy.
+
+Each full render diffed against live first showed only the URL, plus issue-core's
+annotation. A cluster-wide scan afterwards found no workload or ConfigMap still
+naming `forgejo-gitea`. All three consumers answer healthz 200 on `forge-http`.
+The compatibility Service was deleted live, its manifest was removed, and HTTPS
+and SSH git still work.