Point app registry docs at railiance-forge

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

@@ -4,12 +4,12 @@ type: workplan
 title: "S5 app release readiness and scope alignment"
 domain: railiance
 repo: railiance-apps
-status: ready
+status: active
 owner: codex
 topic_slug: railiance
 planning_priority: medium
 created: "2026-06-04"
-updated: "2026-06-04"
+updated: "2026-06-05"
 state_hub_workstream_id: "685f1c18-33c0-400d-a2b1-e1dae0f27c3e"
 ---
 
@@ -23,6 +23,10 @@ and now owns the repeatable S5 application release surface: Gitea registry
 enablement, 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
+keeps only app-release readiness items in S5.
+
 The same review found several gaps:
 
 - `INTENT.md` is missing, so purpose and scope are collapsed into one document.
@@ -66,7 +70,7 @@ of carrying all purpose language itself.
 
 ```task
 id: RAILIANCE-WP-0005-T02
-status: todo
+status: done
 priority: high
 state_hub_task_id: "f8f63edb-a7ef-4692-8b01-66402d296cbb"
 ```
@@ -86,6 +90,9 @@ Focus areas:
 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`.
+
 ---
 
 ## T03 - Create a reusable S5 app onboarding checklist
@@ -129,7 +136,6 @@ Clarify where S5 app data durability begins and ends.
 
 Cover at least:
 
-- Gitea package blobs on the shared Gitea PVC;
 - `vergabe_db` on the shared `apps-pg` CNPG cluster;
 - responsibility split between S5 runbooks and `railiance-platform` backup
   controllers;
@@ -137,6 +143,8 @@ Cover at least:
   beyond smoke-test usage;
 - how to file or link platform-layer workplans when the durability gap is not
   local to this repo.
+- how S5 app runbooks cite forge-owned package/blob restore evidence without
+  owning Gitea package backup procedures.
 
 Done when `SCOPE.md` and app runbooks clearly separate S5 release ownership from
 S3 backup implementation while still giving operators an actionable restore
@@ -174,7 +182,7 @@ PR checks or still needs runner/cluster preparation.
 
 ```task
 id: RAILIANCE-WP-0005-T06
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "382ba252-0f54-45fa-8e33-e656f4472341"
 ```
@@ -193,3 +201,7 @@ Include:
 
 Done when registry growth is no longer only a note in
 `docs/gitea-container-registry.md`.
+
+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.