uptime-kuma: annotate config and drop the unused collection

lucasheld.uptime_kuma was pinned but never used - every monitor was created by
hand-rolled Python. The uptime subdomain stays because the deprecated blocks
still template it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

ansible/requirements.yml

@@ -1,11 +1,10 @@
----
 # Ansible Galaxy Collections Requirements
 # Install with: ansible-galaxy collection install -r requirements.yml
 
-collections:
+# No collections are currently required.
-  # Uptime Kuma Ansible Collection
+#
-  # Used by: infra/41_disk_usage_alerts.yml
+# lucasheld.uptime_kuma was pinned here but never used — every monitor was created
-  # Provides modules to manage Uptime Kuma monitors programmatically
+# by hand-rolled Python instead. Removed 2026-09-11 along with Uptime Kuma itself.
-  - name: lucasheld.uptime_kuma
+# See archive/uptime_kuma/.
-    version: ">=1.0.0"
 
+collections: []

ansible/services_config.yml

@@ -5,6 +5,9 @@
 subdomains:
   # Monitoring Services (on watchtower)
   ntfy: ntfy
+  # DEPRECATED 2026-09-11 — Uptime Kuma is decommissioned and this subdomain no
+  # longer resolves to anything. Kept only because the deprecated monitoring
+  # blocks still template it into uptime_kuma_api_url. See archive/uptime_kuma/.
   uptime_kuma: uptime
   
   # VPN Infrastructure (on spacey)

requirements.txt

@@ -8,4 +8,7 @@ packaging==25.0
 pycparser==2.22
 PyYAML==6.0.2
 resolvelib==1.0.1
+# Only needed by the deprecated Uptime Kuma monitoring blocks, which are kept for
+# reference but never run (uptime_kuma_enabled: false). Drop this once they are
+# rewired to a replacement. See archive/uptime_kuma/.
 uptime-kuma-api>=1.2.1