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/roles/minecraft_fossils/tasks/main.yaml

@@ -0,0 +1,49 @@
+---
+# Fabric server plus a sidecar that mirrors the whitelist, ops and ban
+# lists from the Paper server. World data in /opt/minecraft-fossils/data
+# is not managed here. A compose change recreates the container, so it
+# is saved and stopped with time to finish first.
+- name: Deploy Minecraft Fossils
+  ansible.builtin.include_role:
+    name: docker_service
+  vars:
+    service_name: "minecraft-fossils"
+    service_base_path: "{{ services_base_path }}/minecraft-fossils"
+    service_templates:
+      - src: "secrets.env.j2"
+        dest: "secrets.env"
+        owner: "{{ minecraft_fossils_owner }}"
+        group: "{{ minecraft_fossils_owner }}"
+        mode: "0600"
+    service_files:
+      - src: "docker-compose.yml"
+        dest: "docker-compose.yml"
+        owner: "{{ minecraft_fossils_owner }}"
+        group: "{{ minecraft_fossils_owner }}"
+    # secrets.env only matters at container start; never restart the
+    # game server as a side effect of a deploy
+    service_restart_on_change: false
+    service_graceful_stop:
+      - container: minecraft-fossils
+        timeout: 120
+        pre_stop: docker exec minecraft-fossils rcon-cli save-all flush
+    health_check_enabled: false
+
+- name: Install the daily restart units
+  ansible.builtin.copy:
+    src: "{{ item }}"
+    dest: "/etc/systemd/system/{{ item }}"
+    mode: "0644"
+  loop:
+    - minecraft-fossils-restart.service
+    - minecraft-fossils-restart.timer
+  notify: Reload systemd
+
+- name: Flush handlers
+  ansible.builtin.meta: flush_handlers
+
+- name: Enable the daily restart timer
+  ansible.builtin.systemd:
+    name: minecraft-fossils-restart.timer
+    enabled: true
+    state: started