1.32.0

Two releases' worth of changes: 1.31.0 was merged but never shipped, so a site
on 1.30.0 gets both.

REST Bridge: see what it would expose before switching it on

REST Bridge finds the fields it exposes by reading the definitions JetEngine
already stores, so until something reads them nobody knows what the module
will put on the API. The /digitizer/v1/info endpoint answers that, but only
for a module already running - and the module stands down while the plugin it
replaces is active. So the only way to look was to deactivate a working plugin
on a client's site and find out.

Digitizer Pro Tools > REST Bridge Preview now runs the module's discovery
and registration without registering anything, and reports what it found:
every field with its target and type, compatibility names marked, everything
skipped with the reason, the Rank Math keys, and the routes. Nothing on the
screen changes the site, and it works while the old plugin is still active -
which is the point of it.

The rehearsal suppresses exactly one call, register_rest_field(). Every
discovery, collision check, refusal and diagnostic runs as it always does.

The info endpoint gains rank_math_fields alongside its existing boolean:
those twelve keys are registered as post meta rather than REST fields, so an
agent told only rank_math: true was left to guess what that added.

Agent Log stands down for the standalone plugin

The Agent Log module has been extracted into a plugin of its own for
WordPress.org - AI Agent Activity Log. A site running both would keep two
logs of one thing, in two tables, written by two sets of listeners on the same
hooks. When the standalone is active this module now registers nothing and
says why on the Modules screen, the way Update Policy already does for
Digitizer Update Hold.

Under the hood

1564 assertions pass. Hebrew catalog at 700 strings.