First public WordPress.org release: English readme and service disclosure,
packaging hygiene, and internationalization (text domain loading).
plugins.update now keeps the target plugin active after upgrading it (the
WordPress upgrader deactivates during the file swap and does not restore it on a
programmatic call).
5.0.0
Actionable security.* operation family: hardenings applied at the PHP
runtime, without touching wp-config and always reversible in a single call
(file editor, REST user enumeration, XML-RPC + pingbacks, HTTP headers
HSTS/nosniff/X-Frame-Options/Referrer-Policy, minor core auto-updates,
version masking, ?author=N scan blocking).
Each op accepts dryRun (simulation without writing) and logs the before/after
value for an undo via the inverse op. security.state.get exposes the current
state. Disconnecting (unpair) resets all hardenings.
hsts is set only if HTTPS is actually enforced (anti-lockout guard).
4.0.0
New security.audit operation (read-only, manage_options capability):
free hardening snapshot (versions, configuration flags, admin accounts, core
integrity via wordpress.org checksums). No secret is returned.
3.0.0
New plugin-management operations: plugins.list (read, activate_plugins
capability) and plugins.update (live, irreversible update, update_plugins
capability).
The body is written faithfully (no destructive filtering on our side,
Gutenberg block delimiters preserved); filtered flag if the user lacks the
unfiltered_html capability.
draft mode for content: the proposal is queued and approved from the
“AudiScale pending” screen.
1.1.0
draft mode: proposed values are stored “pending” without changing the live
render.
Approval surface: “Pending AudiScale change” metabox on the edit screen + a
central screen (Settings → AudiScale pending) to approve/reject (nonce +
capability).
promote operation to approve a field from AudiScale (consent equivalent to
direct).
