v0.75.0

Highlights — Maintenance Edge-Proxy

A new opt-in capability: RSGO runs a managed per-product reverse-proxy ("edge", Caddy) that survives product redeploys and serves a controlled maintenance page plus a machine-readable status while the product is down — no more connection-refused. Dormant by default (no edge: block → behaviour unchanged).

• Survival & state-driven routing — proxy when Running; a controlled page during redeploy/maintenance; /hc & /liveness always pass through.
• TLS termination at the edge with RSGO-managed certificates, reloaded without an edge restart.
• Maintenance-page branding — built-in themeable page, custom HTML bundle, or your own container.
• Versioned status contract — stable GET /__status (schema 1): running | maintenance | deploying.
• Optional host-level SNI passthrough router (off by default).
• Documentation (DE/EN), customization templates (examples/edge-maintenance/) and deployable demo stacks (stacks/examples/edge/).

See Configuration → Maintenance Edge-Proxy in the docs.

---

What's Changed

🚀 Features

• feat(edge): generic maintenance edge-proxy (R2) — phases 1-5 @Wiesenwischer (#431)

📚 Documentation

• feat(edge): generic maintenance edge-proxy (R2) — phases 1-5 @Wiesenwischer (#431)
• docs(plans): add maintenance-edge-proxy implementation plan (R2) @Wiesenwischer (#430)

Full Changelog: v0.74.0...v0.75.0