Move Gitea deploy surface into forge

workplans/FORGE-WP-0002-registry-docs-and-readonly-ops.md

@@ -4,7 +4,7 @@ type: workplan
 title: "Canonical registry docs and read-only forge operations"
 domain: railiance
 repo: railiance-forge
-status: active
+status: finished
 owner: codex
 topic_slug: railiance
 planning_priority: high
@@ -105,7 +105,7 @@ competing canonical sources.
 
 ```task
 id: FORGE-WP-0002-T05
-status: todo
+status: done
 priority: high
 state_hub_task_id: "6f6fc3a4-a883-4803-84e7-2700629d397a"
 ```
@@ -115,3 +115,8 @@ After operator review, move deploy-capable Gitea files and commands into
 
 Done when `railiance-forge` owns Gitea deploy/status/ingress commands and
 `railiance-apps` no longer carries live forge deployment files as S5 scope.
+
+Completed on 2026-06-05. The Gitea SOPS values, registry overlay, ingress
+manifest, legacy release values, and deploy/status Makefile targets now live in
+`railiance-forge`. `railiance-apps` keeps compatibility wrappers only. No live
+deploy, SOPS decryption, or Kubernetes apply was run.