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
This repo described itself as 'the forge layer' while the OAS Stack dimension
defines five levels and forge is not one, leaving it unplaced. Placement decided
2026-08-11 (d151d817): the Forgejo workload becomes rapp-forgejo; the layer
responsibility - runner placement, registry retention, artifact lifecycle,
package credentials - folds into S4 railiance-enablement, which already declares
the handoff contract.
Notes that the retirement hypothesis was tested and rejected: this repo and
helix-forge are different lineages, operational versus methodological.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
