Standardize public Gitea HTTPS endpoint

SCOPE.md

@@ -3,7 +3,7 @@
 This file defines what `railiance-forge` owns, when to use it, and where its
 boundaries stop.
 
-Last reviewed: 2026-06-05
+Last reviewed: 2026-06-13
 
 ---
 
@@ -116,15 +116,15 @@ The Fabric graph declarations for forge capabilities and edges live in
 - Status: active forge extraction.
 - Implementation: repository contract, registry docs, initial operating
   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.
+- Stability: emerging but now live-facing; forge owns the reviewed public
+  Gitea HTTPS ingress for the web UI, package registry, and OCI registry.
 - Usage: canonical reference point for forge and registry responsibilities
   currently transitioning out of `railiance-apps`.
 
 Known starting point:
 
-- `railiance-forge` owns Gitea Helm values, registry overlays, ingress,
-  operating contracts, and deploy/status entry points.
+- `railiance-forge` owns Gitea Helm values, registry overlays, public HTTPS
+  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