deploy.sh: restart caddy when the reload cannot be applied

A 'caddy reload' delivered over the admin API cannot apply a config
that disables the admin API -- the fix cannot ride the API it is meant
to enable (2026-08-22: admin off sat in the running config across
deploys). Track the reload result; on failure, restart the container
so it reads the rendered file on start.

scripts/deploy.sh

@@ -159,14 +159,23 @@ if [ '${COMPOSE_UP[$TARGET]}' = '1' ]; then
   # A Caddyfile render is a bind-mount content change, not a container
   # config change: the caddy container often survives 'up -d' and keeps
   # serving its in-memory config. Reload explicitly; the file watcher
-  # (admin on) is the backstop if the API is not up yet.
+  # (admin on) is the backstop if the API is not up yet. If the reload
+  # cannot be applied at all (e.g. the running config has the admin API
+  # disabled -- the fix cannot ride the API it is meant to enable),
+  # restart the container so it reads the file on start.
+  caddy_reloaded=0
   for i in 1 2 3 4 5; do
     if podman exec caddy caddy reload --config /etc/caddy/Caddyfile --adapter caddyfile >/dev/null 2>&1; then
+      caddy_reloaded=1
       echo \"  Caddy reloaded.\"
       break
     fi
     sleep 3
   done
+  if [ \"\$caddy_reloaded\" -ne 1 ]; then
+    echo \"  Caddy reload failed; restarting the container to load the file.\"
+    podman restart caddy
+  fi
 else
   echo '[4/4] Skipping compose restart (stack runs as bare containers on this host)'
 fi