What's in 3.1.1

Hook API content sanitization — /hooks/receive now sanitizes the content param with wp_kses_post() so allowed HTML (headings, links, bold) is preserved when OpenClaw pushes ability requests. Other params still use sanitize_text_field().

Dependency bump — simple-git 3.30.0 → 3.33.0 via npm overrides.

See CHANGELOG.md for full details.

[3.0.6] - 2026-03-10

Why this matters: disabling an ability or using the approval workflow now works on every execution path (including MCP). You get less error log noise and a single place to see how to run the full test suite.

Added

• Destructive toggles enforced in execute callback — Disabled abilities now return an error from the ability callback itself, so no path can run them. Approval workflow is enforced in the same callback: destructive abilities only run when executed from an approved queue item, so MCP or any direct wp_execute_ability call cannot bypass the queue.
• Approval_Queue "executing approved" flag — approve_item() sets a request-scoped flag before calling wp_execute_ability and clears it in finally, so the ability callback can allow execution only when that flag is set.
• Tests for approval in execute path — test_destructive_ability_requires_approval_when_workflow_enabled and test_destructive_ability_runs_when_executing_approved ensure the approval guard and flag behave correctly.
• Testing all features guide — Test-Coverage.md now has a one-shot procedure (make check, test-wp-env, npm lint/build/test, e2e, plugin-check) and a feature-to-test-file mapping table.

Fixed

• MCP server only passes registered abilities — The list sent to the MCP Adapter is now filtered to ability names that actually exist (wp_get_ability), so disabled abilities (e.g. delete-post) are no longer in the tool list and the adapter no longer logs "ability does not exist" repeatedly.
• Woo delete-product confirm test — Assertion now accepts either "confirm" or "WooCommerce" in the error message so the test passes when WooCommerce is inactive.
• MCP server tests in wp-env — Tests that call register_server are skipped when core/get-site-info is not registered (e.g. wp-env without MCP Adapter) to avoid incorrect usage notices.

Changed

• FAQ and Configuration docs — New FAQ "How do I stop the AI from deleting posts?" clarifies that governance toggles control reports only; disable the delete-post ability in Abilities to remove the tool. Approval workflow is documented as applying to all execution paths. Governance and Abilities tabs in Configuration mention the same.

What's Changed

• Bump fast-xml-parser from 5.3.5 to 5.3.6 in the npm_and_yarn group across 1 directory by @dependabot[bot] in #5
• Bump @wordpress/blocks from 15.12.0 to 15.13.0 by @dependabot[bot] in #10
• Bump @wordpress/interactivity from 6.39.0 to 6.40.0 by @dependabot[bot] in #9
• Bump @wordpress/e2e-test-utils-playwright from 1.39.0 to 1.40.0 by @dependabot[bot] in #8
• Bump @wordpress/element from 6.39.0 to 6.40.0 by @dependabot[bot] in #7
• Bump basic-ftp from 5.1.0 to 5.2.0 in the npm_and_yarn group across 1 directory by @dependabot[bot] in #13
• Bump @wordpress/scripts from 31.4.0 to 31.5.0 by @dependabot[bot] in #19
• Bump @wordpress/blocks from 15.12.0 to 15.13.0 by @dependabot[bot] in #17
• Bump phpstan/phpstan from 2.1.39 to 2.1.40 by @dependabot[bot] in #14
• Bump infection/infection from 0.32.4 to 0.32.6 by @dependabot[bot] in #15
• Bump actions/checkout from 4 to 6 by @dependabot[bot] in #23

Full Changelog: v3.0.4...v3.0.5

Full Changelog: v3.0.3...v3.0.4

Full Changelog: v3.0.2...v3.0.3

Full Changelog: v3.0.1...v3.0.2

Full Changelog: v3.0.0...v3.0.1

Full Changelog: v2.9.0...v3.0.0

Full Changelog: v2.8.0...v2.9.0

Full Changelog: v2.7.0...v2.8.0