Close S5 app readiness workplan

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

@@ -4,7 +4,7 @@ type: workplan
 title: "S5 app release readiness and scope alignment"
 domain: railiance
 repo: railiance-apps
-status: active
+status: finished
 owner: codex
 topic_slug: railiance
 planning_priority: medium
@@ -27,16 +27,18 @@ 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:
+The same review found several planning-time gaps that are closed by this
+workplan:
 
-- `INTENT.md` is missing, so purpose and scope are collapsed into one document.
-- The `vergabe-teilnahme` runbook still contains stale image-promotion guidance
-  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.
-- Forge package storage and app database backup responsibilities need clearer
+- `INTENT.md` was missing, so purpose and scope were collapsed into one
+  document.
+- The `vergabe-teilnahme` runbook contained stale image-promotion guidance tied
+  to the old local `issue-core` build context.
+- First-app lessons were documented, but not yet turned into a reusable
+  checklist for the next S5 app release.
+- Forge package storage and app database backup responsibilities needed clearer
   contracts with platform-layer work.
-- The server-side dry-run workflow does not state its live-cluster/CRD
+- The server-side dry-run workflow did not state its live-cluster/CRD
   prerequisites clearly enough for a future runner.
 
 This workplan turns those scope gaps into the next improvement strand.
@@ -100,7 +102,7 @@ compatibility pointers were removed later by `RAILIANCE-WP-0006-T10`.
 
 ```task
 id: RAILIANCE-WP-0005-T03
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "4eab93a9-ad1b-46ca-97ef-18a059f64ab5"
 ```
@@ -122,13 +124,19 @@ The checklist should cover:
 Done when a new app can start from the checklist without reading all historical
 workplans first.
 
+Completed on 2026-06-05 by adding
+`docs/s5-app-onboarding-checklist.md` and cross-linking it from `SCOPE.md` and
+the `vergabe-teilnahme` runbook. The checklist covers app scope, chart/values
+layout, forge artifact consumption, database and secret handoff, ingress/TLS,
+probe Host headers, smoke tests, runbook baseline, and State Hub sync.
+
 ---
 
 ## T04 - Define app data backup and restore handoffs
 
 ```task
 id: RAILIANCE-WP-0005-T04
-status: todo
+status: done
 priority: high
 state_hub_task_id: "299d9623-3a54-4e85-9a70-016e8356c3d9"
 ```
@@ -151,13 +159,20 @@ Done when `SCOPE.md` and app runbooks clearly separate S5 release ownership from
 S3 backup implementation while still giving operators an actionable restore
 readiness gate.
 
+Completed on 2026-06-05 by adding
+`docs/app-data-backup-restore-handoff.md`, updating
+`docs/vergabe-teilnahme.md`, and refreshing `SCOPE.md`. The handoff states that
+S5 owns app release evidence and post-restore app checks, while
+`railiance-platform` owns `apps-pg` backup/restore mechanisms and
+`railiance-forge` owns artifact restore evidence.
+
 ---
 
 ## T05 - Make manifest dry-run workflow prerequisites explicit
 
 ```task
 id: RAILIANCE-WP-0005-T05
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "6cf0e662-d7e2-48b1-b1f2-c7636240dd81"
 ```
@@ -177,6 +192,13 @@ Questions to answer:
 Done when a future operator can tell whether the workflow is ready to enforce
 PR checks or still needs runner/cluster preparation.
 
+Completed on 2026-06-05 by adding
+`docs/manifest-server-dry-run.md`, updating `docs/operator-recipes.md`, and
+making `tools/k8s-server-dry-run.sh` print an explicit representative-cluster
+preflight error. The docs classify runner/cluster prerequisite gaps separately
+from release-blocking manifest failures and note that
+`DRY_RUN_CREATE_NAMESPACES=true` creates the namespace as a real side effect.
+
 ---
 
 ## T06 - Hand off Gitea package registry storage and retention posture