v0.32.2

docs/MIGRATION.md

@@ -1,5 +1,20 @@
 # Deployment and configuration migration history
 
+## 0.32.2 -> 0.32.3 upstream protocol and Dashboard compatibility
+
+No database or backend JSON rewrite is required. In 0.32.2 an HTTPS origin
+saved as `"protocol": "http2"` could negotiate HTTP/1.1 via TLS ALPN. The same
+value **still** permits H2/H1 over TLS in 0.32.3 and still uses H2C on plaintext
+HTTP. To enforce HTTP/2 only, explicitly select new `"protocol": "h2"`.
+Existing `http1` and `auto` values, HTTP/1.1 WebSocket Upgrade, configured
+keepalive and pool settings retain their meaning.
+
+The dashboard registry grows to 24 IDs. Eight HTTP backend cards are optional,
+hidden by default for all accounts until enabled; old ordering and hide/show
+preferences survive. These use existing status data with no extra background
+polling or schema migration. Verify live behavior and WebSocket negotiation on
+a Rust-enabled staging environment before deployment.
+
 ## 0.28.1 -> 0.28.2
 
 SQLite schema 8 is upgraded automatically to schema 9. The additive migration creates `certificate_api_grants`. Existing Certificate API credentials become reload-only compatibility credentials covering all certificate IDs (`*`); rotate them in **Settings -> Certificate API** to replace the wildcard with explicit certificate IDs. New credentials require 1-32 explicit certificate IDs and are reload-only unless deploy permission is enabled.