workplan update

workplans/railiance-apps-WP-0004-app-deployment-improvements.md

@@ -9,7 +9,7 @@ owner: railiance
 topic_slug: railiance
 planning_priority: medium
 created: "2026-05-19"
-updated: "2026-05-22"
+updated: "2026-05-23"
 state_hub_workstream_id: "b61a9aca-4e43-4b3d-a48b-999e0fa842cf"
 ---
 
@@ -20,7 +20,7 @@ This workplan collects concrete follow-ups surfaced while shipping
 independent, and can be picked up in isolation when the next S5 app
 lands or when the next operator onboards. Activated on 2026-05-22;
 local railiance-apps guardrails are implemented, with the package
-publication item blocked on sibling-repo release work.
+publication item blocked on Gitea package publish credentials.
 
 ## I01 — URL-encode DB passwords at Secret-build time
 
@@ -112,6 +112,15 @@ sets `packages.LIMIT_SIZE_PYPI: -1`, and
 the `issue-core` migration. The remaining release and dependency change
 must happen in the `issue-core` and `vergabe-teilnahme` repos.
 
+**Cross-repo progress 2026-05-23.** `issue-core` now has a validated
+`make package-check` build and Gitea Actions publish workflow for the
+`0.2.x` package series. `vergabe-teilnahme` has been switched in
+`pyproject.toml` to `issue-core>=0.2,<0.3`, with the Docker named
+`issue-core` build context removed in favor of the Gitea PyPI index.
+The final unblock still requires a Gitea package username/token to
+publish `issue-core==0.2.0`; once published, regenerate
+`vergabe-teilnahme/uv.lock` from the registry and mark this task done.
+
 ---
 
 ## I04 — Operator onboarding: install the `kubectl cnpg` plugin
@@ -230,7 +239,7 @@ wraps the pattern.
 ## Notes
 
 - Items were activated on 2026-05-22. Local railiance-apps pieces are
-  complete except I03, which is blocked on sibling-repo release work.
+  complete except I03, which is blocked on Gitea package publish credentials.
 - I06 is genuinely cross-repo; the others are local to
   `railiance-apps` or its operator workflow.
 - The first three items (I01, I02, I03) are the highest-leverage