docs: correct build-qt and Podman/Docker descriptions in README

ober

a0cc39aefb6841f522df7a43ea43648cc20b862a

diff --git a/README.md b/README.md
index 43f8cee..9af825e 100644
--- a/README.md
+++ b/README.md
@@ -167,7 +167,26 @@ deadlines, and one active connection. See
 make build-qt
 ```
 
-The Qt backend consists of 45 modules in `src/jerboa-emacs/qt/` (~48,801 lines). All modules must be compiled after `make build`.
+The Qt backend consists of 45 modules in `src/jerboa-emacs/qt/` (~48,801 lines).
+`make build-qt` simply runs the normal `make build` (which translates those
+`.ss` modules to `.sls` alongside the rest of the editor) and then prints a
+status banner — it does **not** compile a Qt binary by itself. To launch the Qt
+frontend interpreted, use `make run-qt`; to produce a static `jemacs-qt` binary,
+use `make static-qt` (below).
+
+### Static binaries (Docker / Linux host)
+
+```bash
+make static-qt   # fully static jemacs-qt, built via Docker (Dockerfile.qt)
+make static-tui  # static TUI binary, built on a prepared Linux host
+```
+
+`static-qt` routes to `docker-static-qt`, which builds with **Docker** and
+copies the resulting `jemacs-qt` out of the image. Podman-based container builds
+are currently **disabled**: `make check-podman` fails immediately ("container
+builds are disabled for this project"), so the legacy `*-podman` targets
+(`podman-deps`, `linux-static-qt-podman`, `linux-static-tui-podman`, ...) do not
+run. Use the Docker path for `static-qt`, or build on a prepared Linux host.
 
 ## Testing