GRM-13: fix: rewrite integration test to verify .runner file and container health instead of unreliable API checks

.env.example

@@ -5,15 +5,19 @@ GITEA_URL=https://git.example.com
 # Admin → Actions → Runners → Create Registration Token
 GITEA_REGISTRATION_TOKEN=your-registration-token
 
-# Gitea admin API token for post-install integration test (optional).
-# The runner registration token above is NOT sufficient for the
-# /api/v1/admin/runners endpoint; it is only valid for registration.
-# To verify the runner appears in Gitea after install, generate a
-# personal access token with at least the "admin" scope:
-#   Settings → Applications → Generate New Token → scope: admin
-# If left unset, the integration test is skipped gracefully.
+# Gitea API token for optional post-install API checks (informational only).
+# The integration test primarily verifies the runner by checking:
+#   1. The .runner registration file exists and is valid
+#   2. The container/service is running
+# If set, API checks are performed as a bonus but do NOT affect pass/fail.
+# Required scopes: read:user, read:repository, read:admin (or just "admin")
+# Generate token at: Settings → Applications → Generate New Token
 # GITEA_ADMIN_TOKEN=your-admin-api-token
 
+# Integration test API retries (optional, default: 3).
+# Number of times to retry API checks waiting for runner to appear.
+# GITEA_INTEGRATION_RETRIES=3
+
 # Default SSH user for remote hosts (optional, overrides --user)
 # GITEA_RUNNER_USER=ubuntu