docs: name Forgejo as the current forge, keep gitea identifiers for compatibility

Gitea is retired; current-state prose in SCOPE, INTENT, README, AGENTS and
rules now says Forgejo. File names, chart/resource names, the .gitea/workflows
path and historical records are unchanged. Adds a forgejo-status alias and
warns that gitea-deploy is not the live release source (railiance-apps
forgejo-values).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 99543@bnt-lap001
Assistant-Session: 05d24177-20b9-4e96-a91b-b73be1d6e99e

INTENT.md

@@ -33,7 +33,7 @@ This layer exists to make those responsibilities explicit and operable.
 > *Where we are going.*
 
 To become the **canonical home for Railiance forge and artifact infrastructure**
-- current Gitea operation, future Forgejo migration, container and package
+- current Forgejo operation (migrated from Gitea), container and package
 registries, forge-backed automation runner substrate, artifact lifecycle, and
 forge operational evidence.
 
@@ -76,11 +76,12 @@ promotion evidence.
 Forge data is operationally critical. Source repos, packages, registry blobs,
 and runner state need explicit backup and restore posture.
 
-### 6. Current Gitea, Future Forgejo
+### 6. Forgejo Is the Current Forge
 
-Gitea is the current workload; Forgejo is the intended production direction.
-The repo should support both the current operating state and clean future
-cutover planning.
+Forgejo is the production forge; the earlier Gitea workload is retired.
+Some chart, resource and path names still say `gitea` for compatibility;
+the repo treats them as Forgejo infrastructure and keeps future forge
+changes cleanly plannable.
 
 ---