Close runner ownership task

SCOPE.md

@@ -157,7 +157,10 @@ lessons into reusable S5 app release patterns.
 - The first-app lessons from `vergabe-teilnahme` are documented, but there is
   no reusable "new S5 app release checklist" yet.
 - The manifest dry-run workflow assumes access to a representative cluster and
-  CRDs. Its operating requirements should be made explicit for future runners.
+  CRDs. Forge-owned runner labels, placement, and credential prerequisites are
+  defined in
+  `/home/worsch/railiance-forge/docs/ci-runner-actions-gitops-ownership.md`;
+  the app-side workflow behavior still needs explicit S5 readiness docs.
 - App-level backup and restore responsibilities need clearer handoff contracts
   with `railiance-platform`, especially for shared CNPG databases consumed by
   S5 apps.