feat(observability): make the five Dankclaw observability containers quadlets

prometheus, grafana, loki, alloy and node-exporter ran only from
dankclaw/compose.yaml. Rootless podman does not restart bare containers, so
they did not survive the 2026-09-11 reboot for the amd_iommu=off change and
had to be restored by hand — the same gap that had already cost the fleet
Caddy and Pi-hole, which is why the boot-persistence rule exists.

Each is now a rootless Quadlet unit under dankclaw/observability/quadlet/,
installed and dispatched by deploy_observability in deploy-remote.sh, with
the compose definitions retired so only one owner exists per container name.
Images, mounts, arguments and container names are unchanged, so Caddy's
proxies and Prometheus' own scrape config keep resolving.

Two posture changes, both about the unauthenticated surface:

* The three HTTP UIs published on 0.0.0.0 with no authentication of any kind
  (Prometheus even with the lifecycle endpoint enabled). They now publish on
  127.0.0.1: the browser path is the guarded franksdank.cloud vhost, Caddy
  reaches them by name over dankclaw_default, and the host-side homepage
  status timer probes loopback. Nothing legitimately used the LAN port.
* node-exporter bound :9100 on every interface; it now binds exactly its two
  consumers, loopback (homepage timer) and the LAN address (Prometheus, which
  runs in a container and cannot reach the host's loopback).

alloy gains a reachable health endpoint: its UI listens on the container's
own loopback and alloy 1.x refuses a config block for it, so the compose
service had nothing to probe — the homepage status card for alloy read 'down'
continuously. The unit moves the UI with a command-line flag and publishes
127.0.0.1:12345.

grafana keeps its Authentik OAuth client secret without receiving the whole
.env: systemd expands the value from a [Service] EnvironmentFile, which never
reaches the container.

scripts/test-changed.sh

@@ -107,6 +107,17 @@ for path in "${CHANGED[@]}"; do
             add_test tests/searxng_quadlet.bats
             add_test tests/deployment_scoping.bats
             ;;
+        # The five observability containers left compose for Quadlet units on
+        # 2026-09-11. Their seam pins boot persistence and the loopback-only
+        # publish posture that keeps them off every host interface. This case
+        # precedes the dankclaw/*/quadlet/*.container fallback below, which
+        # would otherwise swallow it into unrelated seams.
+        dankclaw/observability/*)
+            add_test tests/observability_quadlet.bats
+            add_test tests/caddyfile.bats
+            add_test tests/deployment_scoping.bats
+            add_test tests/docs_completeness.bats
+            ;;
         # Caddy left compose.yaml on 2026-08-26 for a quadlet; caddyfile.bats
         # now asserts against the quadlet itself. Route every change under
         # dankclaw/caddy/ to both seams (this block must precede the