GRM-124: docs: fix outdated references and document health/restart/trigger-workflow commands

docs/tech/architecture.md

@@ -31,13 +31,14 @@ grm install <host>
               ├── rootless_docker.yml  (rootless Docker setup under runner user)
               ├── install_runner.yml   (download binary, config, register, service)
               ├── prune.yml            (Docker prune timer)
+              ├── healthcheck.yml      (health check script + systemd timer)
               └── integration_test.yml (validate service is active)
 ```
 
 The Ansible role task execution order (from `AGENTS.md`):
 
 ```
-main.yml → systemd_check → user_setup → rootless_docker → install_runner → prune → integration_test
+main.yml → systemd_check → user_setup → rootless_docker → install_runner → prune → healthcheck → integration_test
 ```
 
 - `install_runner.yml` handles: download, config, validate, register, service
@@ -59,6 +60,7 @@ main.yml → systemd_check → user_setup → rootless_docker → install_runner
 | `register.yml` | Registers the runner with Gitea using the registration token |
 | `service.yml` | Creates the systemd user service file and starts/enables the service |
 | `prune.yml` | Creates a systemd user timer for daily Docker image and volume pruning |
+| `healthcheck.yml` | Installs a health check script and systemd timer that monitors Docker daemon, runner service, and disk space; restarts unhealthy services automatically |
 | `integration_test.yml` | Verifies the `.runner` file exists and the systemd service is active; optionally queries the Gitea API |
 | `deregister.yml` | Deregisters the runner from Gitea and removes the `.runner` file |
 | `update_runner.yml` | Downloads a new version of the gitea_runner binary |
@@ -71,6 +73,9 @@ main.yml → systemd_check → user_setup → rootless_docker → install_runner
 | `gitea-runner-config.yaml.j2` | Runner configuration file (labels, capacity, log level) |
 | `docker-prune.service.j2` | Systemd user service for Docker pruning (oneshot) |
 | `docker-prune.timer.j2` | Systemd user timer triggering daily Docker prune |
+| `runner-healthcheck.sh.j2` | Health check script (checks Docker, runner service, disk space; restarts if down) |
+| `runner-healthcheck.service.j2` | Systemd user service for the health check (oneshot) |
+| `runner-healthcheck.timer.j2` | Systemd user timer triggering periodic health checks |
 
 ## Per-Runner Isolation
 
@@ -139,6 +144,7 @@ flowchart TD
    - Registers the runner with Gitea
    - Creates and starts the systemd user service
    - Sets up the Docker prune timer
+   - Installs the health check script and systemd timer
    - Runs the integration test (verifies `.runner` file and service state)
 7. Ansible output is streamed to a timestamped log file at `~/.local/state/grm/logs/ansible-<timestamp>.log`
 8. On success, the runner is added to the local registry at `~/.local/share/grm/runners.json`

docs/tech/testing-strategy.md

@@ -83,7 +83,7 @@ The platform list is defined in `devx.molecule.platforms` (single source of trut
 
 ### CI Test Distribution
 
-CI runs all 6 scenarios x 4 platforms (24 test pairs) distributed across available Gitea Actions runners.
+CI runs all 7 scenarios x 4 platforms (28 test pairs) distributed across available Gitea Actions runners.
 
 The `discover-runners` job runs `devx.molecule.discover_runners` which queries the Gitea API for registered runners at three levels (repo, org, instance) and generates a dynamic matrix. If the API query fails (e.g., no admin access for instance-level runners), it falls back to the `MOLECULE_RUNNERS` repo variable, then to a default of 3.