docs(caddy): drop the misleading "skip /openapi.json" comment (#273)

The Caddyfile's encode block had a comment claiming "Skip for
/openapi.json since it's already small and aggressive compression
on JSON adds a few ms" — but the actual directive is bare
\`encode gzip\` with no path matcher, so /openapi.json gets gzipped
along with everything else.

The phantom skip has been there since the original TLS-reverse-proxy
PR. Replace the misleading reasoning with an accurate note: we
compress everything, the JSON-payload sizes here make that a clear
win, and /openapi.json's CPU cost is negligible at the rate it's
hit. Mention the historical inaccuracy so future readers don't
re-derive the same false conclusion from a stale comment.

Caddy config only; no test impact. 760 still passing.

Co-authored-by: Aaron K. Clark <akclark@thenetwerk.net>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: 3 people

caddy/Caddyfile

@@ -35,8 +35,11 @@
         header_up Host {host}
     }
 
-    # Compress responses. Skip for /openapi.json since it's already
-    # small and aggressive compression on JSON adds a few ms.
+    # Compress responses. Applies to everything Caddy serves — the
+    # JSON payloads in this API are mostly small list bodies where
+    # gzip's wins still beat the negligible CPU cost, and /openapi.json
+    # is rare enough not to matter. (An earlier comment here implied
+    # we skipped /openapi.json; the config never actually did that.)
     encode gzip
 
     # Structured access logs to stdout in JSON. Matches the app's