- every write that records history (admin, MCP, batch, import, undo,
automatic) queues the framework's site-cache purge (kind seo, slug the
address or * for settings and robots.txt) after its commit, once per
transaction; a rolled-back write never purges
- the record-deleted cleanup and the address tracking of saves outside the
admin run in lagoon transactions, so their history purges as well
- the RecordSaved listener re-describes an updated record of a content
type after commit and applies AddressChanged per changed locale, so
Journal's API, MCP and imports get the 301 too; an admin save that
already applied it changes nothing more
