v0.29.2

docs/VHOSTS.md

@@ -38,6 +38,12 @@ health/traffic history. Because the vhost configuration participates in cache co
 a rename also rotates that compatibility identity and invalidates incompatible cached objects.
 The editor warns before applying the rename.
 
+## Internal error routing
+
+The main vhost `source` may define `error_fallback`, and each Custom location may do the same. A fallback references the `id` of an enabled `internal` Custom location in the same vhost. Supported statuses are `403`, `404`, `500`, `502`, `503` and `504`; omitted status lists default to `404`. Internal targets are not reachable by ordinary path matching.
+
+Configured upstream/Web Server failures are intercepted before final response/cache publication. The original request method, URI/query and context are internally dispatched to the target, which then follows normal vhost/location processing. Validation rejects fallback cycles and runtime dispatch is depth-limited. See [V0.29.1_IMPLEMENTATION.md](V0.29.1_IMPLEMENTATION.md) for body replay bounds and an Nginx-style static -> app -> redirector example.
+
 ## Frontend selection and private IP isolation
 
 `frontend.hosts` is a normalized hostname-pattern list. Exact hostnames and a single