Expose Gitea package API route

docs/gitea-package-registry.md

@@ -8,6 +8,15 @@ Gitea package support is enabled by `helm/gitea-registry-values.yaml`. That
 overlay is applied after the encrypted base values by `make gitea-deploy` and
 enables both container packages and Python packages.
 
+The public ingress intentionally exposes `/api/packages` and `/v2` only. The
+package route is required for Python package upload and install traffic; the
+general Gitea web UI and API remain outside this ingress manifest.
+
+The live simple-index pages currently render package artifact links with
+`http://gitea.coulomb.social/...`. `uv lock` and clean `pip install` checks work
+against the public package route, but the next Gitea config reconciliation
+should align `ROOT_URL` with the HTTPS package endpoint.
+
 ## Python Packages
 
 Publish Python wheels to the organization package endpoint:
@@ -47,3 +56,7 @@ The portable deployment path for `vergabe-teilnahme` is:
 Registry endpoint ownership lives in `railiance-forge`; the package release and
 application dependency lock belong to the `issue-core` and `vergabe-teilnahme`
 source repos.
+
+Status on 2026-06-05: `issue-core==0.2.0` is published in the Coulomb Gitea
+PyPI registry and `vergabe-teilnahme` has regenerated its lock from this
+registry.

manifests/gitea-ingress.yaml

@@ -16,6 +16,13 @@ spec:
     - host: gitea.coulomb.social
       http:
         paths:
+          - path: /api/packages
+            pathType: Prefix
+            backend:
+              service:
+                name: gitea
+                port:
+                  number: 3000
           - path: /v2
             pathType: Prefix
             backend: