domain cutover: front doors + drone + per-run naming to ci.autonomic.zone

- acme-dns.nix: ONE dual-zone SAN cert (ci+*.ci.autonomic.zone AND ci+*.ci.commoninternet.net)
  via the same acmedns account — storage re-keyed by cc-ci-acme-storage-seed.service; handoff
  reads the new cert dir. Single secret pair => zero changes to the traefik reconciler.
- dashboard/bridge/reports: dual Host rules during the bake window (bridge gets explicit
  parentheses so && does not shadow the dashboard on the new host).
- drone abra app renamed to drone.ci.autonomic.zone (fresh DB supported: DRONE_USER_CREATE
  re-injects the sops bridge token); runner RPC + bootstrap-drone-oauth.sh follow.
- harness: app_domain() issues *.ci.autonomic.zone run domains; RUN_APP_RE / stack-name
  regexes / docker-prune accept BOTH zones during the bake. Warm stacks deliberately stay
  on the legacy zone (data-warm volumes; post-bake migration).
- URLs in bridge/dashboard defaults + recipe-report.py follow the new names.

nix/modules/docker-prune.nix

@@ -30,9 +30,11 @@ let
         exit 0
       fi
       # NEVER prune mid-run: a live run-app stack means a deploy/test is in flight (mid-pull layers
-      # can look prunable). Run-app services: <=4char>-<6hex>_ci_commoninternet_net_* (lifecycle.py).
+      # can look prunable). Run-app services: <=4char>-<6hex>_<zone-stem>_* (lifecycle.py).
+      # Zone stem matches BOTH ci_autonomic_zone (current) and ci_commoninternet_net
+      # (legacy stacks from before the 2026-09 domain cutover) during the bake window.
       if docker service ls --format '{{.Name}}' \
-           | grep -qE '^[a-z0-9]{1,4}-[0-9a-f]{6}_ci_commoninternet_net_'; then
+           | grep -qE '^[a-z0-9]{1,4}-[0-9a-f]{6}_ci_(autonomic_zone|commoninternet_net)_'; then
         echo "docker-prune: a run-app stack is live — skipping (never prune mid-run)"
         exit 0
       fi