Merge + Minify + Refresh (MMR) merges CSS and JS into combined files, stores them in wp-content/cache/mmr/, and tracks the inputs and refresh state in options like mmr_bundles and mmr_refresh_log. The plugin schedules a refresh through wp_cron as mmr_refresh_event to rebuild bundles after source changes. The default admin shows a status panel with bundle counts and the most recent refresh, but no per-bundle list with input handles, output size, or refresh history.

SleekView reads the MMR options and the cache directory index so the build appears as flat rows. One row per bundle can show its hash, the list of source handles, the output file size, and the timestamp of the last refresh. Source assets surface as a second table with the count of bundles each handle participates in, useful for spotting handles that are duplicated across too many bundles. Refresh runs become their own log view with duration, success state, and the trigger (cron, manual, source change).

SleekView is read-only against the cache directory and writes only through MMR's option and cron APIs for inline actions. The plugin keeps building bundles and serving them through its own front-end output exactly as before. Saved views like Bundles refreshed today or Handles in 3+ bundles scope per role so a developer audits the build without access to global toggles or the licence-equivalent settings.

Merge + Minify + Refresh sells a strict mental model: every enqueued CSS or JS handle gets combined into a small set of bundles, and those bundles are refreshed when their inputs change. The model works well until the input list drifts. A plugin adds three handles, a theme update changes a stylesheet version, and the refresh job stalls on a single failing build.

The default admin shows the headline numbers but never lets the engineer see the build as a build. There is no bundle list, no handle cross-reference, and no refresh log. Most teams discover a stale bundle when an editor reports that a recent theme tweak never made it to the front end, by which point the cache has been serving the old artefact for a few thousand visitors.

SleekView treats MMR's options and cache directory as exactly what they are: a build manifest. Every bundle is a row, every input is a handle, every refresh is a logged event. Developers can rebuild a single bundle, agencies can audit client builds without holding plugin rights, and operations can replay failed refreshes before they cascade into a real regression.

The plugin stays focused on bundling; SleekView gives the team a build log they can actually read.