S4 Developer Enablement — CI/CD, platform templates
tegwick
a2525a404c
Decision d151d817 placed railiance-forge: the Forgejo workload becomes rapp-forgejo, and the layer responsibility - runner placement and labels, registry retention, artifact lifecycle, package credentials - folds into S4, which already declared a handoff contract with forge for exactly those concerns. Also states plainly what the 2026-08-11 architecture assessment found about this layer: it is almost entirely aspiration, with a rich Direction of Evolution and 25 commits and no workplans behind it. The gap should be read as open debt rather than as a description of the present. The forge responsibility is S4's first concrete owned accountability. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .claude/rules | ||
| .forgejo/workflows | ||
| docs | ||
| registry | ||
| tools | ||
| workflows | ||
| workplans | ||
| .custodian-brief.md | ||
| .repo-classification.yaml | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| INTENT.md | ||
| LICENSE | ||
| Makefile | ||
| SCOPE.md | ||