Decommission forge compatibility pointers

workplans/RAILIANCE-WP-0005-s5-app-release-readiness.md

@@ -19,9 +19,9 @@ state_hub_workstream_id: "685f1c18-33c0-400d-a2b1-e1dae0f27c3e"
 
 The 2026-06-04 review of `SCOPE.md` against the actual repository
 implementation found that `railiance-apps` has moved beyond "Gitea Helm values"
-and now owns the repeatable S5 application release surface: Gitea registry
-enablement, the `vergabe-teilnahme` Helm release, operator guardrails, and
-deployment runbooks.
+and now owns the repeatable S5 application release surface: forge-backed
+artifact consumption, the `vergabe-teilnahme` Helm release, operator
+guardrails, and deployment runbooks.
 
 The 2026-06-05 `railiance-forge` extraction moved canonical registry operating
 docs and registry-retention policy into the new forge layer. This workplan now
@@ -34,7 +34,7 @@ The same review found several gaps:
   tied to the old local `issue-core` build context.
 - First-app lessons are documented, but there is no reusable checklist for the
   next S5 app release.
-- Gitea package storage and app database backup responsibilities need clearer
+- Forge package storage and app database backup responsibilities need clearer
   contracts with platform-layer work.
 - The server-side dry-run workflow does not state its live-cluster/CRD
   prerequisites clearly enough for a future runner.
@@ -57,7 +57,7 @@ It should explain:
 - why this repo exists as the S5 application deployment surface;
 - what problem it solves for operators and source app repos;
 - what it intentionally does not own across S1-S4 boundaries;
-- how Gitea, package registry enablement, `vergabe-teilnahme`, and future S5
+- how forge-owned registry capabilities, `vergabe-teilnahme`, and future S5
   apps fit together;
 - how workplan files relate to State Hub workstreams and task rows.
 
@@ -84,14 +84,15 @@ Focus areas:
 - document the package-registry credential path for private Python package
   installs without committing tokenized index URLs;
 - state when `vergabe-teilnahme/uv.lock` must be regenerated in the source repo;
-- keep `docs/gitea-package-registry.md` focused on the S5 registry endpoint and
-  cross-link source-repo release docs instead of duplicating them.
+- link to forge-owned registry endpoint docs and source-repo release docs
+  instead of duplicating them in S5.
 
 Done when the Railiance operator docs describe the portable image promotion path
 and no active runbook tells an operator to rely on a sibling repo checkout.
 
 Completed on 2026-06-05 by updating `docs/vergabe-teilnahme.md` and replacing
-the local registry docs with compatibility pointers to `railiance-forge`.
+local registry ownership with direct links to `railiance-forge`. The temporary
+compatibility pointers were removed later by `RAILIANCE-WP-0006-T10`.
 
 ---
 
@@ -178,7 +179,7 @@ PR checks or still needs runner/cluster preparation.
 
 ---
 
-## T06 - Define Gitea package registry storage and retention posture
+## T06 - Hand off Gitea package registry storage and retention posture
 
 ```task
 id: RAILIANCE-WP-0005-T06
@@ -187,8 +188,8 @@ priority: medium
 state_hub_task_id: "382ba252-0f54-45fa-8e33-e656f4472341"
 ```
 
-Document the operating posture for Gitea package storage while Gitea remains the
-active forge.
+Document the forge-owned operating posture for Gitea package storage while
+Gitea remains the active forge.
 
 Include:
 
@@ -199,9 +200,8 @@ Include:
 - handoff to platform backup/restore work when package data becomes production
   critical.
 
-Done when registry growth is no longer only a note in
-`docs/gitea-container-registry.md`.
+Done when registry growth is no longer only a note in S5 app docs.
 
 Completed on 2026-06-05 by moving the canonical storage and retention posture
-to `/home/worsch/railiance-forge/docs/initial-operating-contracts.md`; the local
-registry docs are compatibility pointers.
+to `/home/worsch/railiance-forge/docs/initial-operating-contracts.md`; S5 app
+runbooks now cite forge docs directly.