Skip to content

Release 3.0.6

Choose a tag to compare

@nickhamze nickhamze released this 10 Mar 14:31

[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" flagapprove_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 pathtest_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 guideTest-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.