Delegate Gitea operations to forge

INTENT.md

@@ -38,9 +38,9 @@ a new archaeology exercise.
 > *Where we are going.*
 
 To become the **canonical home for Railiance application workload releases** -
-the Helm values, Kubernetes manifests, registry enablement, app-level runbooks,
-smoke checks, and operator recipes that make user-facing services safe to ship
-on top of the platform.
+the Helm values, Kubernetes manifests, app-level runbooks, smoke checks, and
+operator recipes that make user-facing services safe to ship on top of the
+platform.
 
 This means:
 
@@ -82,10 +82,10 @@ down and mutate those layers to make an app work.
 An app release is healthy when probes, status checks, smoke tests, and operator
 evidence say it is healthy, not merely because manifests applied successfully.
 
-### 6. Current Workload, Future Path
+### 6. App Workloads, Forge Consumers
 
-Gitea and early application releases are current S5 workloads and learning
-surfaces. Their lessons should leave behind reusable deployment patterns that
+Applications consume forge artifacts without owning forge runtime state. Early
+application releases should leave behind reusable deployment patterns that
 survive future forge and app migrations.
 
 ---
@@ -126,8 +126,8 @@ This layer is expected to evolve toward:
 * Stronger **image and package promotion** patterns
 * Clearer **backup, restore, and data ownership handoffs** with S3
 * More complete **smoke, migration, rollback, and observability** recipes
-* Cleaner separation between **current forge operation** and future forge
-  migration paths
+* Cleaner consumption of **forge-owned artifacts and evidence** from app
+  release runbooks
 * Self-evidencing, reviewable **application readiness** before promotion
 
 ---