Licensing abilities: register list, error info, attach via Registrar

[enejb]

Summary

Ships three Jetpack Licensing abilities through the WordPress Abilities API (per RSM Abilities Everywhere plan §4.2):

• jetpack-licensing/list-licenses — Filtered read over Licensing::get_user_licenses() with status (active | expired | attached | detached), license_id, and pagination. Returns a uniform { id, slug, product_name, attached_at, status, expires_at } array.
• jetpack-licensing/get-error-info — Reads the latest license-attach error stored by the Licensing package (Licensing::last_error). Read-only.
• jetpack-licensing/attach-license — Wraps Licensing::attach_licenses(). Idempotent: re-attaching an already-attached key returns attached=true. On failure returns { attached: false, error: { code, message } } with the upstream code mapped to the jetpack_licensing_* vocabulary.

Wiring is done via projects/packages/licensing/actions.php (canonical guarded pattern matching publicize / connection). Registration is gated by jetpack_wp_abilities_enabled (default false) through the Registrar base class.

Permissions reuse the existing Endpoints::can_manage_options_check gate (current_user_can( 'manage_options' )) so the abilities don't drift from the REST surface they wrap.

Test plan

• cd projects/packages/licensing && composer phpunit -- --filter Licensing_Abilities_Test — 30 tests, 127 assertions, all green.
• Full package suite (composer phpunit) — 46 tests, 188 assertions, all green.
• pnpm php:lint clean on new files.
• Manual: with jetpack_wp_abilities_enabled filter set true on a Jetpack-connected site, wp_get_abilities() lists the three new slugs and /wp-json/wp-abilities/v1/abilities exposes them.

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack), and enable the add/ship-licensing-abilities branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack add/ship-licensing-abilities

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• 🔴 Add a "[Status]" label (In Progress, Needs Review, ...).
  
• 🔴 Add testing instructions.
  
• 🔴 Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

🔴 Action required: Please include detailed testing steps, explaining how to test your change, like so:

## Testing instructions:

* Go to '..'
*

---

🔴 Action required: We would recommend that you add a section to the PR description to specify whether this PR includes any changes to data or privacy, like so:

## Does this pull request change what data or activity we track or use?

My PR adds *x* and *y*.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

[jp-launch-control]

Code Coverage Summary

1 file is newly checked for coverage.

File	Coverage
projects/packages/licensing/src/abilities/class-licensing-abilities.php	278/298 (93.29%) 💚

Full summary · PHP report · JS report