docs(ci): name the service Fabled-Git, not Forgejo
CI / lint (push) Successful in 3s
CI / unit (push) Successful in 5s
CI / publish (push) Successful in 13s

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>
This commit is contained in:
2026-08-01 19:54:43 -04:00
co-authored by Claude Opus 5
parent 31217498ce
commit c2d27d9a2b
+1 -1
View File
@@ -47,6 +47,6 @@ Friction, expectations, and anything the maintainer wouldn't see otherwise:
compose pull). compose pull).
- Unit suite is a starter set covering the pure logic (hashing, SQLite dedup, - Unit suite is a starter set covering the pure logic (hashing, SQLite dedup,
media-extension filter, file transfer modes). Grow it as behavior is added. media-extension filter, file transfer modes). Grow it as behavior is added.
- Requires repo Actions secret **`REGISTRY_TOKEN`** (Forgejo PAT, - Requires repo Actions secret **`REGISTRY_TOKEN`** (Fabled-Git PAT,
`read:package` + `write:package`) for the publish lane — the injected `read:package` + `write:package`) for the publish lane — the injected
`GITHUB_TOKEN` can't push to the registry (family rule 7). `GITHUB_TOKEN` can't push to the registry (family rule 7).