hotfix2:fix workflow

.gitea/workflows/release-offline.yml

@@ -8,7 +8,7 @@ permissions:
 
 jobs:
   package-and-deploy:
-    runs-on: ubuntu-latest
+    runs-on: build-host
     steps:
       - name: Prepare local worktree
         env:

deploy/server-maibot/README_DEPLOY_STEPS.txt

@@ -21,7 +21,7 @@ Gitea workflow:
 - .gitea/workflows/release-offline.yml
 
 Current pipeline mode:
-- release on a runner that exposes the default `ubuntu-latest` label
+- single-host release on the repo-level `build-host` runner
 - fetches the source commit from the workflow repository itself
 - defaults to `${gitea.server_url}/${gitea.repository}.git`
 - can override the clone URL with the repository variable `MAIBOT_REPO_URL`
@@ -39,8 +39,7 @@ Optional environment overrides for the workflow runtime:
 - `MAIBOT_BASE_IMAGE`
 
 Runner connectivity note:
-- the runner must advertise the `ubuntu-latest` label; this is part of the default Gitea runner label set unless you replaced it during registration
-- if your production runner only has custom labels, either add `ubuntu-latest` back on the runner side or change the workflow label to your actual runner label
+- the runner must advertise the `build-host` label; this is the current production label on the repository-level runner
 - if the runner cannot access `${gitea.server_url}` directly, set `MAIBOT_REPO_URL` to a runner-reachable HTTPS clone URL
 - for private repositories, the workflow uses the built-in `GITEA_TOKEN`, so no extra personal access token secret is needed
 - the repository or owner Actions settings must allow the job token to read repository contents