v0.5.4
PatchLatestJune 10, 2026Every fix in this release was reproduced and re-verified end-to-end on a live WordPress install before shipping: isolate rules against lazily-registered AJAX actions now fire reliably, the debug header reports the full picture, and the action picker no longer shows phantom entries.
- Rules targeting an admin-ajax action with the default URL pattern ("/") never fired. The safety net that stops a bare "/" from matching every URL on your site also swallowed admin-ajax rules — the rule looked saved but matched nothing. When a rule names specific AJAX actions, its URL pattern is now ignored entirely: matching runs on scope plus action name, which is what the rule actually selects on. Existing rules self-heal on upgrade; no re-saving needed.
- The debug response header only reported the Plugin Skipper, hiding the Isolator's work. An isolate rule could be working perfectly — stripping every plugin except the action's owner — while X-Accelerator-Skipped showed "(none)", which reasonably read as "the rule is broken." The header now reports both modules separately: skipper=<list>; isolator=<action>→<dropped list>.
- The plugin's internal version constant lagged behind the release version, which made diagnostics report a stale version and quietly disabled the scanner-cache auto-invalidation added in 0.5.3. The constant is now derived from the plugin header automatically, so it can never drift again.
- The action picker showed phantom entries harvested from code comments and dynamic registration patterns. The scanner now excludes Accelerator's own source from static scanning and matches only complete, literal hook registrations.
- Safe upgrade from any 0.5.x. No schema change. Stored rules are reinterpreted at load time; the on-disk format is untouched, so downgrade remains safe.

