WBS-7.9: target snapshot admin deploy host runner

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