Trigger the restore drill on demand via drill-* tags (#87)

Gitea 1.22 cannot dispatch workflows through the API or UI (that lands in
1.23), so pushing a drill-* tag is the on-demand path next to the monthly
schedule.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EwZ4jR4KFAPvpjWevfUGX1

.gitea/workflows/drill.yml

@@ -10,7 +10,11 @@ on:
   schedule:
     # 04:17 UTC on the 1st — after the 03:00 stage-local nightly backups.
     - cron: '17 4 1 * *'
-  workflow_dispatch:
+  # On demand: push a `drill-<anything>` tag (`git tag drill-$(date +%s) &&
+  # git push origin --tags`). Gitea 1.22 cannot dispatch workflows via API
+  # or UI (that arrives in 1.23 — then add workflow_dispatch here).
+  push:
+    tags: ['drill-*']
 
 env:
   IMAGE_BASE: gitea.101010.cloud/stwaidele/dorfteich

docs/operations/restore-runbook.md

@@ -34,8 +34,9 @@ never corruption.
 
 ## Automated monthly drill (`.gitea/workflows/drill.yml`)
 
-Runs on the 1st of each month (and on demand via _Run workflow_): it
-executes `deploy/backup/drill.sh`, which
+Runs on the 1st of each month — and on demand by pushing a `drill-*` tag
+(`git tag drill-$(date +%s) && git push origin --tags`; Gitea 1.22 has no
+workflow-dispatch button yet). It executes `deploy/backup/drill.sh`, which
 
 - reads the drilled stage's backups volume **read-only** (stage volumes are
   never touched — everything scratch lives under a unique