railiance-forge/README.md
tegwick fa5d1af0a1
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
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
2026-10-18 02:36:09 +02:00

44 lines
1.1 KiB
Markdown

# railiance-forge
Railiance forge and artifact infrastructure.
This repository is being founded to separate source forge, registry, and
automation runner responsibilities from `railiance-apps` and
`railiance-enablement`.
Start with:
1. `INTENT.md`
2. `SCOPE.md`
3. `AGENTS.md`
4. `docs/`
5. `workplans/`
Current implementation status: active forge extraction. Canonical registry
operation docs, runner ownership contracts, deploy-capable forge files, and
operator targets live here now. No live Helm deploy or Kubernetes apply was run
as part of the move.
Key contracts:
- `docs/initial-operating-contracts.md`
- `docs/ci-runner-actions-gitops-ownership.md`
- `docs/gitea-actions-runner-substrate.md`
- `docs/gitea-actions-runner-evidence.md`
- `docs/backup-restore-secret-handoff.md`
- `docs/observability-operating-evidence.md`
- `docs/gitea-container-registry.md`
- `docs/gitea-package-registry.md`
Useful entry points:
```bash
make registry-docs
make evidence-docs
make runner-docs
make runner-status
make check-runner-tools
make check-tools
make gitea-status
make gitea-deploy
```