ci: converters.yml header names the grant in the private repository's Actions settings as what lets the job token read it, instead of the 1Password fallback that turned out unnecessary (#232 close)

Files changed:
- .gitea/workflows/converters.yml

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2

.gitea/workflows/converters.yml

@@ -23,10 +23,10 @@
 # Runner shape: identical to ci.yml, and for the same reason - see its header for `nodejs`.
 #
 # Access to the private repository: the per-job token (`${{ gitea.token }}`), as `release.yml`
-# uses it for this repository. If this instance does not let it read a second, private repository
+# uses it for this repository. It can read `chemenu-testfiles` only because that repository's own
-# of the same owner, the clone step fails with an authentication error; the way out is a read token
+# Actions settings grant `torben/chemenu` access - a grant set in this repository does nothing.
-# in 1Password, loaded with `1password/load-secrets-action` the way `ci.yml` loads its secret
+# Without it the second checkout fails with "Determining the default branch ... not found", which
-# reference (the service account sees only the CI-CD vault).
+# reads like a missing repository rather than a missing permission (Gitea #232, runs 699 and 701).
 
 name: Converters