v0.26.7

docs/CACHE.md

@@ -246,9 +246,11 @@ existing deduplication guard.
 
 `GET /api/cache` reports settings, HIT/MISS/BYPASS, hot/cold counts and bytes,
 configured COLD byte/object limits, promotions/demotions, errors, fill pressure, object
-views and per-domain reason counters. The overview dashboard shows COLD disk occupancy
-separately from RAM accounting. Hit ratio is `hits / (hits + misses)` and intentionally
-excludes BYPASS traffic.
+views and per-domain reason counters. The `/cache` dashboard shows HOT and COLD
+occupancy against the configured object-count and byte limits with progress bars and
+explicit percentages. HOT byte occupancy uses the charged/allocated HOT value rather
+than logical body bytes; COLD byte occupancy uses persisted storage bytes. Hit ratio is
+`hits / (hits + misses)` and intentionally excludes BYPASS traffic.
 
 `POST /api/cache/purge` requires the existing administrator session, same-origin marker
 and CSRF token. `?vhost=<id>` purges only that vhost scope; omitting it purges all cache