WordPress database optimisation — 1002 MB down to 27 MB

First, we mapped what actually consumed space: revisions, transients, plugin orphans. Cleanup was done in batches, with backups and integrity checks after each step — zero risk of content loss. Finally, we implemented prevention: revision limits, transient cleanup schedule. This is an example of the "investigator, not guesser" method: measure the state, act with the smallest change for the biggest leverage.