diff --git a/README.md b/README.md
index 703f8a7..8e129bf 100644
--- a/README.md
+++ b/README.md
@@ -56,6 +56,7 @@ Site repos call the shared workflow with:
 ```yaml
 jobs:
   deploy:
+    runs-on: docker-desktop
     uses: cliper/hugo_deployment/.forgejo/workflows/deploy-hugo-site.yml@v1
     with:
       deploy_script: ./scripts/deploy.sh
@@ -67,6 +68,7 @@ Notes:
 
 - For the current caller pattern, `DEPLOY_SSH_HOST`, `DEPLOY_SSH_USER`, and `DEPLOY_PATH` are required repo variables unless the caller explicitly passes host and user as workflow inputs
 - Caller repos pass `DEPLOY_SSH_KEY` through `jobs.<job_id>.secrets`; Forgejo v11 accepts caller-provided reusable workflow secrets even though `on.workflow_call` itself only documents `inputs` and `outputs`
+- Caller workflows should keep `runs-on: docker-desktop` on the job that uses this reusable workflow when running against the current Develton Forgejo instance, which avoids buggy workflow expansion on the server side
 - Caller repos can set `DEPLOY_KNOWN_HOSTS` in repo variables with a pinned `known_hosts` entry for stronger host verification
 - If `DEPLOY_KNOWN_HOSTS` is not set, the workflow falls back to `ssh-keyscan` so current repos keep working
 - The reusable workflow itself always runs on `docker-desktop`