This changelog tracks WPColt Cache Inspector as a real product in development. It avoids fake launch claims and focuses on the diagnostic engine, report language, safety rules, and public website work needed before a first release.
Development roadmap
| Version | Status | Focus |
|---|---|---|
| 0.5.x | In progress | Plain-English report generator and conflict priority scoring. |
| 0.4.x | Internal draft | Logged-out request runner for homepage and one post. |
| 0.3.x | Internal draft | Object-cache and known plugin detection model. |
| 0.2.x | Internal draft | Header parser for Age, Cache-Control, X-Cache, X-Varnish, CF-Cache-Status, Set-Cookie, and server hints. |
| 0.1.x | Completed concept | Product scope: read-only cache diagnostics, not another caching plugin. |
0.5.0 – Report language and fix priority
The current development focus is turning raw signals into useful language. A report should not merely say MISS. It should explain whether a MISS is expected, suspicious, caused by a cookie, hidden by CDN behavior, or impossible to verify. The report format is being shaped around four sections: what is working, what is broken, what to fix first, and how to verify the fix.
0.4.0 – Logged-out request runner
- Added the planned two-request test model for homepage and one representative post.
- Separated logged-in admin behavior from public visitor behavior.
- Defined safe timeout handling so a slow origin does not freeze the report screen.
- Added room for future comparison between first request, second request, and post-update purge checks.
0.3.0 – Cache layer detection
- Mapped common WordPress page-cache plugins and optimization plugins.
- Outlined Redis and Memcached object-cache detection rules.
- Defined conflict patterns for duplicate page-cache plugins and cache plugins overlapping with server cache.
0.2.0 – Header parser
- Added interpretation model for CF-Cache-Status, Age, X-Cache, X-Varnish, Cache-Control, Set-Cookie, and Via.
- Defined HIT, MISS, BYPASS, STALE, and Unknown states.
- Added provider-neutral language so reports do not imply official partnerships.
0.1.0 – Product scope
WPColt was scoped as a read-only inspector. The first version should not purge cache, change plugin settings, write server rules, or send hidden data to a remote service. That restraint is intentional: diagnosis should feel safe to run on a production WordPress site.