Naming per Scribe #2272: git.fabledsword.com runs Gitea 1.26.4, not Forgejo. "Fabled-Git" is the standing name for the service; the engine is named only where it's load-bearing.
One change — the REGISTRY_TOKEN note:
-- Requires repo Actions secret **`REGISTRY_TOKEN`** (Forgejo PAT,
+- Requires repo Actions secret **`REGISTRY_TOKEN`** (Fabled-Git PAT,
The surrounding detail stays exactly as-is: read:package + write:package scopes, and the reason the injected GITHUB_TOKEN can't push to the registry (family rule 7). Those are engine-accurate and load-bearing.
Verified before opening: ci-requirements.md is byte-identical between main and this commit's parent, so the merge applies cleanly.
One docs-only commit to `ci-requirements.md`.
Naming per Scribe #2272: `git.fabledsword.com` runs **Gitea 1.26.4**, not Forgejo. "Fabled-Git" is the standing name for the service; the engine is named only where it's load-bearing.
One change — the `REGISTRY_TOKEN` note:
```diff
-- Requires repo Actions secret **`REGISTRY_TOKEN`** (Forgejo PAT,
+- Requires repo Actions secret **`REGISTRY_TOKEN`** (Fabled-Git PAT,
```
The surrounding detail stays exactly as-is: `read:package` + `write:package` scopes, and the reason the injected `GITHUB_TOKEN` can't push to the registry (family rule 7). Those are engine-accurate and load-bearing.
Verified before opening: `ci-requirements.md` is byte-identical between `main` and this commit's parent, so the merge applies cleanly.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
This instance runs Gitea 1.26.4. Per the naming decision on Scribe #2272,
"Fabled-Git" is the standing name for the service and the engine is named
only where it is load-bearing (version-specific API behaviour, act_runner
quirks, click-through UI).
Service-level prose only. Deliberately NOT touched:
- `.forgejo/workflows/` paths, which resolve on this Gitea only because
GITEA__actions__WORKFLOW_DIRS lists them.
- anything naming the upstream Forgejo PROJECT (the artifact-action forks).
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
One docs-only commit to
ci-requirements.md.Naming per Scribe #2272:
git.fabledsword.comruns Gitea 1.26.4, not Forgejo. "Fabled-Git" is the standing name for the service; the engine is named only where it's load-bearing.One change — the
REGISTRY_TOKENnote:The surrounding detail stays exactly as-is:
read:package+write:packagescopes, and the reason the injectedGITHUB_TOKENcan't push to the registry (family rule 7). Those are engine-accurate and load-bearing.Verified before opening:
ci-requirements.mdis byte-identical betweenmainand this commit's parent, so the merge applies cleanly.🤖 Generated with Claude Code