The production Caddyfile has no cache, so the documented self-hosted path reaches Postgres on every read

The shipped production Caddyfile is a plain `reverse_proxy` with no cache handler. The self-hosted path we document therefore has no edge cache at all, and every public read reaches the database.

Two honest options:

1. Add a cache handler to the Caddyfile and document what it caches.
2. Say plainly in `docs/deploy-in-production.md` that a CDN is expected in front, and which topologies it is safe on.

Either is fine. Saying nothing is what leaves a self-hoster with a surprise.

Found Sept 5 2026 while working through read load.

Locate the shipped production Caddyfile and read docs/deploy-in-production.md first. Decide whether the project should configure caching there or document the required CDN and safe topologies; done means the chosen path no longer leaves self-hosters without an explicit caching expectation.

Written by the indexing model from the issue text.