Point app registry docs at railiance-forge

docs/vergabe-teilnahme.md

@@ -68,9 +68,10 @@ make vergabe-superuser   # interactive createsuperuser
 
 ## Promoting a new image tag
 
-1. Build + push from `vergabe-teilnahme` repo (see its `Dockerfile`
-   header for the BuildKit `--build-context` invocation — see also
-   `RAILIANCE-WP-0004 I03`).
+1. Build + push from the `vergabe-teilnahme` repo using the portable package
+   path: `issue-core` must resolve from the Gitea PyPI registry, not from a
+   sibling checkout. If `issue-core==0.2.0` is not published yet, keep
+   `railiance-apps-WP-0004 I03` in `wait`.
 2. Update `image.tag` in `helm/vergabe-teilnahme-values.yaml` to the
    new git SHA.
 3. `make vergabe-deploy` — Helm rolls a new ReplicaSet with
@@ -152,8 +153,8 @@ configuration belongs to `railiance-platform`).
 - Workplan: `workplans/railiance-apps-WP-0002-vergabe-teilnahme-on-railiance01.md`
 - Improvements backlog: `workplans/railiance-apps-WP-0004-app-deployment-improvements.md`
 - Shared DB cluster: `railiance-platform/docs/apps-pg.md`
-- Container registry: `docs/gitea-container-registry.md`
-- Python package registry: `docs/gitea-package-registry.md`
+- Container registry: `/home/worsch/railiance-forge/docs/gitea-container-registry.md`
+- Python package registry: `/home/worsch/railiance-forge/docs/gitea-package-registry.md`
 - Django deployment recipe: `docs/django-on-railiance.md`
 - Operator setup: `docs/operator-setup.md`
 - Operator recipes: `docs/operator-recipes.md`