Phase 1: Docker image, supervisord, three-process cold start

Single bookworm-slim image running opendkim + panel + postfix under
supervisord with enforced start ordering (spec 4):

- build/Dockerfile: multi-stage static Go build; runtime installs postfix,
  opendkim, cyrus-sasl, supervisor, logrotate; unprivileged panel user (7.6.8).
- build/supervisord.conf: priority ordering opendkim -> panel -> postfix;
  crashexit event listener terminates the container on any FATAL process.
- build/postfix-wrapper.sh: waits for both milter sockets (test -S, 30s
  timeout) before `postfix start-fg`, exits non-zero on timeout.
- panel: HTTP :8080 stub + /healthz, journal-milter socket stub (so the
  wrapper's readiness probe passes), log-tailer stub; SIGTERM graceful stop.

Verified on the dev server: image builds, three processes live, panel serves
the stub, wrapper waits for sockets, and an unrecoverable panel failure brings
the container down cleanly.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

cmd/panel/logtailstub.go

@@ -0,0 +1,16 @@
+package main
+
+import (
+	"context"
+	"log"
+)
+
+// tailMailLog is the Phase 1 placeholder for the log-tailer role. In Phase 6 it
+// will follow mail.log and reconcile send-log delivery statuses by queue-id;
+// for now it just idles until shutdown so the role is present in the process
+// tree and its wiring is exercised.
+func tailMailLog(ctx context.Context, path string) error {
+	log.Printf("log-tailer stub active (will follow %s in Phase 6)", path)
+	<-ctx.Done()
+	return nil
+}