v1.0.1

Documentation overhaul (TESTING/CONTRIBUTING/ARCHITECTURE/SECURITY/CLAUDE.md,
CHANGELOG.md, drop unmaintained src/README.md) plus CI-built Docker images:
Gitea Actions now builds and pushes the servicedesk image to the Gitea
container registry on Dockerfile changes, and compose.yaml pulls that image
instead of building locally. No application behavior changes.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

README.md

@@ -66,9 +66,12 @@ and **[wiki/admin](wiki/admin/README.md)** for role-specific how-to guides.
   dashboard is hand-rolled inline-styled bar/column charts, so it needs no client
   build step beyond the CSS bundle.
 - **Database**: MariaDB.
-- **Deployment**: `compose.yaml` — `servicedesk` (php:apache, source bind-mounted
-  from `./src`, no image rebuild needed for PHP/Blade/route changes) + `mariadb`,
-  fronted by Traefik with a private-CA TLS cert.
+- **Deployment**: `compose.yaml` — `servicedesk` (source bind-mounted from `./src`,
+  no image rebuild needed for PHP/Blade/route changes) + `mariadb`, fronted by
+  Traefik with a private-CA TLS cert. The `servicedesk` image itself is built and
+  pushed by Gitea Actions (`.gitea/workflows/build.yml`) to the Gitea container
+  registry whenever `Dockerfile` changes — `compose.yaml` just pulls a tag, it
+  never builds locally.
 
 See **[install.md](install.md)** for full step-by-step deployment instructions —
 both via Docker Compose (this stack) and directly on a server with Apache/Nginx,