Add execute actions to the ability object

[gziolo]

Illustration for the ideas to make abilities more extensible:

• Proposal: Provide extensibility for individual abilities #39

This PR adds extensibility hooks to the ability execution flow by introducing two action hooks that fire before and after ability execution. This allows developers to hook into the ability lifecycle for monitoring, logging, or extending functionality.

• Added before_execute_ability action hook that fires before ability execution
• Added after_execute_ability action hook that fires after successful ability execution
• Refactored the return logic to properly handle validation errors and execute the post-execution hook only on success. It is up for debate what to do on error.

Example Usage

Basic Logging

// Log all ability executions.
add_action( 'before_execute_ability', function( $ability_name, $input ) {
    error_log( 'Executing ability: ' . $ability_name );
    if ( $input !== null ) {
        error_log( 'Input: ' . wp_json_encode( $input ) );
    }
}, 10, 2 );

add_action( 'after_execute_ability', function( $ability_name, $input, $result ) {
    error_log( 'Completed ability: ' . $ability_name );
    error_log( 'Result: ' . wp_json_encode( $result ) );
}, 10, 3 );

[Copilot]

Pull Request Overview

This PR adds extensibility hooks to the ability execution flow by introducing two action hooks that fire before and after ability execution. This allows developers to hook into the ability lifecycle for monitoring, logging, or extending functionality.

• Added before_execute_ability action hook that fires before ability execution
• Added executed_ability action hook that fires after successful ability execution
• Refactored the return logic to properly handle validation errors and execute the post-execution hook only on success

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.84%. Comparing base (e48d165) to head (3845992).
⚠️ Report is 1 commits behind head on trunk.

Additional details and impacted files

@@             Coverage Diff              @@
##              trunk      #56      +/-   ##
============================================
+ Coverage     83.33%   83.84%   +0.51%     
  Complexity       96       96              
============================================
  Files             8        8              
  Lines           516      520       +4     
============================================
+ Hits            430      436       +6     
+ Misses           86       84       -2     

Flag	Coverage Δ
unit	83.84% <100.00%> (+0.51%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[justlevine]

@gziolo I know you marked as draft, but honestly this feels pretty close to mergeable.

(Unlike my filter feedback on #37 . an action should trigger every time ::do_execute() is run vs 1x).

Only question is whether we want to pass the \WP_Error to the filter as well to allow. Not necessary (WPError have their own built-in hooks), and doing this in the future is non-breaking, but it would allow for recoverability flows.

(e.g. if we're MCP and this is an input error, filter to try and coerce the shapes, but if its REST then you to rest_ensure_response( $error ) ).

[gziolo]

I know you marked as draft, but honestly this feels pretty close to mergeable.

I will work on tests and documentation before marking it as fully ready for review.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: gziolo <[email protected]>
Co-authored-by: justlevine <[email protected]>
Co-authored-by: jonathanbossenger <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[Copilot]

Pull Request Overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[justlevine]

LGTM, left some nonblocking doc nits. 🚀

[gziolo]

I will wait for a reply about the docs before landing.

[jonathanbossenger]

One small suggestion, otherwise it all looks good from a docs perspective.

[gziolo]

Just to let you know, all feedback has been addressed in 3845992. I enabled auto-merge.