WBS-7.9: target snapshot admin deploy host runner

docs/SYNOLOGY_ACT_RUNNER_REFACTOR_PR_BODY.md

@@ -0,0 +1,20 @@
+# Synology Act Runner Split PR Body
+
+## Title
+
+`chore: split Synology act_runner start and re-registration scripts`
+
+## Body
+
+- Added `tools/re_register_act_runner_synology.sh` for explicit host-mode re-registration.
+- Added `tools/start_act_runner_synology.sh` for boot-time daemon start only.
+- Kept `tools/setup_act_runner.sh` as the bootstrap path, but made the re-registration flow explicit and repeatable.
+- Switched the runner registration labels to `self-hosted:host,snapshot-admin-host:host` so the job runs in host mode instead of Docker job containers and can be targeted by a dedicated deployment label.
+- Updated `docs/SYNOLOGY_SNAPSHOT_ADMIN_POC.md` and `docs/ROADMAP_WBS.md` so the operator flow and WBS notes match the new runner split.
+- The `snapshot_admin.yml` workflow is split into push smoke validation and manual full validation, which reduces routine CI cost while preserving the full web smoke path on demand.
+
+## Verification
+
+- `python tools/validate_snapshot_admin_workflow_v1.py`
+- `python -c "import yaml, pathlib; yaml.safe_load(pathlib.Path('.gitea/workflows/snapshot_admin.yml').read_text(encoding='utf-8'))"`
+- `git diff -- .gitea/workflows/snapshot_admin.yml tools/setup_act_runner.sh docs/SYNOLOGY_SNAPSHOT_ADMIN_POC.md docs/ROADMAP_WBS.md`

docs/SYNOLOGY_SNAPSHOT_ADMIN_DEPLOYMENT_CHECKLIST.md

@@ -70,6 +70,32 @@ bash /volume1/projects/data_feed/tools/run_snapshot_admin_synology.sh healthchec
 bash /volume1/projects/data_feed/tools/run_snapshot_admin_synology.sh restart
 ```
 
+## 4b. Gitea Actions runner label
+
+Use a unique host label so the deployment job is not mixed with generic self-hosted work.
+
+- Runner label: `snapshot-admin-host`
+- Registration example:
+
+```bash
+REG_TOKEN="<runner-registration-token>" \
+GITEA_URL="http://192.168.123.100:8418" \
+RUNNER_LABEL="snapshot-admin-host" \
+bash tools/re_register_act_runner_synology.sh
+```
+
+- Workflow selector:
+
+```yaml
+runs-on: [self-hosted, snapshot-admin-host]
+```
+
+## 4c. Queue handling
+
+- If the deploy workflow stays queued, it usually means the host runner is busy.
+- Check the job currently holding the runner before re-dispatching.
+- Do not keep dispatching deploy runs back-to-back. The workflow already uses `concurrency` to cancel in-progress duplicates.
+
 ## 5. Reverse proxy
 
 - DSM path: `Control Panel > Login Portal > Advanced > Reverse Proxy`

docs/SYNOLOGY_SNAPSHOT_ADMIN_FINAL_EXECUTION_ONE_PAGER.md

@@ -47,6 +47,20 @@ Confirm that `snapshot_admin_server_v1.py` runs on Synology with loopback bindin
    - Re-run steps 2-7
    - Expected: identical response pattern after restart
 
+## Queue check
+
+If the deployment workflow stays queued for more than a few minutes:
+
+1. Confirm the runner is registered with the host label.
+   - `RUNNER_LABEL=snapshot-admin-host`
+   - Re-register with `bash tools/re_register_act_runner_synology.sh` after setting the registration token.
+2. Confirm the runner daemon is running.
+   - `bash tools/start_act_runner_synology.sh`
+3. Confirm the queue target is the host runner label.
+   - Deploy workflow uses `runs-on: [self-hosted, snapshot-admin-host]`
+4. If another job is occupying the runner, wait for it to finish or cancel the stale workflow from Gitea.
+5. Re-dispatch `snapshot_admin_deploy.yml` after the runner is idle.
+
 ## Pass criteria
 
 - Loopback `200` confirmed.

docs/SYNOLOGY_SNAPSHOT_ADMIN_POC.md

@@ -69,7 +69,7 @@ Use these exact values for the first POC.
    - Start the Python service on boot or via DSM Task Scheduler
    - Keep it bound to `127.0.0.1` unless you intentionally use direct bind mode
    - If you use direct bind mode, keep `--allow-remote` and Basic Auth enabled together
-   - For Gitea Actions runner verification, register `act_runner` with host labels (`self-hosted:host,linux:host`) if you want to avoid Docker job containers and the `Cleaning up container` log line
+   - For Gitea Actions runner verification, register `act_runner` with a dedicated host label (`self-hosted:host,snapshot-admin-host:host`) if you want to avoid Docker job containers and the `Cleaning up container` log line
    - Preferred launcher script: `tools/run_snapshot_admin_synology.sh`
    - Gitea CI deploy path: trigger `.gitea/workflows/snapshot_admin_deploy.yml` `workflow_dispatch` and let the host runner call the launcher script
    - Runner bootstrap: `tools/re_register_act_runner_synology.sh`
@@ -87,7 +87,7 @@ bash tools/re_register_act_runner_synology.sh
 
    - Expected effect:
      - removes the existing `.runner` registration file
-     - registers `self-hosted:host,linux:host`
+     - registers `self-hosted:host,snapshot-admin-host:host`
      - writes an updated `config.yaml`
    - If the old runner remains listed in Gitea, remove it from the repository runner page and re-run the command above