release: 0.1.0: Phases 0-11: panel, Postfix/DKIM, milter, backup, Docker image

Initial feature-complete implementation of the v1.0 specification (phases 0-11 of `docs/implementation-plan.md`).
Added:
  - Panel (Go, single static binary) with SQLite persistence, one-time
  - Domain management with per-domain DKIM (RSA-2048, generated in pure Go) and
  - Application (sender identity) management: SASL credentials via `sasldb2`,
  - Full Postfix relay config generated from env at container start: SMTPS 465,
  - Journal milter (pure Go, `go-milter`) recording every send to `send_log`;
  … (6 more in CHANGELOG)

Full detail: CHANGELOG.md (0.1.0).

test/e2e/dns/Corefile

@@ -0,0 +1,16 @@
+# Authoritative fake zone for the e2e stand (plan C.4). Only e2e.test and its
+# subdomains are served — everything else is refused, which is fine: neither
+# the panel nor Postfix ever needs to resolve anything outside this zone here.
+#
+# The `file` plugin's own `reload` sub-directive (NOT the top-level `reload`
+# plugin, which only watches the Corefile itself) polls db.zone's mtime/serial
+# and reloads with no signal needed, so the test harness can rewrite the zone
+# file (to publish a domain's DKIM record) and just poll until the new record
+# is visible — no container restart, no sleep.
+e2e.test {
+    file /dns/db.zone {
+        reload 1s
+    }
+    log
+    errors
+}