Build Flood v4.7.0 in client-only mode with manual release selection

README.md

@@ -7,9 +7,15 @@ Report issues at https://github.com/k2patel/docker-flood-client/issues.
 For contributions, open an issue with a link to your branch or patch on another
 Git provider. Changes are reviewed and applied by the maintainer on Gitea.
 
-Gitea Actions publishes `docker.io/k2patel/floodui:latest` on pushes to `main`
-and manual runs. The default Flood release is `v4.16.2`; manual runs can select
-another release with `flood_version`. Builds use the custom `Dockerfile.client`.
+Gitea Actions publishes `docker.io/k2patel/floodui:latest` only on manual runs.
+Select `main` in Actions → Build and Push Custom Flood Image → Run workflow
+and set the required `flood_version` release tag. The configured release is
+`v4.7.0`. Repository pushes do not trigger builds.
+
+This is a Flood-only image using the custom `Dockerfile.client`: it runs the
+Flood web UI/API and connects to an external torrent service. It does not bundle
+or start rTorrent. The Dockerfile uses the v4.7 npm lockfile and builds client
+assets; changing release families may require updating the build tooling.
 
 Set Actions secrets `DOCKER_USERNAME` and `DOCKER_TOKEN` with Docker Hub write
 access to `k2patel/floodui`. Builds run remotely on the Kubernetes runner for