Move Gitea deploy surface into forge

SCOPE.md

@@ -30,8 +30,8 @@ The practical contract is:
 4. `railiance-apps` consumes forge artifacts and deploys user-facing workloads.
 
 Canonical registry operation docs and read-only forge checks now live here.
-Deploy-capable Gitea Helm/SOPS/manifests remain in `railiance-apps` until the
-explicit migration gate for live-affecting files is reviewed.
+Deploy-capable Gitea Helm/SOPS/manifests also live here now; `railiance-apps`
+keeps only transitional compatibility wrappers for old operator entry points.
 
 ---
 
@@ -105,20 +105,20 @@ explicit migration gate for live-affecting files is reviewed.
 
 ## Current State
 
-- Status: early extraction.
+- Status: active forge extraction.
 - Implementation: repository contract, registry docs, initial operating
-  contracts, and read-only operator targets are present.
-- Stability: emerging but non-disruptive; no deploy-capable Gitea state has
-  moved yet.
+  contracts, deploy-capable Gitea files, and operator targets are present.
+- Stability: emerging but non-disruptive; files moved without any Helm deploy,
+  SOPS decryption, or Kubernetes apply.
 - Usage: canonical reference point for forge and registry responsibilities
   currently transitioning out of `railiance-apps`.
 
 Known starting point:
 
-- `railiance-apps` currently owns Gitea Helm values, registry overlays, ingress,
-  and deploy-capable Gitea Makefile targets.
-- `railiance-forge` owns registry operation docs, operating contracts, and
-  read-only status entry points.
+- `railiance-forge` owns Gitea Helm values, registry overlays, ingress,
+  operating contracts, and deploy/status entry points.
+- `railiance-apps` keeps app release ownership and transitional compatibility
+  wrappers for old Gitea commands.
 - `railiance-enablement` owns the intent for delivery templates and developer
   paved paths, but not forge runtime operation.
 - `railiance-forge` should absorb forge runtime and artifact infrastructure
@@ -154,8 +154,8 @@ Known starting point:
 
 ## Related / Overlapping
 
-- `railiance-apps` - currently hosts Gitea deployment files and registry docs;
-  should become a consumer after extraction.
+- `railiance-apps` - consumes forge artifacts in S5 app releases and keeps
+  transitional pointers/wrappers for old Gitea paths.
 - `railiance-enablement` - owns reusable CI/CD templates, SDKs, buildpacks, and
   developer portal paths.
 - `railiance-platform` - provides database, storage, backup, and runtime secret