Correct stale Gitea current-state claims to Forgejo
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

Forgejo has replaced Gitea as the forge. Updates SCOPE.md Current State,
AGENTS.md and .claude/rules/repo-identity.md, which still described Gitea as
the operational forge.

Deliberately NOT changed, because they are accurate rather than stale:
- migration and coexistence prose in docs/forgejo-on-railiance01.md,
  docs/forge-source-of-truth-decision.md and the capability registry, where
  Gitea is the thing being migrated from
- gitea-charts/gitea 12.5.0, the real Helm chart Forgejo deploys from
- gitea-db, a running CNPG cluster, and the gitea- prefixed doc filenames in
  railiance-forge, which still exist under those names

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-11 23:08:52 +02:00
parent 668c54da05
commit 5ef514b96d
3 changed files with 9 additions and 8 deletions

View file

@ -1,4 +1,4 @@
**Purpose:** OAS S5 Workloads & Experience Endpoints — application Helm releases, Gitea, coulomb services
**Purpose:** OAS S5 Workloads & Experience Endpoints — application Helm releases, Forgejo, coulomb services
**Domain:** financials
**Repo slug:** railiance-apps