# RustProxy 0.24.8 dashboard cache-memory audit

## Scope

0.24.8 is a dashboard-focused patch. It does not change cache admission, HOT/COLD ownership, persistence, memory limits or cache protocol behavior. It exposes the existing runtime counters more clearly in the overview and reduces permanent explanatory text.

## Overview cache charts

The Cache RAM card now retains the HIT/MISS/BYPASS activity chart and adds/extends resource histories:

- **HOT RAM usage / limit** uses the cache resident/charged byte history and scales it against `hot_limit_bytes` when a finite limit is available.
- **Transient RAM usage / limit** tracks total transient bytes and overlays fill bytes, the byte-bounded COLD writer queue and active COLD read/write I/O buffers on one shared scale. These series are diagnostic lines, not additive stacked accounting.
- **COLD storage usage / limit** tracks persistent COLD bytes against `cold_limit_bytes`. This is disk/storage occupancy and is deliberately not included in process RAM accounting.

All histories keep the existing bounded 60-sample browser-side window and are populated from the already-authenticated `/api/status` payload. No new endpoint or cache-runtime allocation is introduced.

## Memory-accounting explanation

The translated `memoryAccountingHint` text remains unchanged in meaning but is no longer displayed as a permanent paragraph. It is shown on demand from an accessible information control in the Process heading.

## Verification

Offline source checks assert the new chart IDs/history arrays, the retained accounting hint, the information control, release identity and language keys. JavaScript syntax, language JSON parsing, source-package checks and release smoke checks remain part of the standard release verification. Compiler/browser/live-load acceptance remains a release-host gate where those runtimes are available.