DRAFT for review, not merged. Context: HAProxy 3.0.11 (Debian trixie) aborts via
its own watchdog in the DNS resolver (haproxy #3101, fixed in 3.0.13/3.1.11/3.2.6).
* Dockerfile: haproxy from https://haproxy.debian.net trixie-backports-3.2 (committed
signing key, fingerprint asserted, series pin 3.2.*, optional HAPROXY_EXACT),
native OpenSSL QUIC asserted (no compat layer), /haproxy/HAPROXY_VERSION.
* start HAProxy as `haproxy -W -db` (spawn_haproxy_master): `daemon` sent the
master's stderr to /dev/null, losing ALERTs and the ha_panic thread dump.
stderr -> /var/log/haproxy/haproxy-stderr.log, forwarded to container stderr by
scripts/haproxy-stderr-relay.py (rate limited, rotated).
* supervisor: pidof probe every 2 s (was python every 15 s), exponential backoff
on failed restarts.
* tests: relay unit tests; rollback/cert stubs print "Loading success.".
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0185ukXi4YX5FxJGqhi6qab6