Use the short maptool:latest image name in the deploy job

docker.io/library/maptool:latest and maptool:latest resolve to the
same local image (verified on cube.local) - the docker.io/library
prefix is just podman's normalization of the unqualified name, not an
actual registry reference. Short form matches what docker-compose.yaml
itself uses and avoids implying a Docker Hub push/pull that never
happens.

.gitea/workflows/ci.yml

@@ -104,11 +104,14 @@ jobs:
       # (deliberately no `--build`), which only builds when the image tag
       # isn't already present locally. So a bare restart would just
       # relaunch the previous image; removing that tag first forces a
-      # fresh build from the code just synced above. sudo is needed since
-      # the unit — and thus the image — is root's, not gitea-runner's own
-      # (gitea-runner has passwordless sudo for this on cube-host).
+      # fresh build from the code just synced above — purely local, no
+      # registry involved (same `maptool:latest` docker-compose.yaml
+      # already builds/tags; podman rmi never talks to a registry for a
+      # locally-built image). sudo is needed since the unit — and thus the
+      # image — is root's, not gitea-runner's own (gitea-runner has
+      # passwordless sudo for this on cube-host).
       - name: Deploy
         run: |
           sudo systemctl stop podman-compose@maptool.service
-          sudo podman rmi -f docker.io/library/maptool:latest || true
+          sudo podman rmi -f maptool:latest || true
           sudo systemctl start podman-compose@maptool.service