ansible: describe what runs on the servers

The roles had drifted far from production: Forgejo was pinned at 12
while 15.0.11 runs, its config lacked the mailer, packages and the real
database path, and several services existed only on the hosts. Running
a role would have rolled production back. Take the servers as the truth
and make the repository match them.

site.yaml now holds the desired state of both hosts:

 - base: unattended upgrades, fail2ban, Docker daemon config and the
   weekly image prune, as found on the hosts. New: a 500M journal cap,
   and the Docker systemd override is kept absent. That override once
   opened dockerd on tcp/2375 without authentication.
 - traefik: templates as deployed, version in a variable (v3.7.18).
   The Coraza WAF files are removed; no router ever used them.
 - forgejo: 15.0.11, app.ini generated from the live file with the
   secrets taken from the vault.
 - crawler_alert, sillytavern, minecraft, minecraft_fossils: added
   from the hosts.

Forgejo's canonical name becomes git.asxp.io; git.czsk.it stays as an
alias on the same router.

docker_service restarts a stack when its config changes, no longer
forces ownership on existing data directories, and hides template
diffs because they carry secrets. Containers listed in
service_graceful_stop are saved and stopped with a long timeout before
compose recreates them: Docker's 10 s default is too short for a
Minecraft world. Both game servers get stop_grace_period for the same
reason.

Removed: the full-deployment and runner playbooks with their prompts,
the Forgejo backup and restore roles for the old bare-metal host, and
inventory entries for services that were never deployed. SSH hardening
stays a manual playbook, since a mistake there locks everyone out.

New secrets (SMTP, RCON, CurseForge key) went into the vault.

Assisted-by: Claude:fable-5-2

ansible/site.yaml

@@ -0,0 +1,46 @@
+---
+# Everything the deploy pipeline manages. Idempotent: a run with nothing
+# to change touches nothing and restarts nothing.
+#
+#   ansible-playbook site.yaml --check --diff        # dry run
+#   ansible-playbook site.yaml --tags traefik        # one service
+#
+# Host bootstrap (WireGuard, SSH hardening, s3fs, swap) is in playbooks/
+# and is run by hand.
+
+- name: Host baseline
+  hosts: asxpio
+  become: true
+  roles:
+    - { role: base, tags: [base] }
+
+- name: asxpio-ops services
+  hosts: ops_servers
+  become: true
+  roles:
+    - { role: traefik, tags: [traefik] }
+    - { role: crawler_alert, tags: [crawler_alert] }
+
+- name: asxpio-services services
+  hosts: services_servers
+  become: true
+  roles:
+    - { role: sillytavern, tags: [sillytavern] }
+    - { role: minecraft, tags: [minecraft] }
+    - { role: minecraft_fossils, tags: [minecraft_fossils] }
+
+# Late: restarting Forgejo briefly cuts the runner off from its job log
+- name: Forgejo
+  hosts: ops_servers
+  become: true
+  roles:
+    - { role: forgejo, tags: [forgejo] }
+
+# Last: when the pipeline changes the runner it recreates the container
+# that is running the pipeline. Everything else is done by then; that job
+# ends as failed and the next run confirms the result.
+- name: Forgejo runner
+  hosts: services_servers
+  become: true
+  roles:
+    - { role: forgejo_runner, tags: [forgejo_runner] }