WordPress performance fix

This skill changes a production site. Everything here exists to make that reversible.

Prerequisite: ranked findings from wp-perf-audit, plus a baseline measurement to compare against. Without a baseline there is nothing to prove afterwards, so capture one first.

The loop

One change at a time. Never batch, never parallelize, never continue past a failed step.

plan → validate --preflight → approve → snapshot → validate → apply
     → purge → verify → measure → record

The order is load-bearing. Snapshot precedes apply so rollback exists before it is needed. Purge precedes verify so verification reads the new state rather than a cached copy of the old one.