Migrate issue-core OCI and PyPI refs to Forgejo (RAIL-HO-WP-0006)

docs/argocd-gitops.md

@@ -7,7 +7,7 @@ railiance-platform.
 ## Source layout
 
 - Workload bundle: `issue-core/k8s/railiance/`
-- Image: `gitea.coulomb.social/coulomb/issue-core:0.2.1`
+- Image: `forgejo.coulomb.social/coulomb/issue-core:0.2.1`
 - Container port and Service port: `8765`
 - Cluster Service URL: `http://issue-core.issue-core.svc.cluster.local:8765`
 - Tenant Application: `railiance-platform/argocd/applications/issue-core.application.yaml`
@@ -60,8 +60,8 @@ Build the checked-out source tree and publish a registry tag that ArgoCD can
 pull:
 
 ```bash
-docker build -t gitea.coulomb.social/coulomb/issue-core:0.2.1 .
+docker build -t forgejo.coulomb.social/coulomb/issue-core:0.2.1 .
-docker push gitea.coulomb.social/coulomb/issue-core:0.2.1
+docker push forgejo.coulomb.social/coulomb/issue-core:0.2.1
 ```
 
 The Coulomb Gitea package is public-pullable for this image, so the workload

docs/package-release.md

@@ -23,13 +23,13 @@ make publish-gitea
 The package endpoint is:
 
 ```text
-https://gitea.coulomb.social/api/packages/coulomb/pypi
+https://forgejo.coulomb.social/api/packages/coulomb/pypi
 ```
 
 The matching simple index for consumers is:
 
 ```text
-https://gitea.coulomb.social/api/packages/coulomb/pypi/simple/
+https://forgejo.coulomb.social/api/packages/coulomb/pypi/simple/
 ```
 
 Do not commit tokenized package index URLs. CI and local Docker builds should

k8s/railiance/deployment.yaml

@@ -23,7 +23,7 @@ spec:
       # docs). Add imagePullSecrets: [{name: gitea-registry}] if it becomes private.
       containers:
         - name: issue-core
-          image: gitea.coulomb.social/coulomb/issue-core:0.2.1
+          image: forgejo.coulomb.social/coulomb/issue-core:0.2.1
           imagePullPolicy: IfNotPresent
           ports:
             - name: http