Deploys run as gitea-runner, the instance's one runner on Max since 1 November 2026

build-runner was merged into it: the same labels (build stays), the same sudo verbs and
folders, the .NET 9 SDK and the library clone cache.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

CLAUDE.md

@@ -207,7 +207,7 @@ ASPNETCORE_ENVIRONMENT=Production ./PrivaPub admin delete-root <root>   # as the
 ASPNETCORE_ENVIRONMENT=Production ./PrivaPub admin reset-totp <root>    # a login that lost its authenticator and codes
 ```
 
-The deploy runs them as `build-runner`, which owns the published files, reads `appsettings.Production.json` through
+The deploy runs them as `gitea-runner` (the instance's one runner on Max since 1 November 2026; `build-runner` before), which owns the published files, reads `appsettings.Production.json` through
 group www-data and reaches the private mongod; `sudo -u www-data` works too. Every one of them that changes a login or a
 persona (promote, demote, role, create-root, move-persona, delete-root, reset-totp) and `restore` is kept in the staff's
 log as the command line's (`cli`). The command line may leave the server without an administrator (it says so); the

deploy/max/setup.sh

@@ -6,7 +6,7 @@ set -euo pipefail
 SRC="${1:-/root/privapub-deploy}"
 HOST=privapub.thepra.dev
 UNIT=privapub
-RUNNER=build-runner
+RUNNER=gitea-runner
 ACME=/root/.acme.sh/acme.sh
 
 echo "== directories"