automx: the launcher's wrapper is written by the build that ships it

The predecessor's image carried .venv/scripts/flask.sh, created by a
build step that never made it into the files this module holds — the
image worked and its recipe could not reproduce it, caught the moment
the mesh built it from source (exit 127 crash loop at cutover). The
wrapper is now written explicitly, verbatim from the proven image, so
the recipe is the whole truth about the image.

modules/mailu/automx/Dockerfile

@@ -21,6 +21,18 @@ RUN ./setupvenv.sh \
    && . .venv/bin/activate \
    && pip install automx2
 
+# The launcher `start` expects. In the predecessor's image this wrapper appeared during a build
+# step that never made it into the files this module carries — the image worked and the recipe
+# could not reproduce it. Written here explicitly, verbatim from the proven image, so the build
+# is the whole truth about the image again.
+RUN mkdir -p .venv/scripts && printf '%s\n' \
+   '#!/usr/bin/env bash' \
+   'set -euo pipefail' \
+   '. .venv/bin/activate' \
+   "export FLASK_ENV='production'" \
+   "export FLASK_APP='automx2.server:app'" \
+   'flask "$@"' > .venv/scripts/flask.sh && chmod +x .venv/scripts/flask.sh
+
 ENV AUTOMX2_CONF=/etc/automx2.conf
 ADD automx/files/automx2.conf /etc/automx2.conf