docs(cicd): document user-scoped PR runner

.gitea/runner/README.md

@@ -3,8 +3,10 @@
 The native Gitea runners run on **vps**; production runs on **workstation**.
 Main-branch checks and image builds use `homelab:host`. Pull request and
 non-main checks use `homelab-pr:host` under a separate account without Docker
-access. Each runner accepts one job at a time; the build waits for every check
-to pass. CI and deploy runs also show a summary with
+access. The `homelab-pr` runner is registered at User scope for `forust`, so
+any repository under that account can schedule jobs that request this label.
+Each runner accepts one job at a time; the build waits for every check to pass.
+CI and deploy runs also show a summary with
 the release SHA, image build or reuse results, deploy mode, selected services,
 and image digests. Failed runs keep a summary of completed image builds, stage
 results, apply results, and recorded Kubernetes recovery. The final deploy
@@ -46,11 +48,11 @@ Install the unprivileged host runner on the VPS:
 sudo bash .gitea/runner/setup-pr-runner.sh
 ```
 
-Get a registration token from the repository Actions runner settings. Run the
+Get a registration token from the user Actions runner settings. Run the
 installer in a terminal. It asks for the token without echoing it, registers the
 runner as `homelab-pr` with label `homelab-pr:host`, then enables the service.
-The work directory is `/var/lib/gitea-pr-runner`. Confirm that Gitea lists
-`homelab-pr:host` before merging the workflow change. An unmatched label can
+The work directory is `/var/lib/gitea-pr-runner`. Confirm that Gitea lists the
+runner as User scope before merging the workflow change. An unmatched label can
 fall back to the default job image.
 
 Renovate PR validation uses `pull_request_target`, which reads the workflow from